Re: [PATCH 5.005_63 DOC] Readability patch to perlmod

[Peter Scott <Peter@PSDT.com>]

At 02:50 PM 1/17/00 +0900, scozens@pwj.co.jp wrote:
>This makes it read a little better, but still needs some thought;
>Benchmark isn't `the same name' as Benchmark.pm

And it has problems with embedded ::.  Although one could argue that since 
it's an introduction, with the gory details later, it doesn't have to be 
complete.

>Any suggestions/recasts greatly appreciated.

How about saying "A module is a file containing a Perl package with a name 
that's a function of the filename or path."  Now the reader will be clued 
into reading further to find out what that function is.  Always begin with 
a hook, editors say...

>Incidentally, I have an issue with `library file': it's used variously
>to mean `a file in the standard set of modules, which we call the module
>library' and `a Perl4-ish .pl file'. So a library file is a file which
>is something like a module but not quite, or a file which is one of a
>set of standard files and which may or may not be a library file
>(sense 1). ETOOCONFUSING! I've had people confused as to what a/the
>`Perl library' is because of this, so is there a chance we choose one
>meaning and stick to it?

Here's another meaning, from perlvar:

It initially consists of the arguments to any B<-I> command line switches,
followed by the default Perl library, probably F</usr/local/lib/perl>,
followed by ".", to represent the current directory.

>(flames to simon@brecon.co.uk please, not this address.)

Impressive bilocation abilities there...

--
Peter Scott
Pacific Systems Design Technologies

---

References to:

scozens@pwj.co.jp

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---