🚀 go-pugleaf

Hi,

Shankar Unni (shankar@engr.sgi.com) wrote:
: This not so much a standards issue as a migration issue.
: 
: What do people think? Of the idea, of the actual names if they are in favor
: of the idea, of which features should there be corresponding macros for? ...

I had a short (private) discussion with J.Kanze about this issue and we
decided to promote something like this (probably in
comp.lang.c++.moderated if it gets created: The voting period finished
on thursday but I don't have the results yet...). However, since there
are existing compilers which do not support these macro definitions and
which should be usable with the macros, our approach does not need to
built such a facility into the compiler. Instead a header file (which
includes some other header files too) is provided which defines a set
of macros.

I worked out a (not yet finished...) proposal for such files (including
a tool to "guess" about features supported by a certain compiler). I have
currently no feedback from James whether he likes my approach. However, I
have put the stuff into my WWW area. Use

  http://www.informatik.uni-konstanz.de/~kuehl/c++/portdefs.h.html

as an entry point, if you want to have a look on it. You can also download
the current stuff from

  ftp://ftp.informatik.uni-konstanz.de/pub/algo/kuehl/port.tar.gz

via anonymous ftp. Note that it is still under constructions. Some
parts of it are currently somewhat inconsistent although operational (I
will fix this soon).

Suggestion, additions, corrections, etc. are highly welcome! Currently
I have put the code under the GPL just to make sure it can be used by
everybody. I'm willing to make the licensing terms even more liberal
(to make the code useful in commercial products too) but I don't have
the knowledge how to write such a license. Suggestions and help on this
would also be welcome.
--
dietmar.kuehl@uni-konstanz.de
http://www.informatik.uni-konstanz.de/~kuehl
I am a realistic optimist - that's why I appear to be slightly pessimistic

[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]