This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Bikeshed discussion on name of library file for Filesystem TS
- From: Tim Shen <timshen at google dot com>
- To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
- Cc: "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Date: Wed, 24 Sep 2014 14:43:50 -0700
- Subject: Re: Bikeshed discussion on name of library file for Filesystem TS
- Authentication-results: sourceware.org; auth=none
- References: <CAH6eHdQj1qXciGn0ECWpa8jQ4wg+mcWFTMrzaz_02Jv6DrbOMQ at mail dot gmail dot com>
On Wed, Sep 24, 2014 at 2:22 PM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> I'm going to commit <experimental/filesystem> soon, and as previously
> explained, all the new code is in a separate archive, not in
> libstdc++.so.
>
> I think I called that archive libstdc++fs.a but it might be a good
> idea to discuss better names.
>
> * Should the name have libstdc++ or GNU in it somewhere, to
> distinguish our library from another implementation's? Or would it be
> better if different implementations used the same name, so users'
> makefiles are simpler?
>
> * Should the archive name indicate the TS contents are "experimental"
> (as the namespace and include path already do)?
>
> Some options include:
>
> libstdc++file.a
> libc++file.a
> libg++file.a
> libstdexpfile.a
> libexpfile.a
> libfilec++.a
libc++file.a may not be a good name, since libc++ is a different thing :)
--
Regards,
Tim Shen