From: "Jim Blandy" <jimb@red-bean.com>
To: "Randolph Chung" <randolph@tausq.org>
Cc: gdb@sources.redhat.com
Subject: Re: RFC: getting rid of deprecated_hp_som_som_object_present
Date: Thu, 02 Mar 2006 05:57:00 -0000 [thread overview]
Message-ID: <8f2776cb0603012157t13a0c38dy64455acbabddbd23@mail.gmail.com> (raw)
In-Reply-To: <4405B9C0.90505@tausq.org>
On 3/1/06, Randolph Chung <randolph@tausq.org> wrote:
> Any thoughts? Is this even worth touching/fixing?
"Worth"? I'm always tempted to assess the "worth" of a project by how
ugly what it would fix is... :) I think that global variable is
really terrible. And as the Modula-2 example showed, the change is
getting propagated around.
Given that C99 specifies that enum values are ints, would it make
sense to always print enum values specially if the the enum type's
size is not equal to that of builtin_type_int?
next prev parent reply other threads:[~2006-03-02 5:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 15:12 Randolph Chung
2006-03-02 5:57 ` Jim Blandy [this message]
2006-08-02 2:55 ` Is anyone using the HP compilers on PA-RISC with FSF GDB? Daniel Jacobowitz
2006-08-04 5:00 ` Albert Chin
2006-08-04 12:50 ` Daniel Jacobowitz
2006-08-11 15:54 ` Albert Chin
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=8f2776cb0603012157t13a0c38dy64455acbabddbd23@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gdb@sources.redhat.com \
--cc=randolph@tausq.org \
/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