cl.exe which compiles C and C++ has nothing in common with the CLR compiler
(.NET).
Unrelated issues, and what Curtis said : a bit of perspective, gcc is NOT
100% compliant either.
The issue has to do with standards compliance and C++ idioms, not MS
business strategy
Funny how any sense of perspective is thrown out the window with the
opportunity to rag on MS...
Sheesh !!
P.S : if warnings prevented building, no one would be flying today or
tomorrow :) yeah, you're talking about backwards compatibility but obviously
don't have a clue : you can use old standard "unsafe" versions of the
routines if you want to, program will run fine on all versions of windows...
On Sun, Jul 19, 2009 at 11:27 AM, Alan Teeder <ajtee...@v-twin.org.uk>wrote:
> It is one thing to bring out a new software tool, in this case a
> compiler, that enables the use of new technologies (.NET for example), but
> to completely disregard the principles of backwards compatibility, forcing
> software to be extensively re-written, is another.
>
>
> ------------------------------
>
>
>
--
Be Kind.
Remember, everyone is fighting a hard battle.
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
