bugfix : c++11 on xcode

[elliotwoods]

Hey all!

[EDIT]
It seems that we don't have c++11 support right now with on osx.
The issue primarily is that we have to use libc++ with c++11, which does not support legacy tr1 namespace symbols. To fix this bug we need to write a c++11 version which does not use tr1 namespace.

This could either involve:

1. Writing a win/linux/mac C++11 implementation without tr1
2. Writing a special implementation for libc++ without tr1 for osx

I think the only difference between 1 and 2 is more testing is required for 1. (i.e. the code should look identical).

[/EDIT]

In ofTypes I edited:

#if (_MSC_VER)
#include <memory>
#else
#include <tr1/memory>
// import smart pointers utils into std
namespace std {
    using std::tr1::shared_ptr;
    using std::tr1::weak_ptr;
    using std::tr1::static_pointer_cast;
    using std::tr1::dynamic_pointer_cast;
    using std::tr1::const_pointer_cast;
    using std::tr1::enable_shared_from_this;
    using std::tr1::__dynamic_cast_tag;
}
#endif

to:

#if (_MSC_VER || true) // <----basically hacked here
#include <memory>
using std::shared_ptr;
#else
#include <tr1/memory>
// import smart pointers utils into std
namespace std {
    using std::tr1::shared_ptr;
    using std::tr1::weak_ptr;
    using std::tr1::static_pointer_cast;
    using std::tr1::dynamic_pointer_cast;
    using std::tr1::const_pointer_cast;
    using std::tr1::enable_shared_from_this;
    using std::tr1::__dynamic_cast_tag;
}
#endif

now i get complaints on __dynamic_cast_tag. And ran out of google results. ideas?

/Volumes/SHARED/openFrameworks/libs/openFrameworks/types/ofTypes.h:169:36: No type named '__dynamic_cast_tag' in namespace 'std'

[bilderbuchi]

I'd start with this interesring if statement: #if (_MSC_VER || true) ;-) you can never enter the else clause.
also, pinging @LeoColomb about this, I think he was the author of this passage.
edit: wait, what? hmmm

[elliotwoods]

:) that's the bit i hacked
basically the VS2012 code seems to be proper C++11, whilst the rest is using tr1
therefore the switch should really be looking for C++11, not vs2012

[bilderbuchi]

the switch should really be looking for C++11, not vs2012

on a second look I think I agree. but wouldn't the "proper" hack be to test for C++11 instead of true? :-)
also, @tgfrerer could know what's the proper course here.

[bilderbuchi]

shot in the dark: could be a libc++ thing? http://stackoverflow.com/questions/7016730/compiling-with-clang-using-libc-undefined-references

[bilderbuchi]

wait, something is iffy. in your "original" version, where's the #if __cplusplus<201103L clause which is in current develop?

[elliotwoods]

ooh! i thought i was on recent develop since yesterday. i must have missed something. trying now!

[bilderbuchi]

OK possibly the problem here is just the tr1/memory include, which I think needs to select for C++11. Probably like this

#if __cplusplus < 201103L
#include <tr1/memory>
#else
#include <memory>
#endif

or so.

[elliotwoods]

to notes
__cplusplus < 201103L == true on xcode/libc++ c++11

[EDIT]
This is only true when using stdlibc++ becuase that doesn't have c++11 support. So this statement isn't entirely correct.
[/EDIT]

[bilderbuchi]

what's the actual value of __cplusplus?

[elliotwoods]

the new code still doesn't work, also we shouldn't be using tr1 at all

#if __cplusplus<201103L
    using std::tr1::shared_ptr;
    using std::tr1::weak_ptr;
    using std::tr1::enable_shared_from_this;
#endif
    using std::tr1::static_pointer_cast;
    using std::tr1::dynamic_pointer_cast;
    using std::tr1::const_pointer_cast;
    using std::tr1::__dynamic_cast_tag;
}

still doesn't have a c++11 code path

[elliotwoods]

answers here to __cplusplus: http://stackoverflow.com/questions/12865226/in-xcode-4-5-what-is-compiler-default-for-c-standard-library-and-c-lan

[bilderbuchi]

It could be that this worked for now (i.e. with C++11 and stdlibc++) because according to the article I linked above, "Some standard library vendors have maintained the tr1 header files for backwards compatibility. Other vendors (such as libc++, which being c++11 only, has no backwards compatibility to worry about) do not."
So now that you are using libc++ this may have gotten exposed.

[bilderbuchi]

answers here to __cplusplus

that's not really an answer, though. what do you get when you run the program given in the accepted answer? for kicks, could you add a std::cout << __cplusplus << std::endl;, from here?

[elliotwoods]

I have to setup a separate app (oF wont run in this configuration), and the result is 201103, which tallies with what we're currently using.

[elliotwoods]

to confirm, libc++ is required for using std::function.