Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #53628 > unrolled thread
| Started by | Kamel Biskri <email@domain.com> |
|---|---|
| First post | 2014-11-28 23:45 +0100 |
| Last post | 2015-02-06 09:12 -0500 |
| Articles | 20 on this page of 129 — 23 participants |
Back to article view | Back to comp.lang.c
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
Page 2 of 7 — ← Prev page 1 [2] 3 4 5 6 7 Next page →
| From | wpihughes@gmail.com |
|---|---|
| Date | 2015-02-05 13:34 -0800 |
| Message-ID | <e6acfbc6-c489-4931-b467-00c5469b8e07@googlegroups.com> |
| In reply to | #57016 |
On Thursday, February 5, 2015 at 5:24:39 PM UTC-4, Kaz Kylheku wrote: > On 2015-02-05, wpihughes@gmail.com <wpihughes@gmail.com> wrote: > > On Thursday, February 5, 2015 at 11:01:46 AM UTC-4, Richard Heathfield wrote: > > > >> To be fair to both of us, modern syntax-colouring editors make both > >> problems far less likely to hold us up for very long. > > > > > > Modern? Syntax-colouring editors certainly predate C99. > > > > -William Hughes > > > > P.S. nice to see colour spelled correctly > > Bullshit; the word comes to us from Latin, via Old French. Both of these > had it as "color"! There is no need to add any goddamned 'u', let alone > one that serves absolutely no purpose, since it is *silent*. The "u" is their too stress test spell chequers. -William Hughes You have no honour
[toc] | [prev] | [next] | [standalone]
| From | Bartc <bc@freeuk.com> |
|---|---|
| Date | 2015-02-05 21:43 +0000 |
| Message-ID | <mb0o4a$eiq$1@dont-email.me> |
| In reply to | #57016 |
On 05/02/2015 21:24, Kaz Kylheku wrote: > On 2015-02-05, wpihughes@gmail.com <wpihughes@gmail.com> wrote: >> On Thursday, February 5, 2015 at 11:01:46 AM UTC-4, Richard Heathfield wrote: >> >>> To be fair to both of us, modern syntax-colouring editors make both >>> problems far less likely to hold us up for very long. >> >> >> Modern? Syntax-colouring editors certainly predate C99. >> >> -William Hughes >> >> P.S. nice to see colour spelled correctly > > Bullshit; the word comes to us from Latin, via Old French. Both of these > had it as "color"! There is no need to add any goddamned 'u', let alone > one that serves absolutely no purpose, since it is *silent*. I think Old French had it as 'colour'. But never mind how it came about; English doesn't use phonetic spelling, and in the UK, it's spelt 'colour'. It doesn't matter that some letters are silent or it isn't spelt exactly as pronounced (which would make it more like 'culler'). It is necessary to use 'colour' (in those regions using British English) to show that you're not ignorant. Try spelling all of 'poor', 'paw', 'pore', 'pour' etc as 'por' and see how far you get! -- Bartc
[toc] | [prev] | [next] | [standalone]
| From | wpihughes@gmail.com |
|---|---|
| Date | 2015-02-05 13:58 -0800 |
| Message-ID | <183a8d3f-1d70-4d35-bdd6-f79db1b6cf09@googlegroups.com> |
| In reply to | #57019 |
On Thursday, February 5, 2015 at 5:43:18 PM UTC-4, Bart wrote: > in the UK, it's spelt 'colour'. Get it right. "spelt" is a grain. If you want the past of the verb spell use "spelled". -William Hughes Canadian usage is the only correct usage, eh!
[toc] | [prev] | [next] | [standalone]
| From | Bartc <bc@freeuk.com> |
|---|---|
| Date | 2015-02-05 22:07 +0000 |
| Message-ID | <mb0ph6$kh2$1@dont-email.me> |
| In reply to | #57025 |
On 05/02/2015 21:58, wpihughes@gmail.com wrote: > On Thursday, February 5, 2015 at 5:43:18 PM UTC-4, Bart wrote: > >> in the UK, it's spelt 'colour'. > > Get it right. "spelt" is a grain. > If you want the past of the verb spell > use "spelled". Both forms are valid. And the spelling (of colour) is the same in the present and foreseeable future too! -- Bartc
[toc] | [prev] | [next] | [standalone]
| From | Lew Pitcher <lew.pitcher@digitalfreehold.ca> |
|---|---|
| Date | 2015-02-05 18:11 -0500 |
| Message-ID | <bMSAw.1206530$No4.943825@fx19.iad> |
| In reply to | #57019 |
On Thursday February 5 2015 16:43, in comp.lang.c, "Bartc" <bc@freeuk.com> wrote: > On 05/02/2015 21:24, Kaz Kylheku wrote: >> On 2015-02-05, wpihughes@gmail.com <wpihughes@gmail.com> wrote: >>> On Thursday, February 5, 2015 at 11:01:46 AM UTC-4, Richard Heathfield >>> wrote: >>> >>>> To be fair to both of us, modern syntax-colouring editors make both >>>> problems far less likely to hold us up for very long. >>> >>> >>> Modern? Syntax-colouring editors certainly predate C99. >>> >>> -William Hughes >>> >>> P.S. nice to see colour spelled correctly >> >> Bullshit; the word comes to us from Latin, via Old French. Both of these >> had it as "color"! There is no need to add any goddamned 'u', let alone >> one that serves absolutely no purpose, since it is *silent*. > > I think Old French had it as 'colour'. > > But never mind how it came about; English doesn't use phonetic spelling, > and in the UK, it's spelt 'colour'. In Canada as well. > It doesn't matter that some letters are silent or it isn't spelt exactly > as pronounced (which would make it more like 'culler'). It is necessary > to use 'colour' (in those regions using British English) to show that > you're not ignorant. > > Try spelling all of 'poor', 'paw', 'pore', 'pour' etc as 'por' and see > how far you get! How about gaol? It is pronounced exactly the way it is spelled: jAl (soft G, hard A, (unpronounced hard O) L). But, in North America, it is (perhaps mis)spelled "jail" and pronounced jAl (soft G, hard A, (unpronounced soft i) L). Languages, pronunciation, and spelling change region-to-region. We Canadians have learned to tolerate software spell-checkers telling us that we've misspelled colour or favour. We keep on spelling them that way, anyways. -- Lew Pitcher "In Skills, We Trust" PGP public key available upon request
[toc] | [prev] | [next] | [standalone]
| From | Ian Collins <ian-news@hotmail.com> |
|---|---|
| Date | 2015-02-06 12:15 +1300 |
| Message-ID | <cjibs8Fq43fU5@mid.individual.net> |
| In reply to | #57029 |
Lew Pitcher wrote: > On Thursday February 5 2015 16:43, in comp.lang.c, "Bartc" <bc@freeuk.com> > wrote: >> >> But never mind how it came about; English doesn't use phonetic spelling, >> and in the UK, it's spelt 'colour'. > > In Canada as well. It's a shame people keep using the terms US English and British English. It's better to say US English and everyone else's English :) -- Ian Collins
[toc] | [prev] | [next] | [standalone]
| From | David Brown <david.brown@hesbynett.no> |
|---|---|
| Date | 2015-02-06 10:08 +0100 |
| Message-ID | <mb20a0$b7r$2@dont-email.me> |
| In reply to | #57031 |
On 06/02/15 00:15, Ian Collins wrote: > Lew Pitcher wrote: >> On Thursday February 5 2015 16:43, in comp.lang.c, "Bartc" >> <bc@freeuk.com> >> wrote: >>> >>> But never mind how it came about; English doesn't use phonetic spelling, >>> and in the UK, it's spelt 'colour'. >> >> In Canada as well. > > It's a shame people keep using the terms US English and British English. > > It's better to say US English and everyone else's English :) > No, the correct terms are US English and /proper/ English!
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2015-02-06 09:19 +0000 |
| Message-ID | <mb20t1$emh$1@dont-email.me> |
| In reply to | #57043 |
On 06/02/15 09:08, David Brown wrote: > On 06/02/15 00:15, Ian Collins wrote: >> Lew Pitcher wrote: >>> On Thursday February 5 2015 16:43, in comp.lang.c, "Bartc" >>> <bc@freeuk.com> >>> wrote: >>>> >>>> But never mind how it came about; English doesn't use phonetic spelling, >>>> and in the UK, it's spelt 'colour'. >>> >>> In Canada as well. >> >> It's a shame people keep using the terms US English and British English. >> >> It's better to say US English and everyone else's English :) >> > > No, the correct terms are US English and /proper/ English! Well, no. There's just English, and people get to choose whether to use it correctly or incorrectly. The term "British English" is an abomination. Next you'll be asking us to put our country's name on our stamps. I'm beginning to think it's high time we sorted out this colonial rebellion that's been festering for the last two and a half centuries. They've been getting far too boisterous recently. And they keep turning up late when there's a war on. They need to be brought into line. Hmmm? No no no, I don't know how exactly. That's one for the strategy boffins. But I expect it will involve sending in a gunboat or something. It usually does. -- 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
[toc] | [prev] | [next] | [standalone]
| From | Robert Wessel <robertwessel2@yahoo.com> |
|---|---|
| Date | 2015-02-06 03:34 -0600 |
| Message-ID | <9f29da5d48ukvmlu3dhpvbfkep0r2vlkpv@4ax.com> |
| In reply to | #57045 |
On Fri, 06 Feb 2015 09:19:00 +0000, Richard Heathfield <rjh@cpax.org.uk> wrote: >On 06/02/15 09:08, David Brown wrote: >> On 06/02/15 00:15, Ian Collins wrote: >>> Lew Pitcher wrote: >>>> On Thursday February 5 2015 16:43, in comp.lang.c, "Bartc" >>>> <bc@freeuk.com> >>>> wrote: >>>>> >>>>> But never mind how it came about; English doesn't use phonetic spelling, >>>>> and in the UK, it's spelt 'colour'. >>>> >>>> In Canada as well. >>> >>> It's a shame people keep using the terms US English and British English. >>> >>> It's better to say US English and everyone else's English :) >>> >> >> No, the correct terms are US English and /proper/ English! > > >Well, no. There's just English, and people get to choose whether to use >it correctly or incorrectly. > >The term "British English" is an abomination. Next you'll be asking us >to put our country's name on our stamps. > >I'm beginning to think it's high time we sorted out this colonial >rebellion that's been festering for the last two and a half centuries. >They've been getting far too boisterous recently. And they keep turning >up late when there's a war on. They need to be brought into line. Hmmm? >No no no, I don't know how exactly. That's one for the strategy boffins. >But I expect it will involve sending in a gunboat or something. It >usually does. Well, the last couple of times you tried that, it didn't work out all that well. Although I suspect that if you offered to burn Washington again, a lot of colonials would be willing to look the other way for a bit... ;-)
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <kst-u@mib.org> |
|---|---|
| Date | 2015-02-06 08:22 -0800 |
| Message-ID | <ln1tm3ko23.fsf@nuthaus.mib.org> |
| In reply to | #57045 |
Richard Heathfield <rjh@cpax.org.uk> writes:
[...]
> I'm beginning to think it's high time we sorted out this colonial
> rebellion that's been festering for the last two and a half
> centuries. They've been getting far too boisterous recently. And they
> keep turning up late when there's a war on. They need to be brought
> into line. Hmmm? No no no, I don't know how exactly. That's one for
> the strategy boffins. But I expect it will involve sending in a
> gunboat or something. It usually does.
No thanks; we already have plenty of gunboats.
--
Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
[toc] | [prev] | [next] | [standalone]
| From | guinness.tony@gmail.com |
|---|---|
| Date | 2015-02-06 03:39 -0800 |
| Message-ID | <146de024-97c3-45eb-9fb4-774ca688c716@googlegroups.com> |
| In reply to | #57043 |
On Friday, 6 February 2015 09:09:02 UTC, David Brown wrote: > On 06/02/15 00:15, Ian Collins wrote: > > Lew Pitcher wrote: > >> On Thursday February 5 2015 16:43, in comp.lang.c, "Bartc" > >> <bc@freeuk.com> > >> wrote: > >>> > >>> But never mind how it came about; English doesn't use phonetic spelling, > >>> and in the UK, it's spelt 'colour'. > >> > >> In Canada as well. > > > > It's a shame people keep using the terms US English and British English. > > > > It's better to say US English and everyone else's English :) > > > > No, the correct terms are US English and /proper/ English! Yanklish and English.
[toc] | [prev] | [next] | [standalone]
| From | Kaz Kylheku <kaz@kylheku.com> |
|---|---|
| Date | 2015-02-06 15:45 +0000 |
| Message-ID | <20150206071830.966@kylheku.com> |
| In reply to | #57043 |
On 2015-02-06, David Brown <david.brown@hesbynett.no> wrote: > On 06/02/15 00:15, Ian Collins wrote: >> Lew Pitcher wrote: >>> On Thursday February 5 2015 16:43, in comp.lang.c, "Bartc" >>> <bc@freeuk.com> >>> wrote: >>>> >>>> But never mind how it came about; English doesn't use phonetic spelling, >>>> and in the UK, it's spelt 'colour'. >>> >>> In Canada as well. >> >> It's a shame people keep using the terms US English and British English. >> >> It's better to say US English and everyone else's English :) >> > > No, the correct terms are US English and /proper/ English! The US cleans up English for everyone: we can think of it as Americans are being "doctours without bordeurs" in the area of grammeur and ourthography.
[toc] | [prev] | [next] | [standalone]
| From | James Kuyper <jameskuyper@verizon.net> |
|---|---|
| Date | 2015-02-06 08:31 -0500 |
| Message-ID | <mb2fmr$63u$1@dont-email.me> |
| In reply to | #57031 |
On 02/05/2015 06:15 PM, Ian Collins wrote: > Lew Pitcher wrote: >> On Thursday February 5 2015 16:43, in comp.lang.c, "Bartc" <bc@freeuk.com> >> wrote: >>> >>> But never mind how it came about; English doesn't use phonetic spelling, >>> and in the UK, it's spelt 'colour'. >> >> In Canada as well. > > It's a shame people keep using the terms US English and British English. > > It's better to say US English and everyone else's English :) Why? While a solid majority of native speakers of English are from the US(58.5%), and those from the UK form the second largest group (15.8%), those two (groups of) dialects are far from being the only ones in widespread use. <http://en.wikipedia.org/wiki/English-speaking_world> -- James Kuyper
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2015-02-06 13:45 +0000 |
| Message-ID | <mb2gg7$926$1@dont-email.me> |
| In reply to | #57051 |
On 06/02/15 13:31, James Kuyper wrote: > On 02/05/2015 06:15 PM, Ian Collins wrote: >> Lew Pitcher wrote: >>> On Thursday February 5 2015 16:43, in comp.lang.c, "Bartc" <bc@freeuk.com> >>> wrote: >>>> >>>> But never mind how it came about; English doesn't use phonetic spelling, >>>> and in the UK, it's spelt 'colour'. >>> >>> In Canada as well. >> >> It's a shame people keep using the terms US English and British English. >> >> It's better to say US English and everyone else's English :) > > 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. > and those from the UK form the second largest group (15.8%), I think you'll find that those born in England form the /only/ group of /native/ speakers of English, so that'll be 100%. > those two (groups of) dialects are far from being the only ones in > widespread use. <http://en.wikipedia.org/wiki/English-speaking_world> FCVO "English". -- 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
[toc] | [prev] | [next] | [standalone]
| From | James Kuyper <jameskuyper@verizon.net> |
|---|---|
| Date | 2015-02-06 09:18 -0500 |
| Message-ID | <mb2if2$h3g$1@dont-email.me> |
| In reply to | #57053 |
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. -- James Kuyper
[toc] | [prev] | [next] | [standalone]
| From | wpihughes@gmail.com |
|---|---|
| Date | 2015-02-06 07:08 -0800 |
| Message-ID | <1e1160ad-246c-482a-b6d3-4489ef1f58a5@googlegroups.com> |
| In reply to | #57058 |
On Friday, February 6, 2015 at 10:18:53 AM UTC-4, 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. The problem is that the repeated misspellings in the US has rendered the denizens thereof incapable of recognizing irony or sarcasm. -William Hughes
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2015-02-06 15:15 +0000 |
| Message-ID | <mb2lp4$v2g$1@dont-email.me> |
| In reply to | #57059 |
On 06/02/15 15:08, wpihughes@gmail.com wrote: > On Friday, February 6, 2015 at 10:18:53 AM UTC-4, 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. > > > The problem is that the repeated misspellings in the US has rendered > the denizens thereof incapable of recognizing irony or sarcasm. > s/has/have/ :-) Actually, I think you're doing James an injustice. He, like me, is just keeping a very, very straight face while keeping up one end of an extraordinarily silly argument. -- 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
[toc] | [prev] | [next] | [standalone]
| From | wpihughes@gmail.com |
|---|---|
| Date | 2015-02-06 07:31 -0800 |
| Message-ID | <3f8703f8-bf4b-446d-b9ce-349e81d361fb@googlegroups.com> |
| In reply to | #57060 |
On Friday, February 6, 2015 at 11:15:34 AM UTC-4, Richard Heathfield wrote: > On 06/02/15 15:08, wpihughes@gmail.com wrote: > > On Friday, February 6, 2015 at 10:18:53 AM UTC-4, 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. > > > > > > The problem is that the repeated misspellings in the US has rendered > > the denizens thereof incapable of recognizing irony or sarcasm. > > > > s/has/have/ :-) > > Actually, I think you're doing James an injustice. He, like me, is just > keeping a very, very straight face while keeping up one end of an > extraordinarily silly argument. Hoist by my own petard. -William Hughes
[toc] | [prev] | [next] | [standalone]
| From | Richard Heathfield <rjh@cpax.org.uk> |
|---|---|
| Date | 2015-02-06 15:37 +0000 |
| Message-ID | <mb2n28$5ge$1@dont-email.me> |
| In reply to | #57061 |
On 06/02/15 15:31, wpihughes@gmail.com wrote: <snip> > > Hoist by my own petard. Forsooth! Thou art an engineer. A software engineer, presumably. But I will delve one yard below their mines, And blow them at the moon: O, 'tis most sweet, When in one line two crafts directly meet. -- 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
[toc] | [prev] | [next] | [standalone]
| From | wpihughes@gmail.com |
|---|---|
| Date | 2015-02-06 08:15 -0800 |
| Message-ID | <85a5063f-527d-4145-bcf5-c89c61c222c7@googlegroups.com> |
| In reply to | #57062 |
On Friday, February 6, 2015 at 11:37:24 AM UTC-4, Richard Heathfield wrote: > On 06/02/15 15:31, wpihughes@gmail.com wrote: > > <snip> > > > > > Hoist by my own petard. > > Forsooth! Thou art an engineer. A vile calumny! Lets Toot -William Hughes P.S. Oh saucy Worcestershire...
[toc] | [prev] | [next] | [standalone]
Page 2 of 7 — ← Prev page 1 [2] 3 4 5 6 7 Next page →
Back to top | Article view | comp.lang.c
csiph-web