I thought I hit "reply all"... First post to this list :)
---------------------------------------- > From: marchy...@hotmail.com > To: royst...@ices.utexas.edu > Subject: RE: [Libmesh-users] libmesh problem: libmesh_nullptr was not > declared in scope > Date: Thu, 4 Aug 2016 17:32:52 -0400 > > I have not followed the exchange but sometimes I end up including headers > within a namespace or > something. Is libmesh being included within something? Not sure what that > does with some > macros and others not lol. > > fwiw, I just downloaded libmesh and visit a few days ago and was surprised > that I could > be tweaking examples with 2 days ( even though now I'm fumbling with line > integrals > to integrate a current density ) and see the results. Personally I will > probably end up using > R for most analysis but it will take a while to learn the filer formats > and what visit can actually do. > > I searched the mail list and only found maybe one or two old exchanges on > electrochemisty. > Curious if there are specific features for this or if anyone can comment on > usable dynamic > range of mesh refinement ( it seem if I had too fine a grid in places > it complained about some Newton-Raphson not converging or something similar). > There are places > where nanometers matter, other places centimeters and wasn't sure if there > were specific > classes or algorithms to know about. > > Thanks. > > > > ---------------------------------------- > Date: Thu, 4 Aug 2016 14:48:42 -0500 > From: royst...@ices.utexas.edu > To: harroontheg...@gmail.com > CC: libmesh-users@lists.sourceforge.net > Subject: Re: [Libmesh-users] libmesh problem: libmesh_nullptr was not > declared in scope > > > > 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 > ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
