Re: dropping sigc++

On Mon, 17 Jan 2005, Phil wrote:

> James Harr wrote:
> > How do the need for c++, sigc++, and autoconf relate at all?
>
> You need a C++ compiler to build libsigc++ and those parts of Y which
> use it.  Autoconf shouldn't need C++, but Y's configure script will
> check for a C++ compiler.

That's mostly due to the current state of Y.  Y's only client library is
the C++ one, so to get a functional version you need C++.

In the Distant Future, Y will have different client libraries, so
configure will probably let you say --without-c++-library if you don't
have/want C++.  Maybe it'll even automagically detect its presence.

Before people start jumping to implement a c/perl/python/... client
library, can I just suggest we keep it simple for now and just stick to
the c++ one.  I've rewritten the C++ client lib once, and Andrew did it
another time. I'd rather not have to repeat that work N times.  (Of
course, if you really want to do it, then you're welcome to maintain it
yourself).

Regards,

  Mark.
-- 
|| Mark Thomas
|| efaref.net
||
|| Lottery: a tax on people who are bad at math.