From: James Curran/MVP (jamescurran_at_[hidden])
Date: 2001-12-27 23:15:44
>> 4) After inclusion in boost, SigC++ will live on as an LGPL
component
>> until such time at it makes the stl standard. Which
>> means contributions to it will not necessarily go back to boost
>> if done by someone other than myself.
>This may be a maintenance nightmare, but it's not the first time this
has
>come up. Loki would have the same problem, and I'm sure we'd find a way
to
>deal with it.
Um... Don't we already have (and are dealing with) that problem
with thing like heap_map<> being added to the HP/SGI/AT&T STL after it
was made part of the C++ Standard?
Truth,
James Curran