9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] C compiler question
Date: Mon, 13 Jul 2009 21:00:17 -0700	[thread overview]
Message-ID: <dd6fe68a0907132100g5f513121n3fa581bc16c3f070@mail.gmail.com> (raw)
In-Reply-To: <4A5BF452.1090502@tecmav.com>

> Yes, but in my example - sorry - "NeverDefined" doesn't mean "declared and
> defined elsewhere (or not)" but "not declared .and. not defined".

no and yes.

union U
{
  struct
  {
        struct NeverDefined  nf;              //  Unknown, definition
not #included
  } S1
};

declares a struct named NeverDefined just by mentioning it.
the compiler should reject the use because NeverDefined
is not defined.  it's just a bug.  i don't have a copy of the
compiler to play with but erik's patch seems fine.

russ


      parent reply	other threads:[~2009-07-14  4:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-12  3:59 Adriano Verardo
2009-07-12 16:59 ` erik quanstrom
2009-07-14  2:58   ` Adriano Verardo
2009-07-14  3:14     ` erik quanstrom
2009-07-14 14:00       ` Adriano Verardo
2009-07-14 14:57         ` erik quanstrom
2009-07-14 16:26           ` Adriano Verardo
2009-07-14 16:38             ` erik quanstrom
2009-07-14 17:18       ` Roman V Shaposhnik
2009-07-14 17:46         ` erik quanstrom
2009-07-14 18:59           ` Roman V Shaposhnik
2009-07-14 19:29             ` erik quanstrom
2009-07-14 19:45               ` Russ Cox
2009-07-15 11:34                 ` Ethan Grammatikidis
2009-07-15 11:38                   ` erik quanstrom
2009-07-14 20:28               ` [9fans] pointers to incomplete types Roman V Shaposhnik
2009-07-15  9:25               ` [9fans] C compiler question robert wilson
2009-07-14  4:00     ` Russ Cox [this message]

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=dd6fe68a0907132100g5f513121n3fa581bc16c3f070@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).