From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add some code in observer.c to allow unit-testing
Date: Tue, 18 Mar 2003 18:07:00 -0000 [thread overview]
Message-ID: <20030318180704.GS16507@gnat.com> (raw)
In-Reply-To: <3E773D7F.2010003@redhat.com>
> Long term, it's going to run into -Wunused-function. Suggest adding a
> disclaimer pointing out this limitation :-)
Sure, I added the following comment:
/* Since this code will not be used within GDB, it will trigger
a warning if we decide to compile with -Wunused-function.
This is ok for now. (brobecker 2003-03-18) */
> Otherwize (for want of any beter idea :-), ok.
Checked in, with the above addition.
Thanks,
--
Joel
prev parent reply other threads:[~2003-03-18 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 2:09 Joel Brobecker
2003-03-18 15:38 ` Andrew Cagney
2003-03-18 18:07 ` Joel Brobecker [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=20030318180704.GS16507@gnat.com \
--to=brobecker@gnat.com \
--cc=ac131313@redhat.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