Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Keith Thompson <kst-u@mib.org> |
|---|---|
| Newsgroups | comp.std.c, comp.lang.c |
| Subject | Re: Types in C |
| Date | 2011-06-02 15:26 -0700 |
| Organization | None to speak of |
| Message-ID | <lnwrh3kgz6.fsf@nuthaus.mib.org> (permalink) |
| References | <irbo6c$ul$1@speranza.aioe.org> <is0vfg$vqg$1@dont-email.me> <is14v9$f62$1@speranza.aioe.org> <is8snh$qa5$1@dont-email.me> <is8t0m$9cl$1@speranza.aioe.org> |
Cross-posted to 2 groups.
jacob navia <jacob@spamsink.net> writes:
> Le 02/06/11 22:44, Marcin Grzegorczyk a écrit :
>> jacob navia wrote:
>>> Le 30/05/11 22:42, Marcin Grzegorczyk a écrit :
>>>> jacob navia wrote:
>>> After reading N1439 I would tend to agree with what it says but
>>> where should go the void type?
>>>
>>> It is void an object type?
>>
>> Yes, void belongs to object types, even if it might seem weird at first.
>>
>
> Well, YES...
>
> It seems weird to me, I wonder how the readers of the tutorial will
> react.
>
> In any case I will update the tutorial to reflect the current
> thinking of the committee.
[...]
That's up to you, of course, but in the current standard void is
not an object type. It's an incomplete type, and incomplete types
are disjoint from object types.
C201X has no official standing yet, and there are no conforming
implementations.
Are you writing a C99 tutorial or a C201X tutorial? If the latter,
I suggest making it clear that you're referring to a future version
of the language.
Or you might consider writing both, using something similar to
#ifdef to let you generate either version (depending on what tool
you're using to write and publish the tutorial).
(In this particular case, it's just a different way of describing the
same thing.)
--
Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
Back to comp.std.c | Previous | Next — Previous in thread | Find similar | Unroll 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