[31721] in Perl-Users-Digest
Perl-Users Digest, Issue: 2984 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jun 11 06:09:24 2010
Date: Fri, 11 Jun 2010 03:09:07 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 11 Jun 2010 Volume: 11 Number: 2984
Today's topics:
access to files in multiple combinations of folders? <geoff@invalid.invalid>
Re: access to files in multiple combinations of folders <marious.barrier@gmail.com>
Re: access to files in multiple combinations of folders <ben@morrow.me.uk>
Re: access to files in multiple combinations of folders <m@rtij.nl.invlalid>
Re: access to files in multiple combinations of folders <geoff@invalid.invalid>
Re: graphics <nospam-abuse@ilyaz.org>
Re: Is there a way to search all the perl document? <derykus@gmail.com>
OT: Version control (was: How to get "last action" from <john@castleamber.com>
Re: OT: Version control <ben@morrow.me.uk>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Why does perl allow so many different ways of doing <pengyu.ut@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 10 Jun 2010 23:54:58 +0100
From: Geoff <geoff@invalid.invalid>
Subject: access to files in multiple combinations of folders?
Message-Id: <74r216l42r24g8p3hgdm085j5b2m9dm6h6@4ax.com>
Hello
I would like website users to be able to have access to the files in
any combination of folders.
Say there are 20 folders, each with different files in them. User A
needs access to files in folders 1, 2 and 3, user B access to files in
folders 7, 10, 15 and 20 and so on.
Now I know I can have a .htaccess file in each folder but that would
mean giving user A three different user name and password
combinations, user B four different combinations.
Is there a better way?!
Cheers
Geoff
------------------------------
Date: Thu, 10 Jun 2010 19:20:29 -0400
From: Marious Barrier <marious.barrier@gmail.com>
Subject: Re: access to files in multiple combinations of folders?
Message-Id: <hurrjg$jjr$2@localhost.localdomain>
On 06/10/2010 06:54 PM, Geoff wrote:
> Hello
>
> I would like website users to be able to have access to the files in
> any combination of folders.
>
> Say there are 20 folders, each with different files in them. User A
> needs access to files in folders 1, 2 and 3, user B access to files in
> folders 7, 10, 15 and 20 and so on.
>
> Now I know I can have a .htaccess file in each folder but that would
> mean giving user A three different user name and password
> combinations, user B four different combinations.
>
> Is there a better way?!
>
> Cheers
>
> Geoff
I would handle everything through PHP.
------------------------------
Date: Fri, 11 Jun 2010 00:30:09 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: access to files in multiple combinations of folders?
Message-Id: <1598e7-gm03.ln1@osiris.mauzo.dyndns.org>
[f'ups set to c.l.perl.misc]
Quoth Geoff <geoff@invalid.invalid>:
>
> I would like website users to be able to have access to the files in
> any combination of folders.
>
> Say there are 20 folders, each with different files in them. User A
> needs access to files in folders 1, 2 and 3, user B access to files in
> folders 7, 10, 15 and 20 and so on.
>
> Now I know I can have a .htaccess file in each folder but that would
> mean giving user A three different user name and password
> combinations, user B four different combinations.
Why?
> Is there a better way?!
Yes, there are many. If you are talking about .htaccess files, then that
is part of your webserver's configuration; you will need to read your
webserver's documentation (or ask in a relevant group) to find out what
your options are.
If you would like to write a CGI (or some other form of server-side
program) in Perl to do the access checks, that isn't terribly hard; try
until you get stuck and then post the results and someone might help
you.
(If your inclusion of c.l.j indicates you're even considering doing this
entirely client-side, please think again.)
Ben
------------------------------
Date: Fri, 11 Jun 2010 07:53:28 +0200
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: access to files in multiple combinations of folders?
Message-Id: <ojv8e7-p39.ln1@news.rtij.nl>
On Thu, 10 Jun 2010 23:54:58 +0100, Geoff wrote:
>
> Now I know I can have a .htaccess file in each folder but that would
> mean giving user A three different user name and password combinations,
> user B four different combinations.
>
No, it doesn't. Use one htpasswd file and use the .htaccess per directory
to control who has access to that directory. It's really simple, no perl
or php needed. And access control using javascript is always a BAAAD
idea, it is always easily circumvented.
M4
------------------------------
Date: Fri, 11 Jun 2010 07:18:47 +0100
From: Geoff <geoff@invalid.invalid>
Subject: Re: access to files in multiple combinations of folders?
Message-Id: <b5l316p4d4o0eqprq8pm8buu6tsessfpt6@4ax.com>
On Fri, 11 Jun 2010 07:53:28 +0200, Martijn Lievaart
<m@rtij.nl.invlalid> wrote:
>On Thu, 10 Jun 2010 23:54:58 +0100, Geoff wrote:
>
>>
>> Now I know I can have a .htaccess file in each folder but that would
>> mean giving user A three different user name and password combinations,
>> user B four different combinations.
>>
>
>No, it doesn't. Use one htpasswd file and use the .htaccess per directory
>to control who has access to that directory. It's really simple, no perl
>or php needed. And access control using javascript is always a BAAAD
>idea, it is always easily circumvented.
Thanks Martijn,
Do you mean using require user A for example in following .htaccess?
AuthUserFile /usr/local/you/safedir/.htpasswd
AuthGroupFile /dev/null
AuthName EnterPassword
AuthType Basic
require user A
For both A and B is the line
require user A, B
or something different?
Cheers
Geoff
>
>M4
------------------------------
Date: Fri, 11 Jun 2010 03:19:34 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: graphics
Message-Id: <slrni13aq6.tt8.nospam-abuse@powdermilk.math.berkeley.edu>
On 2010-06-10, RedGrittyBrick <RedGrittyBrick@spamweary.invalid> wrote:
>> Generating PDF might be easy (did not try it),
> Yes, there appear to be some good CPAN modules for writing PDF.
>> and it is much easier to print...
> This isn't something I find any problems with. Most laser printers above
> entry level will support PostScript printing. Some of them support PDF
> printing. Most (if not all) Unix/Linux systems will have print systems
> that can rasterise PostScript for non-Postscript printers.
You have a wrong (IMO) metric of "having problems". PS is a
programming language. There is no way to "verify" PS or debug PS:
there is no way to know whether a given PS file will print on your
neighbor's PS printer except for printing it.
Likewise, if you can rasterize PS with one version of GS, this does
not imply that it would rasterize with a different version of GS.
Basically, PS leads you in the same messy can of worms as most other
programming languages (only it has no debuggers or development tools).
PDF, on the other hand, contains just DATA, not PROGRAM. It must be
easy to verify (never tried it); then any non-buggy implementation
would be able to rasterize it.
>> Myself, I would go through enscript or TeX - this would cover the
>> typesetting needs
>
> I also use enscript and a2ps. I found writing TeX (or rather LaTeX)
> still needs a lot of markup and the production chain can be complicated
> and prone to generating mysterious error messages. What TeX toolset do
> you use?
LaTeX + ams.
> prefer keeping source matter in a plain text form rather than in any
> proprietary form that is likely to become obsolete and unreadable.
It is exactly the opposite with me. LaTeX is known to be
non-backward-compatible. So I keep data in proprietary form with a
known script for to-LaTeX conversion. When backward-compatibility
breaks, I can compensate by editing the scripts...
Yours,
Ilya
------------------------------
Date: Thu, 10 Jun 2010 20:49:10 -0700 (PDT)
From: "C.DeRykus" <derykus@gmail.com>
Subject: Re: Is there a way to search all the perl document?
Message-Id: <11df319d-8fec-40b9-840f-37b28dcb5d08@r5g2000prf.googlegroups.com>
On Jun 10, 5:11=A0am, Ben Morrow <b...@morrow.me.uk> wrote:
> Quoth Peng Yu <pengyu...@gmail.com>:
>
> > Suppose I'm looking for the explanation of __END__, but I'm not sure
> > which man page I should look at. perldoc __END__ returns the following
> > error.
>
> > No documentation found for "__END__".
>
> > The dumbest way is to go through each manpage manually. But I'd like
> > to know if there is a command to automatically search which manpage
> > has the word "__END__".
>
> There is an index facility in POD, and recent versions of the docs have
> index entries in all the proper places. I cannot, however, see any way
> of looking up something in that index. The nearest switch I can see for
> perldoc would be
>
> =A0 =A0 perldoc -X __END__
>
> which just says
>
> =A0 =A0 No documentation found for "__END__".
>
> Does anyone know how to make this do something useful?
>
Evidently, the development stalled at some point.
-X expects a pod.idx to be in $Config{arch}/pod
and the thread below establishes that file isn't
generated by Pod::Index as you'd expect. However,
Pod::Index author Ivan Tubert-Brohman mentions
adding -k keyword search patch for Pod::Perldoc.
The patch never got added but the needed pieces
may still be available. See thread:
http://www.nntp.perl.org/group/perl.pod-people/2008/10/msg1350.html
--
Charles DeRykus
------------------------------
Date: Thu, 10 Jun 2010 18:35:05 -0500
From: John Bokma <john@castleamber.com>
Subject: OT: Version control (was: How to get "last action" from SVN::Client?)
Message-Id: <87r5ketqae.fsf_-_@castleamber.com>
Ben Morrow <ben@morrow.me.uk> writes:
> I've no idea, I'm afraid. I haven't used SVN for quite some time,
Did you migrate to git, and if yes was it an easy migration. As in
migrating the repositories and migrating to the new tool chain?
If not git, I am curious as well.
I use mainly subversion but want to look more into git. I know that
which vc is somewhat a matter of taste, but IMO it doesn't hurt to use
another one for a while.
Thanks,
--
John Bokma j3b
Hacking & Hiking in Mexico - http://johnbokma.com/
http://castleamber.com/ - Perl & Python Development
------------------------------
Date: Fri, 11 Jun 2010 01:28:07 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: OT: Version control
Message-Id: <nhc8e7-m113.ln1@osiris.mauzo.dyndns.org>
Quoth John Bokma <john@castleamber.com>:
> Ben Morrow <ben@morrow.me.uk> writes:
>
> > I've no idea, I'm afraid. I haven't used SVN for quite some time,
>
> Did you migrate to git, and if yes was it an easy migration. As in
> migrating the repositories and migrating to the new tool chain?
For my personal stuff I have moved entirely to git. For me by far the
biggest incentive was that it's *fast*, and it never loses its mind. The
DVCS stuff is extremely useful, but takes some getting used to before it
becomes indispensable.
The actual project that piece of code came from migrated to 'no version
control at all'. It was an attempt to get some rather non-technical
users to use VCS, with an extremely simple gui with basically just
'save a copy' and 'undo' buttons. In practice I ended up having to fix
something about the repo more often than the users made use of it, so I
abandoned the idea.
Ben
------------------------------
Date: Fri, 11 Jun 2010 02:15:56 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <aeCdnbE_udkxf4zRnZ2dnUVZ_uadnZ2d@giganews.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Fri, 11 Jun 2010 02:55:01 -0700 (PDT)
From: Peng Yu <pengyu.ut@gmail.com>
Subject: Re: Why does perl allow so many different ways of doing essentially the same thing?
Message-Id: <9013906f-01a8-479d-bf6e-022b17126efc@t10g2000yqg.googlegroups.com>
On Jun 10, 10:14=A0am, Charlton Wilbur <cwil...@chromatico.net> wrote:
> >>>>> "PY" =3D=3D Peng Yu <pengyu...@gmail.com> writes:
>
> =A0 =A0 PY> According to Programming Perl, more than one way may not alwa=
ys
> =A0 =A0 PY> be better. But I just don't see more than one way is better a=
t
> =A0 =A0 PY> all.
>
> comp.lang.python is over there; comp.lang.java is down the hall;
> comp.lang.ruby is between the two of them; and comp.lang.c++ is on the
> other side.
>
> =A0 =A0 PY> In this sense, there were a subroutine that can read multiple
> =A0 =A0 PY> lines from a file. There is no need that the users should
> =A0 =A0 PY> understand the different ways of reading muliple lines as
> =A0 =A0 PY> discussed in other thread mentioned the original post.
>
> Ah, but the reason there are multiple ways to do things is because the
> choice of which way to do things depends on the context.
>
> The best way to read *three* lines from a file is not the best way to
> read *ten thousand* lines from a file. =A0Instead of mandating one way,
> the Perl philosophy is to assume that you're a competent programmer who
> can judge the quality of various solutions for yourself.
Rather than being hypothetically saying there are different ways of
coding for different parameter values. I'd like to see what the best
code is for reading three lines and what is the best code is for
reading 10000 lines?
And I would like to know how much time and effort it would require to
know the different between the different code and how much actually
difference (say in performance or whatever metrics) can be gained by
careful choosing different ways.
> If you're a competent programmer, this is a benefit, because *you* get
> to decide what the best solution is. =A0If you're an incompetent
> programmer, this is a burden, because it requires you to think
> critically about what you're doing, and (as the hypothetical "you" is
> incompetent) you'll probably get it wrong anyway.
>
> And if you find that that last bit is too much of a burden, well, if you
> found Perl, you can find Python, C++, Ruby, or Java.
>
> Charlton
>
> --
> Charlton Wilbur
> cwil...@chromatico.net
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 2984
***************************************
