Chris Torek <no****@torek.net> writes:
(I realize this is off-topic, even with the subject line change.
My apologies for continuing the thread, but I hope the idea here
will prove useful.)
Keith Thompson wrote: There are several newsgroups for test messages. alt.test is one of
them. comp.lang.c is not.
In article <11*********************@g44g2000cwa.googlegroups. com>
Vladimir S. Oka <vl**********@eu.panasonic.com> wrote:Thanks, although I knew that already.
My problem was erratic posting behaviour to c.l.c in particular, and
only c.l.c of all my subscribed groups, so I doubt that posting to
alt.test would have helped much in my investigation. ...
I have had a similar problem in the past.
The solution I used was to compose an on-topic article for the
problematic newsgroup, and then post it and observe.
In case the post failed, I kept a copy of the article, which I
could then use for the next test. If the post succeeded, I simply
contributed an on-topic article.
I think this method of testing is superior, myself. :-)
Agreed. If you have something topical to say, it's a good way to
test; if you don't, you don't really need to test whether you can post
to comp.lang.c anyway.
Having said that, I meant no offense to Vladimir. We do see people
posting test messages here just because they don't know any better.
I see now that Vladimir does know better.
Another suggestion: if you do need to post a test message to
comp.lang.c, and posting to alt.test won't work, you might briefly
mention it in the message, something like "I'd have post to alt.test,
but I'm having a problem that's specific to comp.lang.c."
These are intended as suggestions, not as criticism for not doing it
this way in the first place.
--
Keith Thompson (The_Other_Keith)
ks***@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.