Hello John,
I looked deeper into the problem:
In a file parallel_implementation.h there are lines:
173 // Anonymous namespace for helper functions
174 namespace {
175
176 // Safe to use this here since it won't "infect" anything outside the
177 // anonymous namespace
178 using namespace libMesh;
179However, the following resource http://stackoverflow.com/questions/8775563/using-namespace-statement-inside-an-anonymous-namespace tells that that "using" inside an anonymous namespace is not safe. And I see the same in my system. what do you think? Michael. On 5/7/2014 4:07 PM, John Peterson wrote: > > > > On Wed, May 7, 2014 at 1:58 PM, Michael Povolotskyi > <[email protected] <mailto:[email protected]>> wrote: > > Dear Libmesh developers, > I see that the header files of libmesh include the following > statements: > using namespace libMesh; > > > Only if you configure with --enable-legacy-using-namespace: > > #ifndef LIBMESH_REQUIRE_SEPARATE_NAMESPACE > using namespace libMesh; > #endif > > This should not be on by default any more. > > > This statement causes conflicts between the symbols defined in the > libMesh namespace and my own classes. > > > Is it possible to avoid "using" in the header files? > > > If you are using a recent version of libmesh, you shouldn't have to do > anything... > > -- > John ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
