C
Chris Hills
I beg to disagree.
Unless hundreds of KLOC of, say, embedded GSM/GPRS/3G protocol stack
amounts to "very little" C.
written to ISO9899:1999?
That's an unfair assumption
Given that some of use have over 25 years professional experience some
one at age 14 is not going to have any real world experience.
He is not old enough to have had any work experience nor completed any
formal training. Two months no this NG is hardley enough either.
And that is irrelevant, and patronising.
The point is that he is jumping in to a debat with 2 months exposure to
this NG and NO experience of C standards, any work experience or formal
training.
What the "C language" is, is defined by the "C Standard". Or is it not?
ISO 9899:1999? Which compiler do you use that use a pure implementation
of that?
If you want to widen it out to K&R 1, 2, ANSI89, ISO 90, 95/96 & 99 that
lets most things in except real world implementations.
If you discuss the C language I would have though "as implemented" was a
good idea instead of sending people away to other NG's
This NG is staying static in size rather than growing with the Internet.
What is growing are other c lists and forum where the people who visit
here with a non-pure question end up.
You may say "good" but the net result (no pun intended is that other
forum become THE place to ask authoritative questions on C and
comp.std.C is the place of requisitions on standard C
That leaves this NG dying on its feet because of a few purist.
You have an opportunity to build a much larger community on here. You
can educate people in the differences between what they are doing and
standard C. Make them aware there is a difference. In some cases there
may be a standard or portable way of doing things.
As it is with the way MS are adding TR's etc most questions will be
answered on the MS NG's leaving this NG with a VERY small focus and
fewer people.