From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23754 invoked by alias); 28 Apr 2005 15:50:53 -0000 Mailing-List: contact binutils-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sources.redhat.com Received: (qmail 23256 invoked from network); 28 Apr 2005 15:50:16 -0000 Received: from unknown (HELO us-mimesweeper.terastack.bluearc.com) (63.203.197.133) by sourceware.org with SMTP; 28 Apr 2005 15:50:16 -0000 Received: from uk-email.terastack.bluearc.com (UK-EMAIL.terastack.bluearc.com) by us-mimesweeper.terastack.bluearc.com (Clearswift SMTPRS 5.0.9) with ESMTP id ; Thu, 28 Apr 2005 08:50:01 -0700 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: excessive stab information Date: Thu, 28 Apr 2005 16:02:00 -0000 Message-ID: <89E85E0168AD994693B574C80EDB9C2701D6A3E2@uk-email.terastack.bluearc.com> From: "Andy Chittenden" To: "Dave Korn" , "Daniel Jacobowitz" , "Ian Lance Taylor" Cc: , "Martin Dorey" X-SW-Source: 2005-04/txt/msg00856.txt.bz2 > Why don't you sort out the search path in the makefile so that the > publishing library also finds the public interface header=20 > first? That would > be good practice and achieve the desired consistency. >=20 '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. --=20 Andy, BlueArc Engineering