Xref: utzoo comp.lang.c:34453 comp.std.c:3991
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!decwrl!infopiz!lupine!rfg
From: rfg@NCD.COM (Ron Guilmette)
Newsgroups: comp.lang.c,comp.std.c
Subject: Re: C newsgroups (was: Re: Rationale for posting draft V7 C description)
Message-ID: <2878@lupine.NCD.COM>
Date: 3 Dec 90 06:00:45 GMT
References: <2451.273eb16b@verifone.com> <2713@lupine.NCD.COM> <1990Nov16.194458.24971@athena.mit.edu>
Followup-To: comp.lang.c
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 25

In article <1990Nov16.194458.24971@athena.mit.edu> scs@adam.mit.edu (Steve Summit) writes:
>In article <2713@lupine.NCD.COM> rfg@NCD.COM (Ron Guilmette) writes:
>>This group is for discussing the use of (and the rules of) ANSI C.
>
>Which group?  Posting an article containing the words "this
>group" under a Newsgroups: line containing two groups is bound to
>be confusing (at best).

I apologize to everyone, and especially to the readers of comp.lang.c.
When I posted my wild flame about sticking to discussing ANSI C, I
confess that I did not check to see what all of the newsgroups were
that the original posting (or my follow-up) were going to.

Certainly, I have no reason to object to discussions of (so-called)
K&R C over in comp.lang.c.

I do however encourage everyone to use ANSI C instead.

Again... sorry for my goof.

-- 

// Ron Guilmette  -  C++ Entomologist
// Internet: rfg@ncd.com      uucp: ...uunet!lupine!rfg
// Motto:  If it sticks, force it.  If it breaks, it needed replacing anyway.


Brought to you by Super Global Mega Corp .com