Huh? What incentive does C# have to be compatible with any ANSI standard?So basicalyl C# fails to be ansi compatible.
Huh? What incentive does C# have to be compatible with any ANSI standard?So basicalyl C# fails to be ansi compatible.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
Yes, I strongly beleive that C# ruins C, I learnt C to get away from the horrible .NET framework. Anyway, if Visual C++ uses any part of microsoft's .NET framework it should be condemned for ruining the language.
Also I strongly urge you all to boycott the .NET framework.
long time no C; //seige
You miss 100% of the people you don't C;
Code:if (language != LANG_C && language != LANG_CPP) drown(language);
C++/CLI has C#, VB.NET, etc uses the dotNet Framework. C++ and C does not.
Originally Posted by Adak
That's kind of like telling people to boycott the ACLU. I'm sure there are people that depend on them - but really - what do they care if you're not using their services?Also I strongly urge you all to boycott the .NET framework.
Sean is right. Instead of boycotting one can simply be arrogant towards those who do use it. Just like how one should deal with the ACLU.
"In all matters of opinion our adversaries are insane" - Oscar Wilde
Originally Posted by brewbuck:
Reimplementing a large system in another language to get a 25% performance boost is nonsense. It would be cheaper to just get a computer which is 25% faster.
I don't use .NET or C# in my daily work. But I've used it a little bit. As somebody who has written a huge amount of code, I don't see what's so bad about it. Other than the fact that it came from Microsoft.
If you are interested in writing only code backed by an international standard, then obviously you won't code in C# or use .NET. If not, I see no reason not to leverage it.
Code://try //{ if (a) do { f( b); } while(1); else do { f(!b); } while(1); //}
