|
|
On 29 Apr, 20:14, Eligiusz Narutowicz<eligiuszdotn...@xxxxxxxxxxx>
wrote:
> user923005 <dcor...@xxxxxxxxx> writes:
> > On Apr 29, 11:38 am, Eligiusz Narutowicz<eligiuszdotn...@xxxxxxxxxxx>
> > wrote:
> >> "Default User" <defaultuse...@xxxxxxxxx> writes:
> >> > Eligiusz Narutowicz wrote:
> >> >> Most of answers are in the FAQ, but I dont know why someone answers
> >> >> so. Why have a newsgroup if the people to help are asking this?
>
> >> > What is the reason for having a newsgroup Frequently Asked Question
> >> > list?
>
> >> I think that is very obvious. I don't know your point? So you will only
> >> point people to the FAQ?
>
> > If a well prepared and correct answer is found in the FAQ, wouldn't it
> > be a nice place to point people?
>
> >> Why do you post here then?
>
> > Brian posts here to be helpful. On those occasions when something is
> > not contained in the FAQ, he will post pertinant information regarding
> > the issue at hand.
>
> > Pretty much all usenet groups have FAQs and it is simple common
> > courtesy to read them before posting.
>
> I am sorry but I know what a FAQ is. But one can point nearly all people
> to the FAQ. Nicholas [...]
I prefer Nick to Nicholas.
> [...] was abrupt I thought in his "have you bothered to
> read the faq" comment.
I didn't intend to be abrupt but succinct. Note you have misquoted
me. What I actually wrote was:
>> since NULL can be either 0 or <void*> then how come:
> no! NULL can be defined as ((void*)0) (note the zero at the end).
> Have you read the comp.lang.c FAQ?
what you said I wrote borders on misrepresentation.
I corrected a (possible) misconception and then pointed him
at the FAQ. I did this because I believe NULL, 0, nil etc.
are confusing and the FAQ explains them well. Ben *may*
not have read these excellent explanations so I directed him
to them. What I understand of the issue is from reading the
FAQ. Why would I reproduce (badly) what has already been
done by a smarter person than myself (the FAQ writer)?
> It was just my opinions that this is not the
> right answer. One can always nicely refer people to it, but people can
> not always find what they need if they dont know what the problem
> is. Just my 2c of course. I think it is rude and you may of course think
> otherwise. I didnt see Brian posting too much help only telling people
> off so sorry if I was wrong
well rudeness is (partly) in the eye of the beholder.
--
Nick Keighley
I only see so far because I stand upon the shoulders of FAQ writers
|
|