> On May 7, 2014, at 11:11 PM, Michael Povolotskyi <mpovo...@purdue.edu> wrote: > > may be I'm using the old version, > but enum_solver_package.h > has a statement > using namespace libMeshEnums; > (the last line before #endif) > > Is this okay?
This is an old version, enums are no longer in the libMeshEnums namespace. > >> On 5/7/2014 4:07 PM, John Peterson wrote: >> >> >> >>> On Wed, May 7, 2014 at 1:58 PM, Michael Povolotskyi <mpovo...@purdue.edu> >>> 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 Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
