From: Andrew Cagney <ac131313@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb@sources.redhat.com
Subject: Re: RFC: dummy.[hc] and ``struct dummy''
Date: Fri, 27 Sep 2002 11:20:00 -0000 [thread overview]
Message-ID: <3D94A16E.6010409@redhat.com> (raw)
In-Reply-To: <2427-Fri27Sep2002201112+0300-eliz@is.elta.co.il>
>> Date: Thu, 26 Sep 2002 18:47:11 -0400
>> From: Andrew Cagney <ac131313@redhat.com>
>>
>> I'd like to float the idea of moving all the generic dummy frame code
>> into a new file dummy.[hc].
>
>
> Yes, but I'd suggest to call the files something other than dummy.*,
> lest someone thinks they are junk ;-)
But then I can't have a function called ``dummy_spit()'' (OZ? expression
for blowing one's fuse).
More seriously, I'm struggling for a better name: ``generic'' ``gdf''
``dummy-frame'', ... I guess the last one?
Andrew
next prev parent reply other threads:[~2002-09-27 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 15:47 Andrew Cagney
2002-09-27 10:12 ` Eli Zaretskii
2002-09-27 11:20 ` Andrew Cagney [this message]
2002-09-27 11:21 ` Daniel Jacobowitz
2002-09-27 11:38 ` Elena Zannoni
2002-09-27 11:59 ` Kevin Buettner
2002-09-27 12:07 ` Andrew Cagney
2002-09-27 12:15 ` Elena Zannoni
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=3D94A16E.6010409@redhat.com \
--to=ac131313@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@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