Linked by David Adams on Sun 14th Aug 2011 22:41 UTC, submitted by subterrific
Permalink for comment 485032
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2009-12-10
Oh I see. And you haven't heard about the memory barrier intrinsic either that guarantees just this. And why is it so dangerous for the compiler to improve your code? You want it to run as slow as possible?
So you write cross compiler code, except that you use one specific feature not supported by all compilers. Which makes it not cross compiler code after all.
... But to me (feel free to disagree), the lack of good make alternative is a good show-sign as for MS "commitment" for C/Cxx.
The build system is not part of C++. So it says absolutely nothing about their commitment. But if you like GNU make so much (not that I understand why), why don't you just compile your program with GNU make?
So the message scares you. And the scary message takes 20% of your time. I'm shaking in my boots!
I assume that this is the first time you hear about EEE, right?
I do not use any of these C functions. I code in C++ with the C++ features such as string classes which ensures I don't do buffer overruns of this type. So yes, I haven't heard about EEE, which I assume is some solution to a C developers problem which does not apply to me. The only reason I know about this warning at all is because I compile C dependency libraries once in a while.
Not that its particular relevant since it can't be from this warning message you spend 20% of your development time..
Making such bold claims without knowing who I am and what I do for a living (and for how many years) may make you look like a complete condescending asshole.
Takes one to know one?
But here's some more I know best attitude for you: If I can target 4 platforms (Windows, Linux, Mac and iOS) using 3 different compilers (MSVC, GCC, LLVM) doing high performance multi-core software rendering and only spend a fraction of my time on differences between the compilers, then what am I doing right that you are doing wrong?