Mail Archives: djgpp/1997/12/01/00:02:33
In article <3483335E DOT 3AB5 AT cs DOT com>, fighteer AT cs DOT com says...
>
>> >> >This is explained at some length in the DJGPP FAQ list, section
>> >> >22.16.
>> >>
>> >> Why waste everyone's time by posting this kind of useless answer? If
>> >> you didn't want to answer the question, you shouldn't have bothered
>> >> replying to it. DJ himself thought the question deserved a *real*
>> >> answer....
>> >
>> >finally, by posting a succint and correct answer, eli is saving
>> >everyone's time.
>>
>> HA! All you're really saying is with this kind of answer is that you
don't
>> know the anwser to the question. Think about it.
>
>Eli wrote the FAQ. He spends a tremendous amount of time explaining
>things to people on this user group, and it so happens that chapter
>22.16 was written to answer the exact question you asked. Why should he
>bother typing it out again if you can't be bothered to read it in the
>first place? That's the whole purpose of the FAQ list.
>
>It's perfectly reasonable for newbies to DJGPP to ask FAQs, and
>generally most people will answer their questions briefly and refer them
>to the FAQ for more information. But if you already know that the FAQ
>list exists, why not go to it _first_ instead of last? Then you'd save
>yourself the embarrassment of being told to look there, and save
>everybody else the annoyance of reading this kind of thread.
>
>P.S.: DJ's answer was just a summary of what the FAQ says.
And the FAQ didn't answer the question I had. DJ did. The fact that a lot of
people aren't finding the answers they need in the FAQ should tell you
something about FAQ. Which is that it's not meeting the needs of the users.
- Raw text -