stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <>
Subject Re: STDCXX progress to graduation
Date Fri, 22 Jun 2007 00:23:32 GMT
Noel J. Bergman wrote:
> William A. Rowe, Jr. wrote:
>> diversity is increasing (we wish it were broader, but I suspect this
>> project with the visibility of full ASF status will attract additional
>> committers who might have been hedging their bets on whether or not
>> the project would survive incubation.)
> What effect do you believe GPLv3 will have, now that the FSF is acknowledging 
> that GPL projects may freely take advantage of Apache Licensed code?

I suspect most GPL authors already felt quite free to combine and ship
AL code in their GPL developer toolchains, when useful.  Most J2 stacks
haven't bothered to replace every .jar, they consume AL libraries when
it suits their purpose.

It would be really cool to see some of the FLOSS C++ groups to both
consume and contribute to stdcxx, we'll see what happens.  As far as
other packagers blending proprietary and open source solutions, the
very nature of an 'incubating' ASF project says we don't yet give it
our full confidence, so a packager is behind the curve to rely on any
project until it's graduated.  We'll learn what the real delta is some
year after stdcxx has graduated.

>> things are as quiet as expected for a mature implementation of
>> a reference standard.
> Any concern that because of the maturity, it could stagnate and lose community?

Not at this time.  Because it is widely deployed, there will be a long
term demand.  Because it's transparent to the developer, and in debugging
their apps they can drill right into flaws within stdcxx, I suspect we
will see bug feedback folks turn patchers turn contributors turn project
members for years, as long as C++ is a widely adopted language.


View raw message