Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [commit] new observer.[hc] files
Date: Fri, 28 Feb 2003 15:22:00 -0000	[thread overview]
Message-ID: <20030228152256.GB23109@nevyn.them.org> (raw)
In-Reply-To: <20030228072243.GD6112@gnat.com>

On Thu, Feb 27, 2003 at 11:22:43PM -0800, Joel Brobecker wrote:
> As requested by Andrew in:
> http://sources.redhat.com/ml/gdb-patches/2003-02/msg00773.html
> 
> I checked the attached files in. There have slightly been modified from
> the file originally sent: added the copyright headers, some documentation,
> introduced the notion of subject from the "Design Patterns" book, added
> a missing "static" keyword for an internal function, etc.

> /* The internal generic observer.  */
> 
> typedef void (generic_observer_notification_ftype) (const void *data,
> 						    const void *args);
> 
> struct observer
> {
>   generic_observer_notification_ftype *notify;
>   /* No memory management needed for the following field for now.  */
>   void *data;
> };

> static void
> observer_normal_stop_notification_stub (const void *data,
> 					const void *unused_args)
> {
>   observer_normal_stop_ftype *notify = (observer_normal_stop_ftype *) data;
>   (*notify) ();
> }

Is this extra indirection really necessary?  Because I'm 99% sure it
won't work on several 64-bit platforms.  Function pointers and data
pointers are not required to have the same size; on IA-64 I believe
that a function pointer is 128 bits and a data pointer is 64 bits.

Why not require all observer functions to take the same arguments
instead?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-02-28 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-28  7:38 Joel Brobecker
2003-02-28 15:22 ` Daniel Jacobowitz [this message]
2003-02-28 16:10   ` Andreas Schwab
2003-02-28 16:14   ` Andrew Cagney
2003-02-28 16:39     ` Daniel Jacobowitz

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=20030228152256.GB23109@nevyn.them.org \
    --to=drow@mvista.com \
    --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