From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] cc nit?
Date: Sun, 1 Jul 2012 18:45:22 -0400 [thread overview]
Message-ID: <0ed0a6d52f2a1c49363d9b032c8f178a@kw.quanstro.net> (raw)
In-Reply-To: <CAE9W7-iFxd6ysP4cxRcGVuLT0n+SY2r4XjOTVpjpXi292v4WWQ@mail.gmail.c>
> Many compilers do just that, however, that said, unless the compiler is
> prepared for it, since it effectively yields a struct of zero size which
> normally is a no-go, it could produce bugs involving sizeof, initializers,
> pointer addition et al, even some divisions by zero if the compiler is
> making certain assumptions already, unless it already can have zero length
> objects of this nature for some other reasons.
actually, kenc is pretty good about all these. if you have
struct fu {void x;};
and take sizeof(struct fu), that will give a diagnostic error.
the reason i avoided it was to not mess with the grammer, but if this is a
common thing, maybe it's no big deal.
though as charles points out, it is a bit of a waste of time.
- erik
next prev parent reply other threads:[~2012-07-01 22:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 21:25 erik quanstrom
2012-06-30 21:33 ` Bakul Shah
2012-06-30 21:37 ` erik quanstrom
2012-06-30 22:15 ` Bakul Shah
2012-07-01 13:47 ` erik quanstrom
2012-07-01 16:54 ` Comeau At9Fans
2012-07-01 20:39 ` Charles Forsyth
2012-07-01 22:22 ` Comeau At9Fans
2012-07-01 22:32 ` Charles Forsyth
2012-07-01 22:34 ` Charles Forsyth
2012-07-02 0:21 ` Comeau At9Fans
2012-07-02 0:18 ` Comeau At9Fans
2012-07-02 7:42 ` Charles Forsyth
2012-07-02 7:45 ` Charles Forsyth
[not found] ` <CAE9W7-iFxd6ysP4cxRcGVuLT0n+SY2r4XjOTVpjpXi292v4WWQ@mail.gmail.c>
2012-07-01 22:45 ` erik quanstrom [this message]
2012-07-02 0:24 ` Comeau At9Fans
[not found] ` <CAE9W7-gZsWHuspmwBw0qU_djkiDhAF6hA2zLU3Ms=xiO1j5LXQ@mail.gmail.c>
2012-07-01 16:57 ` erik quanstrom
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=0ed0a6d52f2a1c49363d9b032c8f178a@kw.quanstro.net \
--to=quanstro@quanstro.net \
--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).