From: DJ Delorie <dj@redhat.com>
To: neil@daikokuya.demon.co.uk
Cc: dave@hiauly1.hia.nrc.ca, gcc-patches@gcc.gnu.org
Subject: Re: cpplib: basename () fix
Date: Mon, 05 Mar 2001 12:03:00 -0000 [thread overview]
Message-ID: <200103052002.PAA31318@greed.delorie.com> (raw)
In-Reply-To: <20010305195511.C30317@daikokuya.demon.co.uk>
"back when" we talked about libiberty documentation. One of the
things that would be documented is what functionality you *can* rely
on in functions such as basename, where we use the libc version if it
has one. Such documentation would then indicate that calling basename
with an empty string or empty final component is not well defined.
If we wanted to be anal about it, we could modify our implementation
to abort if you passed it a parameter that caused undefined behavior.
Then we'd be sure that people using such functions aren't going to be
surprised later.
I wouldn't recommend "gcc_" as a prefix, because libiberty is used in
a lot of things other than gcc. "gnu_" would be better, but
"libiberty_" would be more precise.
next prev parent reply other threads:[~2001-03-05 12:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-04 8:24 John David Anglin
2001-03-05 11:40 ` DJ Delorie
2001-03-05 11:56 ` Neil Booth
2001-03-05 12:03 ` DJ Delorie [this message]
2001-03-05 13:01 ` John David Anglin
2001-03-05 13:20 ` DJ Delorie
2001-03-05 14:15 ` John David Anglin
2001-03-05 14:21 ` DJ Delorie
2001-03-05 14:40 ` John David Anglin
2001-03-05 14:54 ` Neil Booth
2001-03-05 15:08 ` John David Anglin
2001-03-05 15:15 ` Neil Booth
2001-03-05 15:25 ` John David Anglin
2001-03-05 15:16 ` DJ Delorie
2001-03-05 15:57 ` John David Anglin
2001-03-05 16:14 ` Raja R Harinath
2001-03-05 17:17 ` John David Anglin
[not found] <no.id>
2001-03-04 10:11 ` John David Anglin
2001-03-06 10:07 ` John David Anglin
2001-03-06 10:29 ` DJ Delorie
2001-03-06 10:32 ` Zack Weinberg
2001-03-06 10:52 ` John David Anglin
2001-03-06 11:16 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2001-03-04 8:34 Mark E.
2001-03-04 7:08 Neil Booth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200103052002.PAA31318@greed.delorie.com \
--to=dj@redhat.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gcc-patches@gcc.gnu.org \
--cc=neil@daikokuya.demon.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).