Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Zironic]

Qualms it seems the community has.

[PermanentInk]

PermanentInk cancels Post Reply: Taken by Melancholy.

[buman]

CCCCOMBO BREAKER

[Hippoman]

3 posts until it descended into madness. That was kwick (no q for you! )

Well take that! I broke your avatar!

[Dark Dude]

C ftw, simple but effective. I can imagine Dwarf Fortress being programmed in Visual Basic or something... oh god, the lag... the lag!

[Deon]

C ftw, simple but effective. I can imagine Dwarf Fortress being programmed in Visual Basic or something... oh god, the lag... the lag!

What the hell are you talking about?! Both C and VB are just providers, and it's compiled in framework so the result is the same in the end.

It doesn't matter if it's written

Code: [Select]

if a>b then
  a=0
end ifor

Code: [Select]

if (a>b) {a:=0}
the result is the same. VB code takes more space but it's easier for someone.
If you want to talk about native, both C/VB are not native, the native is IL (Instruction list).

Honestly, at least open the **** wikipedia before posting something about computAr programming .

Oh well. It looks like I was rick'trolled . Lol. Also, what's wrong with Hippo, stop this stupidity please with Q. QQ .

P.S. OH GOD! My posts starts with Quote....

[Hippoman]

My quizzical amry of queberts strike without any quaint feeling!
ook ill stop :C

[eerr]

What, visual basic?
it's just slow to load up, the entire visual basic library is loaded in one go.

otherwise it runs just fine like any other microsoft product with excessive available free memory.

just fine.

[Hippoman]

What are you talking about now?

[ricree]

the result is the same. VB code takes more space but it's easier for someone.
If you want to talk about native, both C/VB are not native, the native is IL (Instruction list).

Err...... do you want to doublecheck what you said there?  C most certainly compiles down to native code, unlike vb, which compiles to bytecode that is executed by the CLR.  Perhaps you were thinking of C# or managed C++, for which everything you said would be true?  But for normal C, your post is not correct.

[AtomicPaperclip]

Quite interesting, I just noticed there are 5 posts in this thread that start with Q.

Quite a quizzical moment.

Quif quizzes are quizzical, what are tests?

[Deon]

the result is the same. VB code takes more space but it's easier for someone.
If you want to talk about native, both C/VB are not native, the native is IL (Instruction list).

Err...... do you want to doublecheck what you said there?  C most certainly compiles down to native code, unlike vb, which compiles to bytecode that is executed by the CLR.  Perhaps you were thinking of C# or managed C++, for which everything you said would be true?  But for normal C, your post is not correct.

Sorry, I didn't work with C . I started with C++ in school and now I dabble in C#. Thanks for the info .

[Exponent]

the result is the same. VB code takes more space but it's easier for someone.
If you want to talk about native, both C/VB are not native, the native is IL (Instruction list).

Err...... do you want to doublecheck what you said there?  C most certainly compiles down to native code, unlike vb, which compiles to bytecode that is executed by the CLR.  Perhaps you were thinking of C# or managed C++, for which everything you said would be true?  But for normal C, your post is not correct.

For what it's worth, VB5 and VB6 could be compiled to native code, while the CLR is a .NET thing.  And I'm guessing a lot of people learned on pre-VB.NET, and likely have even used it professionally (e.g., I've used VB6 for two jobs in the past).

The biggest technical difference that I can think of between C and VB6 (aside from the built-in GUI functionality of VB6 and its tight integration with Windows) is that VB6 forced a person to use reference-counted memory management, while C of course was rather open-ended with its memory management, offering just a minimal allocator and requiring the programmer to actually manage the memory.

But for careful and knowledgeable use, (a preface that is necessary for pretty much every language, even C), I doubt performance was muc of an issue.  Without care and knowledge, my (possibly gross) generalization would be that VB more often leads to buggy behavior or performance issues, while C more often leads to buggy behavior or crashes.  There may be arguments over which of these alternatives is least critically problematic, but the obvious underlying problem in most of these cases is simply a failure to design and implement programs properly.

[Granite26]

C(and C++) is the driving equivilent of the autobahn with no guardrails through the alps... It's fast, and if you want to skip the switchbacks by going straight down the mountain, that's your perogative. 

[Alexhans]

quacke to the power of C++!!! 

Hippo is turning this into a programming forum XD

anyway... LCS is coded in c++ too.