quote:
Original post by Anonymous Poster Personally I use the VC++ IDE but have it set to use the Intel compiler, which takes a bit longer to compile but generates quicker code in some cases.
But...one thing that MS does know how to do is write compilers. There is not a single c/c++ compiler that conforms EXACTLY to the standard. Sometimes this is a bad thing, but sometimes this is a GOOD thing, as the standard is not perfect. I believe most non-conformances go unoticed by people in this forum. For those of you who are trashing the MS compiler due to it being non-conforming...what are your specific issues with it?
I know that before the first (or second?) service pack for VS.NET, friend functions didn''t give you access to private data members, and I believe you have to declare a friend function in the class before defining it whereas with the standard you don''t have to declare it in the class (I chould be wrong about the standard though).
quote:
Original post by YoshiN I know that before the first (or second?) service pack for VS.NET, friend functions didn''t give you access to private data members,
There haven''t been any service packs for VS.NET.
"If there is a God, he is a malign thug." -- Mark Twain
--AnkhSVN - A Visual Studio .NET Addin for the Subversion version control system.[Project site] [IRC channel] [Blog]
I know that before the first (or second?) service pack for VS.NET, friend functions didn''t give you access to private data members
WRONG!
quote:
, and I believe you have to declare a friend function in the class before defining it whereas with the standard you don''t have to declare it in the class (I chould be wrong about the standard though).
Do you even program in c++? That would completely destroy the purpose of access modifiers.
Have you ever used vs.net, or do you like making completely uninformed statements?
