No, I think COBOL is obsoete. Everyone should move to FoxPro ASAP!

my new voodoo5 card can handle Logo at an *incredible* speed..

THAT''s the language of the future!!

Wazoo

What we do in this life,
echoes in eternity!

As far as C++ being dead, no.

But probably what the person meant is that in .NET, all three langauges (VB, C++, C#) get compiled into an intermediate language. So in .NET, all 3 programs will run at the same speed. Now, you can usually do things in C++ that are faster than VB by the nature of the language, so you can still get an improvement from speed from that, but otherwise they are the same speed. Will C++ die out? Not necessarly. But it comes down to using what you prefer.

This does not apply outside .NET... C++ is ALOT better compared to VB as it stands now.

pouya wrote:
>>i think by intermediate file they mean something like
>>Java''s .class code. which then has to be interpretted by a
>>virtual machine
>>but isn''t that really slow?
Yes its slow but it dosnt work that way.
the difference is that Java is based on running on a virtual machine... that has its own assembly language, java bytecode.
This means that java programs are interpreted instead of compiled.

.Net uses an intermediate language, which is compiled to machine code once you activate the file.
this means you have to wait for it to compile it the first time.

ragonastick wrote:
>>I think C++ is already compiled into an intermediate language
>>already
well it is correct that your files are compiled into separate object files, that are linked together at the end, but since these objects files contains machine code, it would be wrong to call it an intermediate language

C# is C++ & Java spliced & broken to work with VB style coding, so that Microsoft can extend the language due to losing a law-suit against Sun for trying to extend Java.
There are no pointers.
It garbage collects.
No multiple inheritance.
And some ranting about -> being stupid, you always use a .

That what I remember from what I read about C# on the msdn site & else where.

some one said VB and VC++ used the same compiler. Not so, VB is interpeted kind of like java but I think vb is a bit faster.

Matthew
WebMaster
www.Matt-Land.com

VB and VC++ are using the same back-end compiler, and VB can generate native code, not only interpreted (since VB 5.0). So it''s way faster than Java, even though most people who are using VB are also beginners, so they don''t know how to unleash its true power

The reason why VB is slightly slower than VC++ is not only because the language lacks some useful keywords suchs as ++, but also because it heavily relies on OLE. But it''s still fast enough to make games and all kind of applications.