linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mbuesch@freenet.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH, UDEV] change no_trailing_slash() to remove all trailing slashes
Date: Sat, 05 Feb 2005 22:36:50 +0000	[thread overview]
Message-ID: <200502052336.56404.mbuesch@freenet.de> (raw)
In-Reply-To: <200502051818.54277.mbuesch@freenet.de>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

Quoting Paul Jackson <pj@sgi.com>:
> Michael wrote:
> > 	while (len > 0 && path[len-1] == '/')
> 
> I think you'd better make that:
> 
> 	while (len > 1 && path[len-1] == '/')
> 
> or else you can eat your last slash.
> 
> The call no_trailing_slash("/") should produce "/", not "".

Well, I would call that expected behaviour.
Consider the following:
char buf[SIZE];
strcpy(buf, "///");
no_trailing_slash(buf);
strcat(buf, "/foo/bar");

I would expect that to expand to "/foo/bar" and _not_
to "//foo/bar" as you suggest.

> Not that anyone is likely to call no_trailing_slash("////")
> very often ;).
> 

-- 
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]



[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-02-05 22:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-05 17:18 [PATCH, UDEV] change no_trailing_slash() to remove all trailing slashes Michael Buesch
2005-02-05 18:15 ` [PATCH, UDEV] change no_trailing_slash() to remove all Kay Sievers
2005-02-05 22:04 ` [PATCH, UDEV] change no_trailing_slash() to remove all trailing Paul Jackson
2005-02-05 22:36 ` Michael Buesch [this message]
2005-02-06  1:11 ` Paul Jackson
2005-02-06  9:54 ` [PATCH, UDEV] change no_trailing_slash() to remove all trailing slashes Michael Buesch

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=200502052336.56404.mbuesch@freenet.de \
    --to=mbuesch@freenet.de \
    --cc=linux-hotplug@vger.kernel.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 NNTP newsgroup(s).