public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@alumni.caltech.edu>
To: Joe Buck <jbuck@synopsys.com>
Cc: gcc@gcc.gnu.org, slouken@devolution.com
Subject: Re: Regarding anonymous unions, etc.
Date: Tue, 31 Aug 1999 23:20:00 -0000	[thread overview]
Message-ID: <37CC97DA.89E50B3B@alumni.caltech.edu> (raw)
Message-ID: <19990831232000.PypfZiH1BDPdojJDafVX8dpjIuuPV76rd8eUo-jFHrw@z> (raw)
In-Reply-To: <199909010151.SAA18243@atrus.synopsys.com>

Joe Buck wrote:
> 
> > I hear the GCC team is soliciting input as to how important
> > Microsoft C++ extensions like anonymous unions, etc. are.
> 
> Anonymous unions are standard C++ and are supported by GCC.  However, MFC
> does use some non-standard features of MSVC.

I'm referring to C, not C++.  GCC still refuses to accept anonymous 
unions in C programs.  Visual C accepts them happily.  It's not
acceptable to compile the C programs as C++.

If you can tell me what compiler option to give gcc to
get it to accept anonymous unions in C, I'll gladly eat
my hat.

Thanks,
Dan

-- 
(The above is my opinion alone, and not that of my employer)

  reply	other threads:[~1999-08-31 23:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-31 18:29 Dan Kegel
1999-08-31 18:52 ` Joe Buck
1999-08-31 20:02   ` Dan Kegel [this message]
1999-08-31 23:20     ` Dan Kegel
1999-08-31 23:20   ` Joe Buck
1999-08-31 23:20 ` Dan Kegel
1999-08-31 19:44 Sam Lantinga
1999-08-31 20:13 ` Mumit Khan
1999-08-31 23:20   ` Mumit Khan
1999-09-02  0:24   ` Jeffrey A Law
1999-09-02  6:36     ` Gavin Romig-Koch
1999-09-30 18:02       ` Gavin Romig-Koch
1999-09-30 18:02     ` Jeffrey A Law
1999-08-31 23:20 ` Sam Lantinga

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=37CC97DA.89E50B3B@alumni.caltech.edu \
    --to=dank@alumni.caltech.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.com \
    --cc=slouken@devolution.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).