From: Daniel Jacobowitz <drow@false.org>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: Pierre Muller <muller@ics.u-strasbg.fr>,
gdb-patches@sourceware.org, 'teawater' <teawater@gmail.com>
Subject: Re: [PATCH 3/4] catch syscall -- try 4 -- XML support
Date: Sun, 01 Feb 2009 19:45:00 -0000 [thread overview]
Message-ID: <20090201194551.GL4597@caradoc.them.org> (raw)
In-Reply-To: <1233146315.26873.58.camel@miki>
Pretty much OK.
On Wed, Jan 28, 2009 at 10:38:35AM -0200, Sérgio Durigan Júnior wrote:
> +<!-- The root element of a syscall info is <syscalls_info>. -->
> +
> +<!ELEMENT syscalls_info (syscall*)>
Sorry for the trouble, but please use "-" instead of "_".
> +<!-- Maybe the 'number' attribute will have to be changed from
> + ID to CDATA. -->
> +<!ELEMENT syscall EMPTY>
> +<!ATTLIST syscall
> + name CDATA #REQUIRED
> + number ID #REQUIRED>
Yeah, just use CDATA. Let's not mess with ID attributes; an ID of "1"
is not helpful if you want to embed this sort of document in another
one later.
> +<!ELEMENT xi:include (EMPTY)>
> +<!ATTLIST xi:include
> + xmlns:xi CDATA #FIXED "http://www.w3.org/2001/XInclude"
> + href CDATA #REQUIRED>
Delete this; we don't need xi:include support for system call lists,
and you don't call xml_process_xincludes anyway.
> +/* Open FILENAME, read all its text into memory, close it, and return
> + the text. If something goes wrong, return NULL and warn. */
> +
> +static char *
> +fetch_xml_from_file (const char *filename, void *baton)
Assuming this is identical to the one in xml-tdesc.c, give it a name
starting with xml and put it in xml-support.c instead please.
> +int
> +xml_number_of_syscalls (const struct syscalls_info *sysinfo)
> +{
> + return (sysinfo == NULL ? 0 : VEC_length(syscall_desc_p,
> + sysinfo->syscalls));
> +}
Space before paren.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2009-02-01 19:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 0:31 Sérgio Durigan Júnior
2009-01-26 8:33 ` Pierre Muller
2009-01-28 13:23 ` Sérgio Durigan Júnior
2009-02-01 19:45 ` Daniel Jacobowitz [this message]
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=20090201194551.GL4597@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--cc=sergiodj@linux.vnet.ibm.com \
--cc=teawater@gmail.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