In <cd5ihs$l8e$1@n ews-reader2.wanadoo .fr> "jacob navia" <jacob@jacob.re mcomp.fr> writes:
[color=blue]
>The section about boolean values should mention
><stdbool.h> at least. It is still at the C89 stage...[/color]
^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^
So is the C programming community at large.
Dan
--
Dan Pop
DESY Zeuthen, RZ group
Email: Dan.Pop@ifh.de
"Dan Pop" <Dan.Pop@cern.c h> a écrit dans le message de
news:cd5tff$n4b $6@sunnews.cern .ch...[color=blue]
> In <cd5ihs$l8e$1@n ews-reader2.wanadoo .fr> "jacob navia"[/color]
<jacob@jacob.re mcomp.fr> writes:[color=blue]
>[color=green]
> >The section about boolean values should mention
> ><stdbool.h> at least. It is still at the C89 stage...[/color]
> ^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^
> So is the C programming community at large.
>[/color]
So what?
The current standard is C99. Period.
The FAQ should mention the current version of the standard.
I am not advocating dropping all references to C89, but the
current standard should be mentioned.
In <cd600i$gn0$1@n ews-reader1.wanadoo .fr> "jacob navia" <jacob@jacob.re mcomp.fr> writes:
[color=blue]
>"Dan Pop" <Dan.Pop@cern.c h> a écrit dans le message de
>news:cd5tff$n4 b$6@sunnews.cer n.ch...[color=green]
>> In <cd5ihs$l8e$1@n ews-reader2.wanadoo .fr> "jacob navia"[/color]
><jacob@jacob.r emcomp.fr> writes:[color=green]
>>[color=darkred]
>> >The section about boolean values should mention
>> ><stdbool.h> at least. It is still at the C89 stage...[/color]
>> ^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^
>> So is the C programming community at large.[/color]
>
>So what?[/color]
So this is what people writing C code care about. When the importance of
portable programming penetrates your thick skull, you'll understand why.
[color=blue]
>The current standard is C99. Period.[/color]
So what?!? You're not posting to comp.std.c, are you?
[color=blue]
>The FAQ should mention the current version of the standard.[/color]
Sez who? The FAQ maintainer obviously thinks otherwise, as the [ISO]
tag means:
International Organization for Standardization , ISO 9899:1990
(see question 11.2). [ISO]
[color=blue]
>I am not advocating dropping all references to C89, but the
>current standard should be mentioned.[/color]
Who are you to decide what the FAQ *should* do? Start your own FAQ and
put whatever you want there. Then see if anyone else cares about it.
Your C tutorial has already been a tremendous success in c.l.c, hasn't it?
Dan
--
Dan Pop
DESY Zeuthen, RZ group
Email: Dan.Pop@ifh.de
In message <cd65f7$hrm$3@s unnews.cern.ch> Dan.Pop@cern.ch (Dan Pop) wrote:
[color=blue]
> In <cd600i$gn0$1@n ews-reader1.wanadoo .fr> "jacob navia" <jacob@jacob.re mcomp.fr> writes:
>[color=green]
> >So what?[/color]
>
> So this is what people writing C code care about. When the importance of
> portable programming penetrates your thick skull, you'll understand why.
>[color=green]
> >The current standard is C99. Period.[/color]
>
> So what?!? You're not posting to comp.std.c, are you?
>[color=green]
> >The FAQ should mention the current version of the standard.[/color]
>
> Sez who? The FAQ maintainer obviously thinks otherwise, as the [ISO]
> tag means:
>
> International Organization for Standardization , ISO 9899:1990
> (see question 11.2). [ISO]
>[color=green]
> >I am not advocating dropping all references to C89, but the
> >current standard should be mentioned.[/color]
>
> Who are you to decide what the FAQ *should* do? Start your own FAQ and
> put whatever you want there. Then see if anyone else cares about it.
> Your C tutorial has already been a tremendous success in c.l.c, hasn't it?[/color]
I think there must be some sort of annual cycle of Mr Pop unpleasantness; I
think I last killfiled him about the same time last year. Maybe he's trying
for the title of c.l.c's most annoying poster? I personally find him far more
of an irritant than the mere incompetents and general trolls like ERT. At
least they're not vindictive, unpleasant sociopaths with far too much posting
time on their hands.
*PLONK*
--
Kevin Bracey, Principal Software Engineer
Tematic Ltd Tel: +44 (0) 1223 503464
182-190 Newmarket Road Fax: +44 (0) 1728 727430
Cambridge, CB5 8HE, United Kingdom WWW: http://www.tematic.com/
"Kevin Bracey" <kevin.bracey@t ematic.com> a écrit dans le message de
news:e66dfbce4c .kbracey@temati c.com...[color=blue]
> In message <cd65f7$hrm$3@s unnews.cern.ch>
> Dan.Pop@cern.ch (Dan Pop) wrote:[/color]
[snip][color=blue]
>
> I think there must be some sort of annual cycle of Mr Pop unpleasantness;[/color]
I[color=blue]
> think I last killfiled him about the same time last year. Maybe he's[/color]
trying[color=blue]
> for the title of c.l.c's most annoying poster? I personally find him far[/color]
more[color=blue]
> of an irritant than the mere incompetents and general trolls like ERT. At
> least they're not vindictive, unpleasant sociopaths with far too much[/color]
posting[color=blue]
> time on their hands.
>
> *PLONK*[/color]
Well I surely agree with this description :-)
I can't understand that the same people that strictly say that only
STANDARD C is on topic in this list now say that the C99 standard is
irrelevant. I just want that the FAQ *mentions* the standard
boolean interface header <stdbool.h> !!!
References:
ANSI/ISO C Standard 7.15 Boolean type and values <stdbool.h>
"jacob navia" <jacob@jacob.re mcomp.fr> writes:
[color=blue]
> I just want that the FAQ *mentions* the standard boolean
> interface header <stdbool.h> !!![/color]
There's nothing anybody but the FAQ maintainer can do about that.
Take it up with Steve Summit.
"jacob navia" <jacob@jacob.re mcomp.fr> writes:[color=blue]
> The section about boolean values should mention
> <stdbool.h> at least. It is still at the C89 stage...
> (Section 9)[/color]
I agree. The C FAQ was updated just recently; the latest text
version, at <ftp://ftp.eskimo.com/u/s/scs/C-faq/faq.gz>, is less than
two weeks old (the HTML version hasn't been updated yet). It does
include material about the C99 standard; I'm a little surprised it
doesn't mention C99's new support for boolean types.
(Anyone who thinks the C FAQ *shouldn't* discuss C99 should probably
take it up with Steve Summit.)
--
Keith Thompson (The_Other_Keit h) kst-u@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst>
We must do something. This is something. Therefore, we must do this.
"Steve Summit" <scs@eskimo.com > a écrit dans le message de
news:cd6qo7$nsd $1@eskinews.esk imo.com...[color=blue]
> jacob navia wrote:[color=green][color=darkred]
> >> The section about boolean values should mention
> >> <stdbool.h> at least.[/color][/color]
>
> Indeed it should. I'll make a note. Thanks.
>[/color]
Thanks for your work Steve. The other issues I mention in another
post are not very important. If you want I can contribute a lot
of answered questions about Win32 that could replace the MSDOS
part but that is not essential and I leave it at your choice.
Kevin Bracey <kevin.bracey@t ematic.com> spoke thus:
[color=blue]
> I think there must be some sort of annual cycle of Mr Pop unpleasantness; I
> think I last killfiled him about the same time last year. Maybe he's trying
> for the title of c.l.c's most annoying poster?[/color]
Personally, I'd much prefer being told that I'm wrong in the Dan Pop
manner than not know it.
--
Christopher Benson-Manica | I *should* know what I'm talking about - if I
ataru(at)cybers pace.org | don't, I need to know. Flames welcome.
jacob navia wrote:[color=blue]
> "Dan Pop" <Dan.Pop@cern.c h> a écrit dans le message de
> news:cd5tff$n4b $6@sunnews.cern .ch...
>[color=green]
>>In <cd5ihs$l8e$1@n ews-reader2.wanadoo .fr> "jacob navia"[/color]
>
> <jacob@jacob.re mcomp.fr> writes:
>[color=green][color=darkred]
>>>The section about boolean values should mention
>>><stdbool.h > at least. It is still at the C89 stage...[/color]
>>
>> ^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^
>>So is the C programming community at large.
>>[/color]
>
>
> So what?
>
> The current standard is C99. Period.
>
> The FAQ should mention the current version of the standard.
> I am not advocating dropping all references to C89, but the
> current standard should be mentioned.[/color]
So there is a later standard. BFD.
What about all those of us who are forced to use compilers
that are built around the C89 standard?
Many of the companies will not uprade their compilers unless
all of the projects require it. Most of my embedded systems
programming has shown that the C89 standard is adequate and
there isn't a _need_ to upgrade.
But what about legacy projects. I got access to a whole lot
of code that uses #define BOOL, #define TRUE, #define FALSE,
and similar. We are not going to change all that old code
to upgrade it to a standard. Simply because customers will
not pay more for their product than they need to. The money
for upgrading code has to come from somewhere.
Steve Summit wrote:
[color=blue]
> jacob navia wrote:
>[color=green][color=darkred]
>>>The section about boolean values should mention
>>><stdbool.h > at least.[/color][/color]
>
> Indeed it should. I'll make a note. Thanks.
>
> E. Robert Tisdale wrote:
>[color=green]
>>The C FAQ is obsolete.[/color]
>
> I'm biased, of course, but I think that's a *little* strong.
>[color=green]
>>It needs to be brought up-to-date.[/color]
>
> When's the last time you looked at the version posted here?[/color]
I consult the C FAQ frequently.
I don't re-read the entire FAQ every time.
I have probably consulted it at least once in the last week or two.
In addition,
both ANSI and ISO require periodic review of their standards.
This process is beginning in 1995,
and will likely result in a completely revised standard
(nicknamed ``C9X'' on the assumption of completion by 1999).
This information is now almost a decade old.
There is a new standard and the C FAQ should be completely overhauled
to reflect the adoption of that new standard.
Christopher Benson-Manica wrote:[color=blue]
>
> Kevin Bracey <kevin.bracey@t ematic.com> spoke thus:
>[color=green]
> > I think there must be some sort of annual cycle of Mr Pop unpleasantness; I
> > think I last killfiled him about the same time last year. Maybe he's trying
> > for the title of c.l.c's most annoying poster?[/color]
>
> Personally, I'd much prefer being told that I'm wrong in the Dan Pop
> manner than not know it.[/color]
But then again, I'd rather be told I'm wrong in the Chris Torek manner
than the Dan Pop manner.
Comment