From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit/hpux] Obsolete some definitions only used for hppa-pro
Date: Tue, 22 Apr 2003 18:15:00 -0000 [thread overview]
Message-ID: <20030422181522.GD914@gnat.com> (raw)
In-Reply-To: <3EA57465.9020102@redhat.com>
> Just fyi:
> // OBSOLETE
> has a little evilness behind it - it's C++ not ISO C 90. GDB gets way
> with it by either using:
>
> #if 0
> // OBSOLETE ...
> #endif
>
> or just applying it to the entire file.
>
> Oh, and if something can be simplified by removing a value/macro only
> defined in obsolete code then it's a real option. The person that tries
> to resurect that obsolete target will need to re-write the section anyway.
Ah, ok. I thought this C++-ism was tolerated for obsolete declarations.
But this was just nonsense, now that I think of it. I shall fix
momentarily and send a new patch (will also take your recommendation
to delete the code).
Thanks!
--
Joel
prev parent reply other threads:[~2003-04-22 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 1:16 Joel Brobecker
2003-04-22 16:57 ` Andrew Cagney
2003-04-22 18:15 ` 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=20030422181522.GD914@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