Jason Dusek wrote:
> Begin forwarded message:
>
> > From: Jason Dusek <[EMAIL PROTECTED]>
> > Date: Sat Nov 22, 2003 10:10:27 PM US/Central
> > To: drieux <[EMAIL PROTECTED]>
>
> > Subject: Re: POD, Faq and tradition - Re: extracting email addys.
> > Maybe there is some way to get the FAQ to respond to messages on the
> > list - that way we wouldn't need to understand 'perldoc' and so forth.
The problem here is that perldoc is the standard means for getting
documentation. Most people here want to encourage new Perl programmers to
use this as a first reference. It is a necessary skill. If desired
information is available through the sqtandard POD, then using perldoc will
be much faster than posting to the list and waiting for an answer.
> > We newbies could just send the thing out to the list, and everyone
> > could ignore it in good conscience. If the FAQ didn't help us, we
> > could always repost with a note about "BadFAQ" in the subject line.
That is actually what peldoc -q does. One thing that might be worth trying
is to do something like the following:
perldoc perlfaq > "perldoc/perlfaq.txt". That will give you a plain-text
readout of the questions in each FAQ sheet.
I'm working on a full-text search for my archive of this list from about the
beginning of the year, up to a few weeks ago. It's a bit slow, though,
taking five or ten minutes to crawl through the 16,000+ posts, 28.8 MB, on
an "All Words" search. I'm pretty sure that the reason for this is that I'm
using regexes with the g modifier and counting matches, which adds
considerably to the parsing overhead. Something like this would be very
cumbersome to run on a busy Internet server. That's just for a text
search. Some of what you seem to envision would require artificial
intelligence of a high order, which requires even more in the way of system
resources
> > Of course some newbies are lazy, but but most of us are really
> > motivated by practicality. We often have no background in using the
> > FAQ. You might write our heuristic as:
> >
> > if ( work_to_figure_out_faq > work_to_figure_out_problem ) {
> > &AskList();
> > } else { &AskFAQ(); }
> >
> > To put it another way: if I surmise that it is easier (and faster) for
> > me to ship the problems out to you guys than it is for me to figure
> > out the FAQ, then most of the time that's what I'm going to do. This
> > is somewhat despicable I suppose - but I have work to do.
I would pretty much agree here. You should definitely look at the FAQ
first, or perldoc, but if they are not getting to the point, it doesn't hurt
to ask for help. I think a full text search through the pod could help:
That could be a pretty major undertaking, though.
>
> >
> > And on another note, what good are gurus who refuse to help the
> > humblest neophytes in their stumblings? Is it not the purpose of this
> > list to assist the ignorant, the lame and even the stupid as they seek
> > out the one true Perl? This isn't the 'true masters' list after all.
It certainly is intended to help the beginner ease his or her first steps in
Perl. I think there is also a common feeling that those first efforts will
be most productive if the new student is learning how to find the answers
for him-or-herself. Some people need more feedback than others, of course.
I think what most of us are looking for is to see students take a few steps
on their own, ask for help when they get stuck, then apply their own efforts
inputting the sufggestions offered to use.
One case in point would be newbies who consistently blow off the use of
strict and warnings, in spite of copious advice to use them. Helpers on the
list do grow impatient with that, because the student is discarding the most
available source of help in diagnosing problems. Usually, if a question is
included in the FAQ, people will simply point this out and provide sample
wording to pose the question at the command line.
It's really a matter of give and take.
> > - Jason
Joseph
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]