VB6 - Cobol of the future?

[AtW]

What I mean is that I call CreateThread() if I want a thread (which I think is what you do in C#). That's an API call; not sure why anybody thinks functions of the API should be part of the language.

Well, printf is also an API call. Why not remove it? Obviously the issue with threads in C++ is that there is no standard way to do threads on all flavours of Unix and on Windows I think it is done differently too - Unix itself I think favoured processes rather than threads, at least until recently, as far as I am aware, Linux was piss poor when it came to threads - Unix guys are just too used to processes rather than threads.

I don't think you can easily implement gargabe collection in C++ easily - can't be arsed to find out exact details, but I think in environment where you can easily take pointers as a matter of routine then garbage collector can free memory block when it might be used later.

I don't think they should put GC into C++ - it will never be as good as in C# and people who can't deal with leaks should not touch C++ anyway, it's a dieing language for a very small minority of people. I don't feel sorry I no longer use it to be honest - I like C#.

[Churchill]

No.

COBOL is fit for purpose because it is reliable in the extreme. It doesn't make your algorithms easy, but it does protect your data.

It was invented before there was a Microsoft.

Hmm.

I was taking the piss!

And yes, I know you can get "Cobol for .NET"!

[DiscoStu]

I think this may be the nerdiest thread I've ever seen on here.