Add compiler detection for C++11 features support

[asmodehn]

No description provided.

[XorfacX]

Why not think it as the default (we are in 2014 now after all) and check when not supported ?

[asmodehn]

I agree for most software. However many compilers do not implement it
completely yet... and in that case we should provide a fallback behavior.

So we will have anyway multiple fallbacks behavior in code... which means
the build system needs to detect and pick the fallback behaviors we need
when we need them.

That is the job of wkcmake, so it still has to know about multiple versions
of c++...
On Feb 14, 2014 3:27 PM, "XorfacX" [email protected] wrote:

Why not think it as the default (we are in 2014 now after all) and check
when not supported ?

Reply to this email directly or view it on GitHubhttps://github.com//issues/36#issuecomment-35059653
.

[XorfacX]

That's what i meant: default support and fallback when needed.
The title of the ticket was suggesting the opposite.

By the way which compiler do not implement it yet ?

XorfacX
http://www.fairydwarves.com

[asmodehn]

Visual 2013, at least.
http://msdn.microsoft.com/en-us/library/hh567368.aspx

Gcc is almost there, but the 2014 standard will come out sometime soon so...
http://gcc.gnu.org/projects/cxx0x.html

Actually wkcmake will have to move to cmake 3.0 since it includes macros to
detect c++11 features...
That should probably be the first step.

Cmake 3.0 will be out soon, there are no remaining bugs to be fixed for the
released. It was planned to go out early february....
On Feb 15, 2014 5:29 PM, "XorfacX" [email protected] wrote:

That's what i meant: default support and fallback when needed.
The title of the ticket was suggesting the opposite.

By the way which compiler do not implement it yet ?

XorfacX
http://www.fairydwarves.com http://www.anno1777.com/index.php?i=235232

On Fri, Feb 14, 2014 at 10:53 AM, AlexV [email protected] wrote:

I agree for most software. However many compilers do not implement it
completely yet... and in that case we should provide a fallback behavior.

So we will have anyway multiple fallbacks behavior in code... which means
the build system needs to detect and pick the fallback behaviors we need
when we need them.

That is the job of wkcmake, so it still has to know about multiple
versions
of c++...
On Feb 14, 2014 3:27 PM, "XorfacX" [email protected] wrote:

Why not think it as the default (we are in 2014 now after all) and
check
when not supported ?

Reply to this email directly or view it on GitHub<
https://github.com/asmodehn/wkcmake/issues/36#issuecomment-35059653>
.

Reply to this email directly or view it on GitHub<
https://github.com/asmodehn/wkcmake/issues/36#issuecomment-35070083>
.

Reply to this email directly or view it on GitHubhttps://github.com//issues/36#issuecomment-35150278
.

[XorfacX]

Thanks for those links, very interesting.
Here is the one for Intel compiler http://software.intel.com/en-us/articles/c0x-features-supported-by-intel-c-compiler