From mboxrd@z Thu Jan 1 00:00:00 1970 From: hjl@lucon.org (H.J. Lu) To: jbuck@synopsys.com (Joe Buck) Cc: law@cygnus.com, rittle@comm.mot.com, egcs@cygnus.com Subject: Re: Implications of tighter integration of libg++ Date: Mon, 09 Feb 1998 14:46:00 -0000 Message-id: References: <199802091739.JAA10303@atrus.synopsys.com> X-SW-Source: 1998-02/msg00380.html > > > > > It is desirable to place libraries compiled against and dependent upon > > > a given version of g++, and their related header files, into the > > > compiler's lib and include directory. > > Yes, but once we have complete standards conformance, we should get to the > point where libstdc++ always has the exact same API, so this kind of Did you mean ABI or API? With the old g++, API might be the same. But ABI changed. I was talking about vtable and name mangling. > dependency doesn't really exist. I think that the compiler-specific > lib directory really makes sense only for static libraries, not shared > libraries. > > > -- H.J. Lu (hjl@gnu.org)