Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <chastain@cygnus.com>
To: gdb@sources.redhat.com, jskallal@home.com
Subject: Re: Is GDB using reserved TYPEDEF identifiers? [REPOST]
Date: Sat, 23 Jun 2001 21:15:00 -0000	[thread overview]
Message-ID: <200106240415.VAA19378@bosch.cygnus.com> (raw)

John Kallal writes:

> 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.

The C standard (ISO/IEC 9899:1999) does not reserve these names,
but the Single Unix Specification does reserve all names with the
suffix "_t".  Here's the reference:

  http://www.opengroup.org/onlinepubs/7908799/xsh/compilation.html

> 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'?

That's up to the head maintainer.

My opinion is that we should do nothing until someone demonstrates
an actual problem on a specific configuration (specific host system,
specific Ansi C compiler, specific host triple, specific target triple).

It's a triage problem.  There's plenty of other work that yields
more benefit for less effort.

Michael Elizabeth Chastain
<chastain@redhat.com>
"love without fear"


             reply	other threads:[~2001-06-23 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-23 21:15 Michael Elizabeth Chastain [this message]
2001-06-25  5:04 ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2001-06-21 10:27 John S. Kallal

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=200106240415.VAA19378@bosch.cygnus.com \
    --to=chastain@cygnus.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