Could it be the case that "/* Compiler supports nullptr, but it is disabled in libmesh */" means that libmesh can't use nullptr since it's disabled in libmesh, meaning that #define libmesh_nullptr can't be defined nullptr, because nullptr is disabled?
Harry Pearce On Thu, Aug 4, 2016 at 1:42 PM, Harry Pearce <harroontheg...@gmail.com> wrote: > Could it be the case that > "/* Compiler supports nullptr, but it is disabled in libmesh */" > means that libmesh can't use nullptr since it's disabled in libmesh, > meaning that #define libmesh_nullptr can't be defined nullptr, because > nullptr is disabled? > > Harry Pearce > > On Thu, Aug 4, 2016 at 12:48 PM, Roy Stogner <royst...@ices.utexas.edu> > wrote: > >> >> On Thu, 4 Aug 2016, Harry Pearce wrote: >> >> In regards to LIBMESH_HAVE_CXX11_NULLPTR it says: >>> >>> #ifndef LIBMESH_HAVE_CXX11_NULLPTR >>> #define LIBMESH_HAVE_CXX11_NULLPTR 1 >>> #endif >>> >> >> I'm utterly baffled then. If you include libmesh_nullptr.h (as all >> our headers do, indirectly!), then it should include libmesh_config.h >> to get that definition, it should test that definition and decide to >> #define libmesh_nullptr nullptr, and then your compiler shouldn't even >> *see* the term "libmesh_nullptr", because your preprocessor should >> have already substituted it. >> --- >> Roy > > > ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
