On Thursday, May 16, 2002, at 11:52 , Dennis G. Wicks wrote:

> Yes, perldoc is only useful if you already know what
> you are looking for!

the same is equally as true about the man pages for
folks who have never been in a unix environment.

{ it is SO ANNOYING that perldoc perldoc does not have
a reference to the fact that one can get the table of
content with either
        perldoc perl
of
        perldoc perltoc

whereas man man at least gets you the feed into how
things can be started... }


> Some perlmeister should come up with something that
> does a real search for terms in the things that
> perldoc knows about that works something along the
> lines of man -k. For instance, contrast man float
> with man -k float. Until then perldoc is pretty much
> useless for us beginners!

You raise a very critical point here about one of the core problems with
getting a 'rational' definition on who are the 'RealPerlBeginners[tm]'
from the folks who have K-years of Koding, and have fallen off the wagon
into perl so that they can front end a stack of dark and evil fortran -
simply because no one has built a clean object oriented fortran GUI 
library,
with cross platform compatability that can also be quickly reconfigured to 
be a webFrontEnd, that would have allowed them to do all of that in native 
fortran....

But I am not sure that I can fully support you here.

Since even on a solaris box:

        vladimir: 51:] man -k vnode
        vladimir: 52:]

while 'everyone'[tm][1] KNOWS that one can always do the

        cd /usr/include/sys
        grep vnode *.h | more

and have more fun than a barrel of monkies.

understanding the basic commandline arguments that
can be used for doing basic searching with perldoc
I think is part and parcel of making the step over
to being a bit more than JUST a clueless newbie....

Just as knowing that '-k' was a kool option to
man - that helped get you past being merely a
clueless newbie unix perkin....

As such, I fear that a part of the process that
so clearly needs to be stressed here is how to get
over that initial hump and into the perldoc's themselves.

Either that or empowering folks to

    sub JustdoIt {

                my ( $your_reality_here, $why_not, $what_did_that_perdoc_mean ) =
                                @_ ;

                my $this;

                while(1) {
                        write_some_code(@$your_reality_here);
                        blow_it_up(@$why_not);
                        get_over_it(%$what_did_that_perdoc_mean);
                }

                return($this);  # like as if this is gonna happen.
                
     } # end of JustDoIt

hum...

        "would you call that a design error
                or a launch error?"
                        - real genius   

> And thanks for all the help!

we aim to please...

ciao
drieux

---

[1] 'everyone' and 'but everyone knows' are registered
trade marks and/or intellectual property registered
and owned by TheyThemThoseGuys Inc. and is used here
in compliance with the strict licencing requirements,
and in no way does this usage disparage their intellectual
property rights, nor anticipates that this phrase(s) can
or should be used in the public domain without the appropiate
due regard for the fully vested intellectual property rights
of TheyThemThoseGuys Inc. , their assignies, agents, co-conspirators,
or the person(s) behind the drapes who are pulling all the strings.




-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to