On Mon, Feb 18, 2013 at 1:55 PM, Roy Stogner <royst...@ices.utexas.edu>wrote:
> > On Mon, 18 Feb 2013, Subramanya Gautam Sadasiva wrote: > > > Thanks Benjamin, Roy. Let me try if that helps. > > Let us know if the --disable-rtti workaround succeeds for you? Ben > and John are probably correct that the best fix for "my compiler can't > always handle dynamic_cast" is "get a better compiler", but I'd like > for us to support the default on OSX too, and if the workaround I > suggested is sufficient then we should try to update our configure > tests to catch these cases and disable RTTI automatically. > So what happens if you call dynamic_cast or typeid when RTTI is disabled? I don't see how it can be other than undefined behavior... We (Roy) seems to have been pretty careful, but there are still some dynamic_casts and typeids running around in the library (adjoint_refinement_estimator.C and reference_counted_object.h) and there are some in nanoflann and getpot. These are probably just bugs waiting to happen, even if RTTI-disabled seems to work on some compilers, some of the time. Anyway, as I understand it, disabling RTTI is, by definition, non-standard. Can't quote chapter/verse of the standard, but this seems to be accepted as truth in most internet forums I've come across. So I vote that we not bend over backwards in trying to support this mode of operation :-/ -- John ------------------------------------------------------------------------------ The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
