quote:Original post by daerid
what''s the other 2%?
Hidden porno.
quote:Original post by davepermen
it can't 'export' templates.. rest should work, but i'm not sure.. its a longlong time i read the last time about it...
call it very compliant.. and call comeau full compliant.. and call the 2002 quite compliant.. and call vc6.. uhm.. not allowed to post that, i would get too much ***** in my text else:D (not that i don't use it.. but.. uhm.. its another language:D)
"take a look around" - limp bizkit
www.google.com
quote:http://gotw.ca/gotw/085.htm
That is Variant's major weakness: Most real-world compilers don't even come close to being able to handle this implementation, and the code should be viewed as important but still experimental. I attempted to build Alexandrescu's Variant code using all of the compilers that I have available: Borland 5.5; Comeau 4.3.0.1; EDG 3.0.1; Intel 7.0; gcc 2.95, 3.1.1, and 3.2; Metrowerks 8.2; and Microsoft VC++ 6.0, 7.0, and 7.1 RC1. As some readers will know, some of the products in that list are very strong and standards-conforming compilers. None of these compilers could successfully compile Alexandrescu's template-heavy source as it was provided.
I tried to massage the code by hand to get it through any of the compilers, but was only successful with Microsoft VC++ 7.1 RC1. Most of the compilers didn't stand a chance, because they did not have nearly strong enough template support to deal with Alexandrescu's code. (Some emitted a truly prodigious quantity of warnings and errors -- Intel 7.0's response to compiling main.cpp was to spew back an impressive 430K's worth -- really, nearly half a megabyte! -- of diagnostic messages.)
export
support.
quote:Original post by liquid_ice_programmer
If VS.net 2003 is 98% C++ compliant what persent is VS.net 2002?
quote:Original post by antareus
The export keyword is hard to implement. Really hard.