Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org,
	gcc-patches@gcc.gnu.org
Subject: Re: [gdb/libiberty] Improve support for cross debugging shared libraries with DOS style pathnames (from Unix hosts)
Date: Fri, 23 Apr 2010 14:30:00 -0000	[thread overview]
Message-ID: <83mxwu2qd4.fsf@gnu.org> (raw)
In-Reply-To: <201004231113.o3NBDS94030996@glazunov.sibelius.xs4all.nl>

> Date: Fri, 23 Apr 2010 13:13:28 +0200 (CEST)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: gdb-patches@sourceware.org, eliz@gnu.org, gcc-patches@gcc.gnu.org
> 
> > > Please don't use "path" when you really mean "file name".  It's
> > > confusing; "path" should be reserved for lists of directories such as
> > > PATH or INFOPATH.
> > 
> > Oh.  I really meant a "path", as in:
> > 
> >  "A path, the general form of a filename or of a directory name,
> >  specifies a unique location in a file system."
> > 
> >  (From <http://en.wikipedia.org/wiki/Path_%28computing%29>.)
> > 
> > I suppose that's why we have IS_ABSOLUTE_PATH, and not IS_ABSOLUTE_FILE_NAME,
> > and such.
> > 
> > IMO, it's the use of singular path or "search path" to mean
> > "list of directories" that's overloaded.
> > "Set assumed file system kind for target reported file names"
> > kind of sounds like it is only talking about the filename "/dir1/dir2/files1"
> > (or directory and filenames, if you think of a directory a file as well).
> > Maybe I could just get rid of the mention of paths/file names, and go with:
> > 
> >   "Set the assumed file system kind of the target."
> > 
> > Anyway, I'll change it to what you think is clearer.
> 
> I think that depends on whether you're coming from a UNIX environment
> or a DOS environment.  To me (not really having used DOS for two
> decades) path is perfectly clear and acceptable.

From standards.info, node "GNU Manuals":

       Please do not use the term "pathname" that is used in Unix
    documentation; use "file name" (two words) instead.  We use the term
    "path" only for search paths, which are lists of directory names.

You can hardly say that RMS comes from a DOS environment, can you?


  reply	other threads:[~2010-04-23 14:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22 17:24 Pedro Alves
2010-04-22 17:46 ` Daniel Jacobowitz
2010-04-23  8:54 ` Eli Zaretskii
2010-04-23 10:46   ` Pedro Alves
2010-04-23 11:15     ` Mark Kettenis
2010-04-23 14:30       ` Eli Zaretskii [this message]
2010-04-23 15:41         ` Mark Kettenis
2010-04-23 14:35     ` Eli Zaretskii
2010-04-24 11:18       ` Pedro Alves
2010-04-24 11:40         ` Eli Zaretskii
2010-04-24 13:13           ` Pedro Alves

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=83mxwu2qd4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --cc=pedro@codesourcery.com \
    /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