From: Bruce Korb <bkorb@pacbell.net>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Gabriel Dos Reis <gdr@integrable-solutions.net>,
Robert Dewar <dewar@gnat.com>,
zack@codesourcery.com, gcc@gcc.gnu.org
Subject: Re: module level flags
Date: Sun, 29 Sep 2002 13:08:00 -0000 [thread overview]
Message-ID: <3D975D4A.4D845589@pacbell.net> (raw)
In-Reply-To: <20020929195837.GA6173@nevyn.them.org>
Daniel Jacobowitz wrote:
>
> On Sun, Sep 29, 2002 at 10:22:16AM -0700, Bruce Korb wrote:
> > Gabriel Dos Reis wrote:
> > > | If the standard says otherwise, then this construct:
> > > |
> > > | (mumble*)&stumble
> > > |
> > > | where 'stumble' is not of type 'mumble' must be deemed a
> > > | hard error.
> > >
> > > Not necessarily. The C abstract machine has a notion of "effective
> > > type" and "compatible type".
> >
> > By golly, YYSTYPE darn well better be compatible with
> > arbitrary pointers or there are real problems.
>
> What is a YYSTYPE? A union pointer? A char *? If it's a char *, as
> the language suggests it should be, then you're OK. If it's a union*
> you should be accessing the appropriate union member, not casting.
YYSTYPE is a bucket designed by YACC (Bison) to carry
either a pointer (of any sort) or a scalar.
next prev parent reply other threads:[~2002-09-29 20:01 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 6:40 Robert Dewar
2002-09-29 10:05 ` Bruce Korb
2002-09-29 10:17 ` Gabriel Dos Reis
2002-09-29 10:45 ` Bruce Korb
2002-09-29 11:36 ` Gabriel Dos Reis
2002-09-29 13:06 ` Daniel Jacobowitz
2002-09-29 13:08 ` Bruce Korb [this message]
2002-09-29 13:21 ` Daniel Jacobowitz
2002-09-29 10:49 ` Russ Allbery
2002-09-30 21:33 ` Alexandre Oliva
2002-09-30 21:42 ` Bruce Korb
-- strict thread matches above, loose matches on Subject: below --
2002-10-02 0:53 Robert Dewar
2002-10-01 13:58 Robert Dewar
2002-10-01 14:54 ` Joe Buck
2002-10-01 15:40 ` Michael Matz
2002-10-05 11:36 ` Toon Moene
[not found] <orn0py67ug.fsf@free.redhat.lsd.ic.unicamp.br>
2002-10-01 11:33 ` Joe Buck
2002-10-01 12:16 ` Geoff Keating
2002-10-05 21:03 ` Kai Henningsen
2002-10-06 6:36 ` Gabriel Dos Reis
2002-10-06 8:25 ` Nathan Sidwell
2002-10-06 8:29 ` Gabriel Dos Reis
2002-10-01 12:29 ` Bruce Korb
2002-10-01 14:14 ` Alexandre Oliva
2002-10-01 14:25 ` Alexandre Oliva
2002-10-03 16:46 ` Joe Buck
2002-10-03 17:34 ` Zack Weinberg
2002-10-03 18:07 ` Richard Henderson
2002-09-29 14:03 Robert Dewar
2002-09-29 13:42 Robert Dewar
2002-09-29 14:52 ` Russ Allbery
2002-09-29 13:38 Robert Dewar
2002-09-29 13:36 Robert Dewar
2002-09-29 13:38 ` Bruce Korb
2002-09-29 14:05 ` Russ Allbery
2002-09-29 10:45 Robert Dewar
2002-09-29 10:31 Robert Dewar
2002-09-28 16:41 Bruce Korb
2002-09-28 16:52 ` Tim Prince
2002-09-28 16:53 ` Bruce Korb
2002-09-28 18:06 ` Zack Weinberg
2002-09-28 18:20 ` Bruce Korb
2002-09-28 20:56 ` Zack Weinberg
2002-09-28 22:08 ` Bruce Korb
2002-09-29 15:46 ` Geoff Keating
2002-09-29 3:20 ` Robert Dewar
2002-09-29 11:55 ` Zack Weinberg
2002-09-29 13:10 ` Bruce Korb
2002-09-29 13:59 ` Zack Weinberg
2002-09-29 17:21 ` Tom Tromey
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=3D975D4A.4D845589@pacbell.net \
--to=bkorb@pacbell.net \
--cc=dewar@gnat.com \
--cc=drow@mvista.com \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=zack@codesourcery.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).