This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch to add snprintf/vsnprintf to libiberty [take 2]
> Well we prototype asprintf/vasprintf. I thought these would work
> similarly. I don't care, if you want I'll take them out. Just re-ack
> either way.
I'm just asking at the moment. It's a fairly new function, so OSs
implementing it are likely to have followed the spec, compared to
something pre-void or pre-size_t.
Unfortunately, we don't have a robust HAVE_ for prototypes.
> I have a blanket gcc assignment on file, I assumed that covered
> libiberty since I thought gcc is considered the "master" for that
> directory.
It tends to, but for some things put directly into libiberty that are
independent of gcc, a separate libiberty assignment is useful.
> WRT libstdc++-v3, I believe that GPL and/or LGPL files are not
> supposed to be linked into libstdc++-v3, which is why I said "public
> domain" cause Paolo wanted to use them. The other libiberty files
> linked into libstdc++-v3 all either have public domain, the berkeley
> license or no license. See the comment above the `NEEDED' variable in
> libiberty/Makefile.in.
We can do a GPL+exception license, similar to what libstdc++-v2 itself
uses.
Besides, a different type of disclaimer from your employer/school is
needed if you put things in the public domain, compared to assigning
them to the FSF. And if you are assigning it to the FSF, shouldn't
the FSF (via the SC) decide the license?
> > No embedded texinfo documentation?
>
> Sorry I didn't understand it. How does it work?
See libiberty/getcwd.c or libiberty/xmalloc.c
Configure with --enable-maintainer-mode and make will build
$srcdir/functions.texi from the source comments. You'll need perl.