public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Love-Jensen <eljay@adobe.com>
To: "'Gaurav Gautam, Noida'" <gauravga@noida.hcltech.com>,
	<gcc@gcc.gnu.org>, MSX to GCC <gcc-help@gcc.gnu.org>
Subject: Re: No effect of -fshort-enums..is it a bug
Date: Thu, 22 Sep 2005 16:28:00 -0000	[thread overview]
Message-ID: <BF584543.1F89%eljay@adobe.com> (raw)
In-Reply-To: <SERRANOevWWGxegIqun000001d8@SERRANO.CAM.ARTIMI.COM>

Hi Dave, Daniel, and Gaurav,

For C99, I stand corrected.

For C89 or C++98, I think my statement is applicable.  (But until I
double-check by reading those standards, take that with a grain of salt.)

For all three, having enum be an int (signed or unsigned) is legit of
course.

For all three, having enum be a long is (at best) a compiler extension, at
worst (-pedantic ?) not supported.  If I'm reading the specs correctly.
NOTE:  not germane to Gaurav's question, just talking out loud.

Sincerely,
--Eljay

  reply	other threads:[~2005-09-22 16:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22 13:40 Gaurav Gautam, Noida
2005-09-22 15:32 ` Neil Booth
2005-09-22 15:36 ` John Love-Jensen
2005-09-22 16:15   ` Daniel Jacobowitz
2005-09-22 16:20   ` Dave Korn
2005-09-22 16:28     ` John Love-Jensen [this message]
2005-09-22 16:41       ` Gabriel Dos Reis
2005-09-22 16:51     ` Robert Dewar
2005-09-22 18:31       ` Daniel Jacobowitz
2005-09-22 19:03         ` Paul Brook
2005-09-22 16:26   ` Gabriel Dos Reis
2005-09-22 16:33     ` John Love-Jensen
  -- strict thread matches above, loose matches on Subject: below --
2005-09-23 14:06 Gaurav Gautam, Noida
2005-09-23 14:21 ` John Love-Jensen
2005-09-21 13:35 Gaurav Gautam, Noida
2005-09-21 14:19 ` Daniel Jacobowitz
2005-09-21 14:55   ` Robert Dewar
2005-09-21 17:26     ` Daniel Jacobowitz
2005-09-21 15:42 ` Andreas Schwab
2005-09-23  9:16   ` Bernhard R. Link
2005-09-21 12:17 Gaurav Gautam, Noida
2005-09-21 12:39 ` Daniel Jacobowitz

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=BF584543.1F89%eljay@adobe.com \
    --to=eljay@adobe.com \
    --cc=gauravga@noida.hcltech.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).