This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
RE: excessive stab information
- From: "Andy Chittenden" <AChittenden at bluearc dot com>
- To: "Dave Korn" <dave dot korn at artimi dot com>,"Daniel Jacobowitz" <drow at false dot org>,"Ian Lance Taylor" <ian at airs dot com>
- Cc: <binutils at sourceware dot org>,"Martin Dorey" <mdorey at bluearc dot com>
- Date: Thu, 28 Apr 2005 16:49:37 +0100
- Subject: RE: excessive stab information
> Why don't you sort out the search path in the makefile so that the
> publishing library also finds the public interface header
> first? That would
> be good practice and achieve the desired consistency.
>
'cos it doesn't work. Consider the case where we have a directory that
publishes bar.h to foo/bar.h. In the source directory, the cpp files
#include "bar.h". In other directories, users #include "foo/bar.h". If
the source file was also #including a currently private header file
"fred.h", that header file can be published later without the need to
change existing source.
Your suggestion does give rise to the possibility of putting the root of
our tree in the #include path but then we don't get the benefit of
published/not published headers.
--
Andy, BlueArc Engineering