Oops - didn't reply all
---------- Forwarded message ----------
From: Derek Gaston <fried...@gmail.com>
Date: Thu, Sep 13, 2012 at 10:53 AM
Subject: Re: [Libmesh-devel] header file path safety
To: "Paul T. Bauman" <ptbau...@gmail.com>
On Thu, Sep 13, 2012 at 10:48 AM, Paul T. Bauman <ptbau...@gmail.com> wrote:
> I haven't complained, but I've already hit several cases where I had to
> rename my own header file because it collided with a libMesh header name.
> This would fix any further possibilities of this happening.
>
Hmmm.... that would also mean that you would have a class name that is
similar / the same as a libmesh class name. Do you not use "using
namespace libmesh" ? 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... so
that name probably wouldn't have worked out very well anyway...
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...
Derek
------------------------------------------------------------------------------
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
