From: robert wilson <hotaru@thinkindifferent.net>
To: 9fans@9fans.net
Subject: Re: [9fans] C compiler question
Date: Wed, 15 Jul 2009 09:25:38 +0000 [thread overview]
Message-ID: <h3ipd2$cfd$1@news.eternal-september.org> (raw)
In-Reply-To: <a53acd743c3a6f747bf168ee2d08a2d4@coraid.com>
erik quanstrom wrote:
> assuming that pointers to incomplete types are
> themselves incomplete, and you haven't cited
> chapter and verse showing they are, i read that paragraph
> as saying that what plan 9 libraries do would be
> illegal, and therefore if we follow the standard,
> we'd need to remove Incomplete*s and replace
> them with void*s.
>
> if i'm wrong, can you explain how?
> The void type comprises an empty set of values; it is an incomplete
type that cannot be completed.
if a pointer to an incomplete type is incomplete, then void* is
incomplete, too. as far as i can tell, the standard would allow an
implementation where pointers vary in size and the sizes of pointers
can't be determined at compile-time, but that would be insane.
next prev parent reply other threads:[~2009-07-15 9:25 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 ` robert wilson [this message]
2009-07-14 4:00 ` [9fans] C compiler question Russ Cox
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='h3ipd2$cfd$1@news.eternal-september.org' \
--to=hotaru@thinkindifferent.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).