From: Daniel Berlin <dan@www.cgsoftware.com>
To: "John S. Kallal" <jskallal@home.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: Is GDB using TYPEDEF identifiers?
Date: Thu, 21 Jun 2001 20:20:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0106212317110.21748-100000@www.cgsoftware.com> (raw)
In-Reply-To: <01062113244301.01467@CyberMax>
On Thu, 21 Jun 2001, John S. Kallal wrote:
> I think that POSIX reserves all identifiers defined with a typedef statement
> that that end with the characters "_t" for use within the POSIX header files.
> I note that the GDB source code uses a lot a such identifiers. Should
> we change to another suffix such as "_td" and document that requirement
> in the GDB coding rules within file 'gdbint.texinfo'?
Um, why?
POSIX says a lot of things that are well, dumb.
This is just one of them.
Besides, GDB is not beholden to POSIX.
When the C 'XX standard says not to do it, we'd probably stop doing it.
--Dan
next prev parent reply other threads:[~2001-06-21 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 10:21 John S. Kallal
2001-06-21 20:20 ` Daniel Berlin [this message]
2001-06-22 1:32 ` Eli Zaretskii
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=Pine.LNX.4.33.0106212317110.21748-100000@www.cgsoftware.com \
--to=dan@www.cgsoftware.com \
--cc=gdb@sources.redhat.com \
--cc=jskallal@home.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