On the lack of manpower: (Apache stdcxx)
Though this isn't news, I just came across it and it speaks to our common problem. (And it's of interest to boost users in general.) Note that ARM and Sun are even invested in stdcxx to some extent. From Apache's C++ Standard Library project <http://stdcxx.apache.org/status/2011-02.txt>: Stdcxx continues to be dormant. All but [1] committer have moved on to other projects. The only remaining committer (the VP of the project) is too busy with his day job to make even small changes, or to put out the long-awaited patch release, stdcxx 4.2.2. A number of users and organizations have been using the project and expressed interest in contributing to it. Several submitted patches, others have offered help with the project build and test infrastructure. Unfortunately, since no committer is available to review patches and guide the contributors through the ASF process to enable them to gain commit privileges there seems to be little hope of reviving stdcxx. A possible solution that would allow contributions to resume is to grant commit privileges to the handful of contributors who have already submitted some patches or expressed serious interest in contributing going forward. Another alternative is to move stdcxx to a repository outside of ASF such as SPI (http://www.spi-inc.org/) where interested developers could start committing changes on their own right away, without going through the "training" process. This seems to the preferred solution among at least some of the interested users. Are there any other options? Future plans: Unless the issue with contributions can be resolved in the next quarter I suggest to retire the project.
On 01/06/2012 03:43 PM, Jim Bell wrote:
Though this isn't news, I just came across it and it speaks to our common problem. (And it's of interest to boost users in general.) Note that ARM and Sun are even invested in stdcxx to some extent.
Future plans:
Unless the issue with contributions can be resolved in the next quarter I suggest to retire the project.
Cannot libc++ replace whatever role stdcxx had?
On Fri, Jan 6, 2012 at 2:49 PM, Mathias Gaunard < mathias.gaunard@ens-lyon.org> wrote:
On 01/06/2012 03:43 PM, Jim Bell wrote:
Though this isn't news, I just came across it and it speaks to our common problem. (And it's of interest to boost users in general.) Note that ARM and Sun are even invested in stdcxx to some extent.
Future plans:
Unless the issue with contributions can be resolved in the next quarter I suggest to retire the project.
Cannot libc++ replace whatever role stdcxx had?
What is 'libc++'? I'm unsure of my ground here, but isn't any given libc++ specific to some (group of) vendors or platforms, whereas stdc++ sought to be cross platform and open source? - Rob.
On 01/06/2012 03:55 PM, Robert Jones wrote:
What is 'libc++'?
A BSD-licensed cross-platform standard C++11 library implementation. It is developed as part of the clang project, but is not supposed to be clang-specific. At least I believe those were the goals; I think it only works with clang on Mac OS X for now. (Note: it's the first hit on Google for 'libc++')
I'm unsure of my ground here, but isn't any given libc++ specific to some (group of) vendors or platforms, whereas stdc++ sought to be cross platform and open source?
libstdc++ is licensed under a GPL variant and is only meant to work with GCC.
On 6 January 2012 14:49, Mathias Gaunard <mathias.gaunard@ens-lyon.org> wrote:
On 01/06/2012 03:43 PM, Jim Bell wrote:
Future plans:
Unless the issue with contributions can be resolved in the next quarter I suggest to retire the project.
Cannot libc++ replace whatever role stdcxx had?
While researching possible support of Clang on Windows, I looked at the Apache stdcxx and wondered that if it was relicensed by Apache (moved outside) it could be merged (community-wise too) into libc++ for potential boost of the latter. ...loose thought Best regards, -- Mateusz Loskot, http://mateusz.loskot.net
On Fri, Jan 6, 2012 at 09:43, Jim Bell <Jim@jc-bell.com> wrote:
Though this isn't news, I just came across it and it speaks to our common problem. (And it's of interest to boost users in general.) Note that ARM and Sun are even invested in stdcxx to some extent.
From Apache's C++ Standard Library project <http://stdcxx.apache.org/status/2011-02.txt>:
Stdcxx continues to be dormant. All but [1] committer have moved on to other projects. The only remaining committer (the VP of the project) is too busy with his day job to make even small changes, or to put out the long-awaited patch release, stdcxx 4.2.2.
A number of users and organizations have been using the project and expressed interest in contributing to it. Several submitted patches, others have offered help with the project build and test infrastructure. Unfortunately, since no committer is available to review patches and guide the contributors through the ASF process to enable them to gain commit privileges there seems to be little hope of reviving stdcxx.
A possible solution that would allow contributions to resume is to grant commit privileges to the handful of contributors who have already submitted some patches or expressed serious interest in contributing going forward.
Wake-up call for the ASF. I have about 80+ patches for stdcxx (based on 4.2.1) which I wanted to submit to the project and which fix a not insignificant number of important bugs. I was willing to help with the integration of these patches into a new release, and with testing, having already tested Solaris and Linux, since it's my job anyway. Essentially, these patches would make stdcxx equal to the implementation available with the current Sun Studio C++ compilers and Solaris 10 and 11. I made these patches publicly available in June 2011 here: http://kdesolaris-svn.cvsdude.com/trunk/STDCXX/4.2.1/ But the ASF process bureaucracy around submitting the simplest patch makes it next-to impossible. It's really regrettable because stdcxx is a very nice implementation of C++2003. --Stefan -- Stefan Teleman KDE e.V. stefan.teleman@gmail.com
On 1:59 PM, Stefan Teleman wrote:
On Fri, Jan 6, 2012 at 09:43, Jim Bell<Jim@jc-bell.com> wrote:
...
From Apache's C++ Standard Library project <http://stdcxx.apache.org/status/2011-02.txt>:
... Several submitted patches, others have offered help with the project build and test infrastructure. Unfortunately, since no committer is available to review patches and guide the contributors through the ASF process to enable them to gain commit privileges there seems to be little hope of reviving stdcxx. ... Wake-up call for the ASF.
I have about 80+ patches for stdcxx (based on 4.2.1) which I wanted to submit to the project and which fix a not insignificant number of important bugs. I was willing to help with the integration of these patches into a new release, and with testing, having already tested Solaris and Linux, since it's my job anyway. Essentially, these patches would make stdcxx equal to the implementation available with the current Sun Studio C++ compilers and Solaris 10 and 11.
...
But the ASF process bureaucracy around submitting the simplest patch makes it next-to impossible.
It's really regrettable because stdcxx is a very nice implementation of C++2003.
Quite a shame: contributors seem to have wandered off in frustration. (That happens here, too.) stdcxx is an important project. Beyond being a cross-platform reference implementation with an amicable license, it gives you a complete set of Standard C++ Library documentation you can browse from your local disk -- very valuable.
participants (5)
-
Jim Bell -
Mateusz Loskot -
Mathias Gaunard -
Robert Jones -
Stefan Teleman