Hi Sukender,
IMHO your tone is too confrontational. Nothing is gained from this tone,
as no one here as far as I know has any control over these issues.
Stupid question #1: Why use VC9? For me there is *absolutely no improvements*
that I'll use. May we wait for VC10?
If you don't need it don't buy it. Speak with your wallet.
Stupid question #2: Why the hell C++ .lib can't be compatible across compilers;
I mean, is that so difficult to set an standard? Or is there something I don't
know?
Ask Microsoft, I'm not sure anyone here can answer this (other than say
that it's marketing or bad programming, but I think even that isn't the
whole story - it's rarely that simple - and just bad mouthing without
having all the facts doesn't gain us anything)
There are some other "features" in MSVC that will make your programs
crash if you link libs with the "feature" disabled into an executable
with the "feature" enabled. One example is iterator debugging
(_HAS_ITERATOR_DEBUGGING), another is checked iterators (_SECURE_SCL).
These can bring problems akin to those which different versions of the
VC++ runtime (DLL vs static, or version number) can bring.
There are only three solutions IMHO:
1. be informed about these issues in order to keep control over your
build system
2. code in pure C so that the VC++ runtimes are not involved
3. do not use MSVC to compile anything (and be aware of the business
implications of this)
J-S
--
______________________________________________________
Jean-Sebastien Guay [EMAIL PROTECTED]
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
