Re: Types in C

Path	csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From	Tim Rentsch <txr@alumni.caltech.edu>
Newsgroups	comp.std.c
Subject	Re: Types in C
Date	Wed, 01 Jun 2011 12:23:36 -0700
Organization	A noiseless patient Spider
Lines	38
Message-ID	<kfn62opnyo7.fsf@x-alumni2.alumni.caltech.edu> (permalink)
References	<irbo6c$ul$1@speranza.aioe.org> <is0vfg$vqg$1@dont-email.me> <is14v9$f62$1@speranza.aioe.org> <is15pu$ahd$1@dont-email.me> <kfn39jup0n2.fsf@x-alumni2.alumni.caltech.edu> <is58gv$aeo$1@dont-email.me>
Mime-Version	1.0
Content-Type	text/plain; charset=us-ascii
Injection-Info	mx04.eternal-september.org; posting-host="FgYPIxjYg/4sV3coyTmnng"; logging-data="3492"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1993JDYwo/uMEiFLAjGS+QGN43k+CSDyg4="
User-Agent	Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock	sha1:BhnJHjb5Y4UMdSgoa2H46+mnHjE= sha1:bvVj9SwZ5oPPprnAPk7QUhQA7O8=
Xref	x330-a1.tempe.blueboxinc.net comp.std.c:380

Show key headers only | View raw

Shao Miller <sha0.miller@gmail.com> writes:

> On 6/1/2011 12:43 AM, Tim Rentsch wrote:
>> Shao Miller<sha0.miller@gmail.com>  writes:
>>
>> [snip]
>>>
>>> In the N1494 draft, we have 6.2.5p19:
>>>
>>>    "The void type comprises an empty set of values; it is an incomplete
>>> object type that cannot be completed."
>>>
>>> Similarly:
>>>
>>>    typedef char a_incomplete[];
>>>
>>> could never be completed, if I'm not mistaken.
>>
>> Only because there is no way to refer to type in
>> question, not for any sort of fundamental reason.
>> The two cases aren't analogous at all.
>
> The original poster seemed, to me, to be struggling with the idea that
> an object type can be incomplete and complete at different times, but
> that the previous status of 'void' as an "incomplete type" mightn't
> quite fit with the new status of "object type" ("incomplete object
> type," in particular).  This was simply an example of another
> incomplete object type which forever carries that status, you've
> agreed.

No, I haven't.  The two cases are not the same.

In fact the case with a typedef of an incomplete array
type could be made complete, by providing an extension
(eg, using _Pragma or some such) that allows an existing
type to be decorated with additional information.  So saying
the typedef'ed array type can never be completed is wrong.
And that result is fundamentally different from void.

Thread

Types in C jacob navia <jacob@spamsink.net> - 2011-05-22 21:29 +0200
  Re: Types in C Keith Thompson <kst-u@mib.org> - 2011-05-22 12:48 -0700
  Re: Types in C Marcin Grzegorczyk <mgrzegor@poczta.onet.pl> - 2011-05-30 22:42 +0200
    Re: Types in C Shao Miller <sha0.miller@gmail.com> - 2011-05-30 17:45 -0500
      Re: Types in C Keith Thompson <kst-u@mib.org> - 2011-05-31 08:47 -0700
        Re: Types in C Shao Miller <sha0.miller@gmail.com> - 2011-05-31 13:54 -0400
      Re: Types in C Tim Rentsch <txr@alumni.caltech.edu> - 2011-05-31 22:38 -0700
        Re: Types in C Shao Miller <sha0.miller@gmail.com> - 2011-06-01 07:22 -0500
          Re: Types in C Tim Rentsch <txr@alumni.caltech.edu> - 2011-06-01 12:13 -0700
    Re: Types in C jacob navia <jacob@spamsink.net> - 2011-05-31 00:16 +0200
      Re: Types in C Shao Miller <sha0.miller@gmail.com> - 2011-05-30 18:30 -0500
        Re: Types in C Tim Rentsch <txr@alumni.caltech.edu> - 2011-05-31 22:43 -0700
          Re: Types in C Shao Miller <sha0.miller@gmail.com> - 2011-06-01 07:41 -0500
            Re: Types in C Tim Rentsch <txr@alumni.caltech.edu> - 2011-06-01 12:23 -0700
      Re: Types in C Marcin Grzegorczyk <mgrzegor@poczta.onet.pl> - 2011-06-02 22:44 +0200
        Re: Types in C jacob navia <jacob@spamsink.net> - 2011-06-02 22:49 +0200
          Re: Types in C Keith Thompson <kst-u@mib.org> - 2011-06-02 15:26 -0700

csiph-web