Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Generate observer.[hc]
Date: Thu, 08 Apr 2004 22:40:00 -0000	[thread overview]
Message-ID: <4075D4D9.7000104@gnu.org> (raw)
In-Reply-To: <20040408222914.GA32726@nevyn.them.org>

> On Thu, Apr 08, 2004 at 05:09:34PM -0400, Andrew Cagney wrote:
> 
>>> Hello,
>>> 
>>> The attached adds the script observer.sh that can be used to generate:
>>> 	observer.h
>>> 	observer.ch (#included by observer.c)
>>> aat build time using doc/observer.texi as the input.
>>> 
>>> While this is more ambitious than gdbarch.* (which are explicitly 
>>> generated and then committed to CVS) I suspect it is prefered.
>>> 
>>> Comments?
>>> 
>>> Once this is in I can add a few observers, and start deleting all those 
>>> hooks and events.
> 
> 
> I like it, and the patch looks fine to me.  My only complaint is that I
> don't much like the .ch suffix.  But then, using .c is probably pretty
> confusing too, so I don't have a better idea - I won't complain.

So far I've been through .hh .cc .hc .ch ....

>>> -@deftypefun extern struct observer *observer_attach_normal_stop (observer_normal_stop_ftype *@var{f})
> 
> 
> Also, my instinct when reading this manual would be to just remove
> these obsolete "extern"s.  Which would break the script, since it would
> try to generate an event for observer_detach_@var{event}.  So I think
> that either that should be fixed or there should be a comment somewhere
> to leave them in.

Oops, thats the wrong example, try:

   +@deftypefun void normal_stop (struct bpstats *@var{bs})

(yes the externs can go)

Andrew



  reply	other threads:[~2004-04-08 22:40 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 [this message]
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
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=4075D4D9.7000104@gnu.org \
    --to=cagney@gnu.org \
    --cc=drow@false.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