Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: XML XInclude support
Date: Tue, 06 Feb 2007 12:49:00 -0000	[thread overview]
Message-ID: <20070206124910.GA31162@nevyn.them.org> (raw)
In-Reply-To: <usldo1jdf.fsf@gnu.org>

On Fri, Feb 02, 2007 at 08:53:32PM +0200, Eli Zaretskii wrote:
> > +  /* Simple, portable version of dirname that does not modify its
> > +     argument.  */
> > +  base = lbasename (filename);
> > +  while (base > filename && IS_DIR_SEPARATOR (base[-1]))
> > +    --base;
> 
> I'm glad to see portable file-name handling, but this loop needs a
> small extra to not fail in the case of "d:foo".

Does it?  lbasename ("d:foo") will return a pointer to the 'f'.  At
that point base > filename is true, but IS_DIR_SEPARATOR is false,
so we use "d:" as the directory name.  If that's wrong, I don't know
enough about DOS based filesystems to know why.

> I'd suggest to use @var{document} instead of @var{name}, and reword
> the last sentence like this:

Is this better?

@noindent
When @value{GDBN} encounters an element of this form, it will retrieve
the named XML @var{document}, and replace the inclusion directive with
the contents of that document.  If the current description was read
using @samp{qXfer}, then so will be the included document;
@var{document} will be interpreted as the name of an annex.  If the
current description was read from a file, @value{GDBN} will look for
@var{document} as a file in the same directory where it found the
original description.


-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-02-06 12:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-29 21:32 Daniel Jacobowitz
2007-01-31 18:33 ` Daniel Jacobowitz
2007-02-02 18:53 ` Eli Zaretskii
2007-02-06 12:49   ` Daniel Jacobowitz [this message]
2007-02-07 18:16     ` Eli Zaretskii
2007-02-07 18:37       ` Daniel Jacobowitz
2007-02-07 18:45         ` Daniel Jacobowitz
2007-02-07 22:49           ` Daniel Jacobowitz
2007-02-08 13:06             ` Mark Kettenis
2007-02-08 13:14               ` Daniel Jacobowitz
2007-02-08 16:15                 ` Mark Kettenis
2007-02-08 13:57                   ` Daniel Jacobowitz
2007-02-06 13:03   ` Daniel Jacobowitz
2007-02-07 18:20     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070206124910.GA31162@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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