Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Generate observer.[hc]
Date: Fri, 16 Apr 2004 06:59:00 -0000	[thread overview]
Message-ID: <6654-Fri16Apr2004095441+0300-eliz@gnu.org> (raw)
In-Reply-To: <407E9FEE.1040906@gnu.org> (message from Andrew Cagney on Thu, 15 Apr 2004 10:45:02 -0400)

> Date: Thu, 15 Apr 2004 10:45:02 -0400
> From: Andrew Cagney <cagney@gnu.org>
> > 
> > let me play the Devil's
> > advocate and ask what significant wins we gain from generating the
> > source files from the Texinfo file, that justify maintaining the
> > scripts which are required to support this machinery?
> 
> We first establish a one-stop shop for adding observers, and second 
> eliminate the drudgery of churning out the C code needed to implement 
> each observer.

That much is understood, but I still have a difficulty to see how
inventing an elaborate machinery for churning C code out of Texinfo
(which is hardly a trivial Sed'ery) is justified by the benefits you
mentioned.  I thought perhaps there were other, subtler, benefits
which I didn't see.  Are there?

> (At a guess, we're going to end up with something between 10 and 20
> observers).

So what, we will have all of them in the docs?


  reply	other threads:[~2004-04-16  6:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 21:09 Andrew Cagney
2004-04-08 22:29 ` Daniel Jacobowitz
2004-04-08 22:40   ` Andrew Cagney
2004-04-08 22:44     ` David Carlton
2004-04-08 22:45     ` Daniel Jacobowitz
2004-04-15 11:57 ` Eli Zaretskii
2004-04-15 14:45   ` Andrew Cagney
2004-04-16  6:59     ` Eli Zaretskii [this message]
2004-04-16 18:56       ` Andrew Cagney
2004-04-17  7:44         ` Eli Zaretskii
2004-04-15 14:32 ` Andrew Cagney

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=6654-Fri16Apr2004095441+0300-eliz@gnu.org \
    --to=eliz@gnu.org \
    --cc=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.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