On Thu, Sep 13, 2012 at 11:53 AM, Derek Gaston <fried...@gmail.com> wrote:
>
> Hmmm.... that would also mean that you would have a class name that is
> similar / the same as a libmesh class name.
>
Yes, but this is why use namespace religiously.
> Do you not use "using namespace libmesh" ?
>
*NEVER* And I get really pissed when I include a library that does
something like that... *looks at Trilinos and its using namespace std*
> Because even with this change you still wouldn't be able to have a class
> name that is the same as a libmesh class name...
>
Yes, that's true, but again, this is why keeping things in a namespace is
nice. But I suppose there's some taste involved here.
>
> But I do see your point... I just wonder if the cure is worse than the
> disease. Let's make sure not to make the source structure of libmesh
> extremely painful just to fix something that comes up very rarely...
>
Agreed. This is why I didn't complain because it doesn't seem to be a
pervasive problem.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
