Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #57074

Re: Why the C programming language book was never updated past C89?

From Richard Heathfield <rjh@cpax.org.uk>
Newsgroups comp.lang.c
Subject Re: Why the C programming language book was never updated past C89?
Date 2015-02-06 17:13 +0000
Organization go, ion artisan!
Message-ID <mb2snc$udo$1@dont-email.me> (permalink)
References (10 earlier) <bMSAw.1206530$No4.943825@fx19.iad> <cjibs8Fq43fU5@mid.individual.net> <mb2fmr$63u$1@dont-email.me> <mb2gg7$926$1@dont-email.me> <mb2if2$h3g$1@dont-email.me>

Show all headers | View raw


On 06/02/15 14:18, James Kuyper wrote:
> On 02/06/2015 08:45 AM, Richard Heathfield wrote:
>> On 06/02/15 13:31, James Kuyper wrote:
> ...
>>> Why? While a solid majority of native speakers of English are from the
>>> US(58.5%),
>>
>> Native English speakers are born in England. That's what "native" means.
>
> In US English, native speakers of a language are those who speak that
> language as their first language, regardless of where they were born. I
> was unaware that this was one of the differences between the two
> dialects - and I honestly doubt that it is. I think you're just
> redefining the term to support an unsupportable claim.

Firstly, English is not a dialect. It is a language. Secondly, I base my 
claim that a native speaker of English is someone born in England on the 
etymology of "native", which descends from the Latin "nativus" (birth or 
origin), which stems from "natus" (born), which itself stems from 
"nasci" (to be born). It is, therefore, not an unreasonable way to
interpret the term. Mine may not be the /only/ definition of "native", 
but it is certainly a perfectly valid definition, and it is the one I've 
used all my adult life. I'm not in the habit of re-defining words on the 
fly in an attempt to win arguments. (That's not to say that I've never 
done it, or that I won't do it in future. But it's not a habit! And I 
didn't do it on this occasion.)

Of course, in your own language, you are free to define terms as you 
will. If, however, you name your language "English" and then go on to 
borrow many hundreds of thousands of English words with which to 
populate that language (and frequently changing not only their spellings 
but even their meanings in the process), we should hardly be surprised 
if occasionally there arise little disputes such as this one over the 
meanings of words.

The parallels with C are striking. Dennis Ritchie was of course a 
Hertfordshire man by birth, and Ken Thompson hailed from Somerset. They 
met at Cambridge University in 1961, and thanks to a shared love of 
Morris dancing they became firm friends. In 1964, scratching around for 
a dissertation subject, they consulted their tutor, who said "under no 
circumstances should you create your own operating system or your own 
language". Rightly taking this as a broad hint, they decided to do both. 
They worked hand in glove on both projects, and then tossed a coin to 
decide who would submit which dissertation. Ken won, so he took the 
credit for Unix, leaving Ritchie with the credit for C.

The name "C" is a curious one, and it has an interesting derivation. 
Most programming languages of the time were American, so Ken and Dennis 
originally called their own work "British Computer Programming 
Language", or BCPL for short. Eventually, they decided this was terribly 
long-winded. As they continued to develop it, they ended up dropping the 
CPL bit, and just called it B. And then, one May morning, with the 
dissertation date looming, the 'B' key on Dennis's typewriter got stuck, 
just as he was typing out the title page of his dissertation. He thumped 
it a bit, but it was well and truly stuck, so he typed "The C 
Programming Language" instead. Ken came along with a hammer a few 
minutes later to fix the key in the manner of the traditional British 
craftsman, but they had no time to re-work the text, and in any case 
they kind of liked the new name, so it stayed.

At any time you care to mention, the UK's economic state is either 
appalling or catastrophic. Since, at the time, it happened to be 
catastrophic, they decided to do their bit for exports by licensing Unix 
to Microsoft. Unfortunately, further research on their part suggested 
that Microsoft wouldn't exist for another eleven years, so they looked 
around for another buyer. SCO was a promising candidate, but again they 
would have to wait some time if they wanted to do a deal there. They 
tried phoning IBM, but the line was engaged ("busy"). Eventually, they 
turned to AT&T, who weren't actually a software company, but they did at 
least have the merit of existing, and they did manage to answer the phone.

The deal was struck. Cannily, though, Thompson and Ritchie decided to 
keep C under their hats for a while. They rewrote Unix in SNOBOL, and 
shipped that to AT&T instead. AT&T were delighted with the OS, but 
weren't too happy about the language. This was music to our heroic duo's 
ears. They immediately offered to rewrite Unix in a more sensible 
language, but it would take them many years of tedious research, and 
they would need a laboratory in which to work. AT&T fell for it, hook, 
line, and sinker. "Come to Bell Labs," they said. T&R did precisely 
that, and from time to time over the next few years they would submit 
status reports that were encouraging in tone but which pointed out how 
much more work was required and how much budget it would require. Bell 
Labs paid up quite happily. Meanwhile, T&R were happily bunking off and 
spending their days playing SpaceWars.

Bell Labs finally got wise to what was going on, and said that they'd 
better publish something pretty soon or the deal was off. Thompson and 
Ritchie checked their calendars. Hmm, perhaps five years of SpaceWars 
was taking the mickey a bit. So they blew the dust off the very first C 
manual that Ritchie had cobbled together, recompiled Unix in that rather 
ancient version of C, and handed everything in with a flourish some time 
in the Spring of 1969. They kept the very latest version back, in 
keeping with their normal business strategy.

Well, Bell Labs just *loved* C, even the primitive version that they 
were actually given, but Ritchie managed to persuade them that it needed 
some fine-tuning. This got the pair another four years funding, and they 
spent most of that playing SpaceWars too. Being British, though, they 
had a finely-developed sense of humour, so they spent a few weeks coming 
up with a joke language called C++. In due course, however, they decided 
that it wasn't all that funny after all, so one night they dropped the 
manual on a random desk in the main office (it happened to be the desk 
of a junior programmer with the unlikely name of Stroustrup), and 
thought no more about it.

Eventually, Bell Labs put their foot down again, and this time Dennis 
and Ken gave them the real C language. "And now," they said, "we have to 
write a manual for it. Unfortunately, we don't know American well 
enough. Could we have an American ghost-writer to turn all our pavements 
into sidewalks and handbags into purses?"

Bell Labs lent them Brian Kernighan, who was actually born in a small 
village in County Durham, but he'd emigrated to the USA as a young 
child, so he was fairly fluent in American. In fact, he was so fluent 
that he had all but forgotten how to speak English, which is why it took 
five years to come up with the manual. At least, that's what they 
claimed. It is equally possible that they spent the time writing a 
three-player version of SpaceWars (Project Code: Plan 3).

C, as we all know, became immensely popular, and Kernighan's translation 
of Ritchie's book was a best-seller. Better still, lots of implementors 
thought they could do better than Thompson and Ritchie, so they came up 
with all kinds of extra ideas. The resulting pot-pourri provided years 
of profitable consultancy for Brian, Ken, and Dennis.

The time came, however, when the industry began to demand some kind of 
interoperability between the various dialects of C, and there was a call 
for standardisation. ANSI set up the X3J11 committee, and everybody 
confidently expected that Dennis and Ken, at least, would be included in 
it. Ken, however, persuaded Dennis that they had better uses for their 
time (such as, for example, playing SpaceWars). So they contented 
themselves with firing an occasional potshot at the committee from the 
safety of Bell Labs.

This may have been a mistake.

The ANSI C of 1989 was a worthy language indeed, but Ritchie had more or 
less lost control of it by this stage. This situation worsened when ISO 
stuck their oar in, but at first they played it very cool. They didn't 
actually change anything (other than the section numbering). No, they 
wanted to make sure that the separation between the language and its 
authors was complete.

By 1995, ISO had achieved total separation. Ken and Dennis were no 
longer bothered about ISO's machinations. They had completed Plans 3, 4, 
5, 6, 7, and 8, and now they were working on the best ever version of 
SpaceWars, code-named Plan 9. Naturally, they developed this in their 
own, heavily improved version of C, which they kept pretty much to 
themselves for the time being.

ISO were delighted, because it meant that these British guys were 
finally out of the way, and they could start to Americanise the 
language. "What we need," they said, "is tail fins. Cup holders. 
Electric windows. Power steering. A big V8 engine. Better make that two. 
An electric sun-roof. Electric toothbrush, perhaps. More cup-holders. 
Lots of different /sizes/ of cup-holders. Maybe a gun rack? And 
*obviously* automatic transmission. How these guys ever managed to drive 
a stick-shift language is just ridiculous." And so the features kept 
piling on, as the clean, simple, quintessentially British two-door 
language became stuffed and bloated with "luxury" features, until it 
could hardly go round a corner without falling over. The Americans were 
delighted. That was a proper, *American* language.

But it was already too late. Stroustrup (remember him?) had mistaken the 
manual on his desk for a work assignment. By the time he'd finished with 
C++, even the cup-holders had cup-holders. The American dream had become 
a reality. The showrooms put C++ in the spotlight and draped Miss 
America over its bonnet (or "hood"), and C was relegated to a back 
corner, gathering dust.

Ken, Brian and Dennis noted the commercial demise of C with wry 
amusement. They knew that their language was still the best for actually 
getting things done quickly, but they saw no point in trying to convince 
the world, not when they were busy having the mother of all SpaceWars 
battles, courtesy of Plan 9, and real, proper, sensible, streamlined, 
fast, elegant C. British C.

-- 
Richard Heathfield
Email: rjh at cpax dot org dot uk
"Usenet is a strange place" - dmr 29 July 1999
Sig line 4 vacant - apply within

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Why the C programming language book was never updated past C89? Kamel Biskri <email@domain.com> - 2014-11-28 23:45 +0100
  Re: Why the C programming language book was never updated past C89? Robert Miles <milesrf@Usenet-News.net> - 2015-02-05 04:40 -0600
    Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-05 11:08 +0000
      Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-05 14:18 +0100
        Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-05 13:52 +0000
          Re: Why the C programming language book was never updated past C89? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-02-05 14:32 +0000
            Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-05 14:55 +0000
              Re: Why the C programming language book was never updated past C89? Ben Bacarisse <ben.usenet@bsb.me.uk> - 2015-02-05 17:07 +0000
          Re: Why the C programming language book was never updated past C89? Bartc <bc@freeuk.com> - 2015-02-05 14:49 +0000
            Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-05 15:01 +0000
              Re: Why the C programming language book was never updated past C89? Bartc <bc@freeuk.com> - 2015-02-05 15:31 +0000
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-05 15:58 +0000
              Re: Why the C programming language book was never updated past C89? wpihughes@gmail.com - 2015-02-05 13:07 -0800
                Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-05 16:18 -0500
                Re: Why the C programming language book was never updated past C89? wpihughes@gmail.com - 2015-02-05 13:43 -0800
                Re: Why the C programming language book was never updated past C89? Bartc <bc@freeuk.com> - 2015-02-05 21:54 +0000
                Re: Why the C programming language book was never updated past C89? jak <please@nospam.tnx> - 2015-03-10 10:43 +0100
                Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-05 17:01 -0500
                Re: Why the C programming language book was never updated past C89? Greg Martin <greg.at.softsprocket@dot.com> - 2015-02-06 15:55 +0000
                Re: Why the C programming language book was never updated past C89? Kaz Kylheku <kaz@kylheku.com> - 2015-02-05 21:24 +0000
                Re: Why the C programming language book was never updated past C89? wpihughes@gmail.com - 2015-02-05 13:34 -0800
                Re: Why the C programming language book was never updated past C89? Bartc <bc@freeuk.com> - 2015-02-05 21:43 +0000
                Re: Why the C programming language book was never updated past C89? wpihughes@gmail.com - 2015-02-05 13:58 -0800
                Re: Why the C programming language book was never updated past C89? Bartc <bc@freeuk.com> - 2015-02-05 22:07 +0000
                Re: Why the C programming language book was never updated past C89? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-02-05 18:11 -0500
                Re: Why the C programming language book was never updated past C89? Ian Collins <ian-news@hotmail.com> - 2015-02-06 12:15 +1300
                Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-06 10:08 +0100
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-06 09:19 +0000
                Re: Why the C programming language book was never updated past C89? Robert Wessel <robertwessel2@yahoo.com> - 2015-02-06 03:34 -0600
                Re: Why the C programming language book was never updated past C89? Keith Thompson <kst-u@mib.org> - 2015-02-06 08:22 -0800
                Re: Why the C programming language book was never updated past C89? guinness.tony@gmail.com - 2015-02-06 03:39 -0800
                Re: Why the C programming language book was never updated past C89? Kaz Kylheku <kaz@kylheku.com> - 2015-02-06 15:45 +0000
                Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-06 08:31 -0500
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-06 13:45 +0000
                Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-06 09:18 -0500
                Re: Why the C programming language book was never updated past C89? wpihughes@gmail.com - 2015-02-06 07:08 -0800
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-06 15:15 +0000
                Re: Why the C programming language book was never updated past C89? wpihughes@gmail.com - 2015-02-06 07:31 -0800
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-06 15:37 +0000
                Re: Why the C programming language book was never updated past C89? wpihughes@gmail.com - 2015-02-06 08:15 -0800
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-06 17:13 +0000
                Re: Why the C programming language book was never updated past C89? wpihughes@gmail.com - 2015-02-06 10:48 -0800
                Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-06 16:47 +0100
                Re: Why the C programming language book was never updated past C89? "Osmium" <r124c4u102@comcast.net> - 2015-02-06 09:52 -0600
                Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-06 12:08 -0500
                Re: Why the C programming language book was never updated past C89? "Osmium" <r124c4u102@comcast.net> - 2015-02-06 11:32 -0600
                Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-06 12:41 -0500
                Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-07 14:21 +0100
                Re: Why the C programming language book was never updated past C89? glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-02-06 18:03 +0000
                Re: Why the C programming language book was never updated past C89? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2015-02-06 13:28 -0700
                Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-07 14:22 +0100
                Re: Why the C programming language book was never updated past C89? Bartc <bc@freeuk.com> - 2015-02-06 13:56 +0000
                Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-06 16:55 +0100
                Re: Why the C programming language book was never updated past C89? glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-02-06 18:06 +0000
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-06 18:16 +0000
                Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-06 13:34 -0500
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-06 18:44 +0000
                Re: Why the C programming language book was never updated past C89? glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-02-06 19:00 +0000
                Re: Why the C programming language book was never updated past C89? Robert Wessel <robertwessel2@yahoo.com> - 2015-02-06 17:44 -0600
                Re: Why the C programming language book was never updated past C89? Kaz Kylheku <kaz@kylheku.com> - 2015-02-07 01:46 +0000
                Re: Why the C programming language book was never updated past C89? Robert Wessel <robertwessel2@yahoo.com> - 2015-02-07 00:20 -0600
                Re: Why the C programming language book was never updated past C89? Kaz Kylheku <kaz@kylheku.com> - 2015-02-07 06:47 +0000
                Re: Why the C programming language book was never updated past C89? Robert Wessel <robertwessel2@yahoo.com> - 2015-02-07 01:26 -0600
                Re: Why the C programming language book was never updated past C89? Robert Wessel <robertwessel2@yahoo.com> - 2015-02-07 01:34 -0600
                Re: Why the C programming language book was never updated past C89? raltbos@xs4all.nl (Richard Bos) - 2015-02-07 11:59 +0000
                Re: Why the C programming language book was never updated past C89? raltbos@xs4all.nl (Richard Bos) - 2015-02-07 11:57 +0000
                Re: Why the C programming language book was never updated past C89? Keith Thompson <kst-u@mib.org> - 2015-02-06 10:51 -0800
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-06 19:05 +0000
                Re: Why the C programming language book was never updated past C89? Keith Thompson <kst-u@mib.org> - 2015-02-06 11:23 -0800
                Re: Why the C programming language book was never updated past C89? wpihughes@gmail.com - 2015-02-06 11:31 -0800
                Re: Why the C programming language book was never updated past C89? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-02-06 15:26 -0500
                Re: Why the C programming language book was never updated past C89? raltbos@xs4all.nl (Richard Bos) - 2015-02-09 21:19 +0000
                Re: Why the C programming language book was never updated past C89? Jim Barlow <jim.j.barlow@gmail.com> - 2015-02-09 21:16 -0800
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-10 05:36 +0000
                Re: Why the C programming language book was never updated past C89? Les Cargill <lcargill99@comcast.com> - 2015-02-10 07:53 -0600
                Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-10 15:08 +0100
                Re: Why the C programming language book was never updated past C89? Les Cargill <lcargill99@comcast.com> - 2015-02-10 19:57 -0600
                Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-11 10:19 +0100
                Re: Why the C programming language book was never updated past C89? Les Cargill <lcargill99@comcast.com> - 2015-02-11 07:32 -0600
                Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-11 15:32 +0100
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-11 14:06 +0000
                Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-11 08:07 -0500
                Re: Why the C programming language book was never updated past C89? Les Cargill <lcargill99@comcast.com> - 2015-02-11 07:33 -0600
                Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-11 09:08 -0500
                Re: Why the C programming language book was never updated past C89? Bartc <bc@freeuk.com> - 2015-02-11 14:29 +0000
                Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-11 16:28 +0100
                Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-11 11:52 -0500
                Re: Why the C programming language book was never updated past C89? Keith Thompson <kst-u@mib.org> - 2015-02-11 10:37 -0800
                Re: Why the C programming language book was never updated past C89? Les Cargill <lcargill99@comcast.com> - 2015-02-11 19:02 -0600
                Re: Why the C programming language book was never updated past C89? Ian Collins <ian-news@hotmail.com> - 2015-02-12 14:55 +1300
                Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-11 15:38 +0100
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-11 16:09 +0000
                Re: Why the C programming language book was never updated past C89? Phil Carmody <pc+usenet@asdf.org> - 2015-02-14 18:39 +0200
                Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-10 10:14 +0100
                Re: Why the C programming language book was never updated past C89? glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2015-02-06 17:49 +0000
                Re: Why the C programming language book was never updated past C89? Greg Martin <greg.at.softsprocket@dot.com> - 2015-02-06 15:59 +0000
                Re: Why the C programming language book was never updated past C89? raltbos@xs4all.nl (Richard Bos) - 2015-02-06 13:34 +0000
                Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-06 16:58 +0100
                Re: Why the C programming language book was never updated past C89? raltbos@xs4all.nl (Richard Bos) - 2015-02-09 21:21 +0000
                Re: Why the C programming language book was never updated past C89? Kaz Kylheku <kaz@kylheku.com> - 2015-02-06 20:54 +0000
                Re: Why the C programming language book was never updated past C89? Bartc <bc@freeuk.com> - 2015-02-06 21:27 +0000
                Re: Why the C programming language book was never updated past C89? Ian Collins <ian-news@hotmail.com> - 2015-02-07 11:31 +1300
                Re: Why the C programming language book was never updated past C89? Robert Wessel <robertwessel2@yahoo.com> - 2015-02-07 00:22 -0600
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-05 21:57 +0000
            Re: Why the C programming language book was never updated past C89? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2015-02-05 10:10 -0500
          Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-05 16:48 +0100
            Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-05 16:02 +0000
              Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-06 10:14 +0100
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-06 09:26 +0000
                Re: Why the C programming language book was never updated past C89? Keith Thompson <kst-u@mib.org> - 2015-02-06 08:36 -0800
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-06 17:20 +0000
                Re: Why the C programming language book was never updated past C89? raltbos@xs4all.nl (Richard Bos) - 2015-02-07 12:05 +0000
                Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-08 12:02 +0000
          Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-05 11:59 -0500
          Re: Why the C programming language book was never updated past C89? Keith Thompson <kst-u@mib.org> - 2015-02-05 10:47 -0800
            Re: Why the C programming language book was never updated past C89? Bartc <bc@freeuk.com> - 2015-02-05 19:38 +0000
              Re: Why the C programming language book was never updated past C89? Keith Thompson <kst-u@mib.org> - 2015-02-05 13:40 -0800
                Re: Why the C programming language book was never updated past C89? Ian Collins <ian-news@hotmail.com> - 2015-02-06 10:54 +1300
                Re: Why the C programming language book was never updated past C89? Keith Thompson <kst-u@mib.org> - 2015-02-05 15:27 -0800
          Re: Why the C programming language book was never updated past C89? Robert Wessel <robertwessel2@yahoo.com> - 2015-02-05 13:04 -0600
            Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-05 14:18 -0500
              Re: Why the C programming language book was never updated past C89? Robert Wessel <robertwessel2@yahoo.com> - 2015-02-05 18:35 -0600
                Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-06 08:47 -0500
                Re: Why the C programming language book was never updated past C89? Robert Wessel <robertwessel2@yahoo.com> - 2015-02-07 00:32 -0600
            Re: Why the C programming language book was never updated past C89? Richard Heathfield <rjh@cpax.org.uk> - 2015-02-05 21:53 +0000
        Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-05 12:17 -0500
          Re: Why the C programming language book was never updated past C89? David Brown <david.brown@hesbynett.no> - 2015-02-06 10:26 +0100
  Re: Why the C programming language book was never updated past C89? "Osmium" <r124c4u102@comcast.net> - 2015-02-05 08:26 -0600
    Re: Why the C programming language book was never updated past C89? James Kuyper <jameskuyper@verizon.net> - 2015-02-06 09:12 -0500

csiph-web