From: Eli Zaretskii <eliz@gnu.org>
To: "Nelson H. F. Beebe" <beebe@math.utah.edu>
Cc: guile-devel@gnu.org
Subject: Re: Fix 'dirname' and 'basename' on MS-Windows
Date: Wed, 09 Jul 2014 19:49:31 +0300 [thread overview]
Message-ID: <834myqcw9w.fsf@gnu.org> (raw)
In-Reply-To: <CMM.0.95.0.1404918995.beebe@psi.math.utah.edu>
> Date: Wed, 9 Jul 2014 09:16:35 -0600 (MDT)
> From: "Nelson H. F. Beebe" <beebe@math.utah.edu>
> Cc: beebe@math.utah.edu
>
> >> 6. If the suffix operand is present, is not identical to the
> >> characters remaining in string, and is identical to a suffix of the
> >> characters remaining in string, the suffix suffix shall be removed
> >> from string. Otherwise, string is not modified by this step. It
> >> shall not be considered an error if suffix is not found in string.
> >> ...
>
> The phrase `is not identical to the characters remaining in string'
> means that ".bar" is the result, rather than "".
Any idea why does this exception make sense?
> Also, in guile documentation, would it not be better to replace "file
> name", "base name", FILENAME, and BASENAME with the standard POSIX
> terminology "pathname" and "filename"?
GNU Coding Standards frown upon using "path" for anything that is not
a PATH-style directory list. In GNU terminology, "filename" can be
both full (a.k.a. "absolute") and relative file names.
next prev parent reply other threads:[~2014-07-09 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 15:16 Fix 'dirname' and 'basename' on MS-Windows Nelson H. F. Beebe
2014-07-09 16:49 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-01 15:38 Windows file name separators Ludovic Courtès
2014-07-02 16:13 ` Fix 'dirname' and 'basename' on MS-Windows Eli Zaretskii
2014-07-09 14:22 ` Ludovic Courtès
2014-07-09 14:53 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834myqcw9w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=beebe@math.utah.edu \
--cc=guile-devel@gnu.org \
/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).