public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Aurel Balmosan <ab@orga.com>
To: Alexandre Oliva <oliva@dcc.unicamp.br>, egcs-bugs <egcs-bugs@cygnus.com>
Subject: Re: Initialising an union
Date: Thu, 20 Aug 1998 02:41:00 -0000	[thread overview]
Message-ID: <35DBD533.721DB13F@orga.com> (raw)
In-Reply-To: <or4sv8ejg4.fsf@araguaia.dcc.unicamp.br>

Alexandre Oliva wrote:

> Does it apply to local non-static variables?  I'm pretty sure this is
> true for variables in static storage, but how about local ones?
> Unfortunately, I don't have access to the ANSI-C Standard :-(

It does. In the ANSI-C Language Referenze Version 2 A.8.7
from 31.Oct.1988 ANSI Programming Langues C, X.3.159-1989
you find the sentence:

    In the first edition the initialisation of auto and register
    struct's, union's or vektors was not allowed. The ANSI-C
    standard allowes to use const constructors or simple
    initilizer expresions.

This make clear that auto and register structs/unions/vektors
can be initialised.

Also I used the same code on different platforms i.e DEC-Unix
where we use the standard C compiler which comes with the OS.
There the code works as I expected.

So now I am back that the egcs-1.0.3a has a bug here.

Bye,

    Aurel.

--
Aurel Balmosan           | Department SE-SW
ORGA Kartensysteme GmbH  | phone: +49 5254 991 824
An der Kapelle 2         | fax  : +49 5254 991 749
33104 Paderborn, Germany | mailto:ab@orga.com





  reply	other threads:[~1998-08-20  2:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-18  0:39 Aurel Balmosan
1998-08-18 18:14 ` Alexandre Oliva
1998-08-19  2:44   ` Aurel Balmosan
1998-08-19 14:51     ` Alexandre Oliva
1998-08-20  2:41       ` Aurel Balmosan [this message]
1998-08-20  8:15         ` Alexandre Oliva
  -- strict thread matches above, loose matches on Subject: below --
1998-08-17  7:51 Aurel Balmosan
1998-08-18 11:46 ` Jeroen Dobbelaere
1998-08-19  4:40   ` Aurel Balmosan
1998-08-19 10:03     ` Jeroen Dobbelaere

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=35DBD533.721DB13F@orga.com \
    --to=ab@orga.com \
    --cc=egcs-bugs@cygnus.com \
    --cc=oliva@dcc.unicamp.br \
    /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).