Re: Where to put support for missing C++ C headers?

From: rwgk_at_[hidden]
Date: 2001-04-15 01:05:37

I like this, too. Thanks!
I am not up to spec with the boost naming conventions.
Currently I am using the directory name C++_C_headers
for the surrogate <cxxx> header files. Would it be
better to create
root/boost/compatibility/cpp_c_headers?
The corresponding name for the Python script used to
generate the headers would be
root/libs/compatibility/generate_cpp_c_headers.py.
OK?
Ralf

--- In boost_at_y..., "David Abrahams" <abrahams_at_m...> wrote:
> I like this. Do you need more input, Ralf?
> 
> -Dave
> ----- Original Message -----
> From: "Beman Dawes" <bdawes_at_a...>
> To: <boost_at_y...>; <boost_at_y...>
> Sent: Saturday, April 14, 2001 3:25 PM
> Subject: Re: [boost] Where to put support for missing C++ C headers?
> 
> 
> > At 06:22 PM 4/13/2001, David Abrahams wrote:
> >
> >  >I do not want to leave Ralf hanging, but I'm not sure what to 
tell him.
> > He
> >  >is making an important contribution to Boost.Python, and the 
generation
> > of
> >  >missing <cxxx> headers is a useful contribution to boost 
overall,
> >  >consistent
> >  >with our mission. Does anyone have an idea about this?
> >  >
> >  >Perhaps we should start with a web page on library 
compatibility, with
> >  >links to the new <limits> file for GCC and to Ralfs 
scripts/generated
> >  >files...
> >
> > Perhaps segregate the material in a Compatibility Library. 
Directory
> > location root/boost/compatibility/ for headers and
> > root/libs/compatibility/... for everything else.
> >
> > Say up front in the index.html file that we hope these libraries 
can be
> > removed at some time in the future.  But that until standard 
library
> > suppliers become more standard conforming, we supply workarounds 
which
> > allow Boost to be used on otherwise non-conforming platforms.
> >
> > --Beman
> >
> >
> > To unsubscribe, send email to: <mailto:boost-unsubscribe_at_y...>
> >
> >
> > Your use of Yahoo! Groups is subject to 
http://docs.yahoo.com/info/terms/
> >
> >