[31567] in Perl-Users-Digest
Perl-Users Digest, Issue: 2826 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Feb 19 09:09:23 2010
Date: Fri, 19 Feb 2010 06:09:05 -0800 (PST)
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, 19 Feb 2010 Volume: 11 Number: 2826
Today's topics:
Re: (lack of) Helpfulness of Perl error messages. <justin.0911@purestblue.com>
Re: (lack of) Helpfulness of Perl error messages. <justin.0911@purestblue.com>
Re: benchmarks for perl? <Phred@example.invalid>
Re: benchmarks for perl? <bugbear@trim_papermule.co.uk_trim>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: weird behavior when passing hashes to subroutine <patrickh@gmail.com>
Re: weird behavior when passing hashes to subroutine <spamtrap@piven.net>
Re: weird behavior when passing hashes to subroutine <justin.0911@purestblue.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 19 Feb 2010 13:01:06 -0000
From: Justin C <justin.0911@purestblue.com>
Subject: Re: (lack of) Helpfulness of Perl error messages.
Message-Id: <5d75.4b7e8b92.5d297@zem>
On 2010-02-18, sreservoir <sreservoir@gmail.com> wrote:
> On 2/18/2010 11:15 AM, Justin C wrote:
>> As some of you are probably aware I often have difficulty with Perl and
>> I ask for help here usually about once a month. I try to help myself
>> where I can, and sometimes, when I'm preparing a minimal example for
>> posting here, I find the solution to my problem. That's just happened
>> again, but only due to an error message I received from my text editor
>> and not Perl directly.
>>
>> I'm a Mac user, and code using TextMate<URL:http://macromates.com/>, it
>> has the ability to run code, I don't know how it does it, though, and
>> it's error message gave me the clue to the solution of my problem. The
>> error message on my Debian box was non-helpful.
>>
>> What is likely to be the cause of the non-helpful error message? Is the
>> version of Perl on my Mac likely more recent - I've just checked and on
>> my Debian box it's 5.10.0, while on the Mac it's 5.8.8. Does TextMate
>> have a built in Perl interpreter that gives better error messages?
>>
>> The error I saw on Debian:
>> Not a HASH reference at ... line...
>>
>> The error I saw from TextMate:
>> Can't coerce array into hash at ... line...
>
> the two messages are equally helpful if you think about it. The second
> doesn't even explicitly tell you it's a reference problem. If you need
> to, you can use diagnostics; alternatively, grep perldiag.
Maybe it's the way my brain (doesn't)work that made be deduce the
problem from that - I suppose the fact that I got two different errors
made me look more closely.
I've not used diagnostics before, and had forgotten of it's existence,
but I'll try and remember to use it in future.
> As for the line references, you can twiddle with your code so that all
> of the references aren't on a single line.
That's an idea. Thank you for your reply.
Justin.
--
Justin C, by the sea.
------------------------------
Date: Fri, 19 Feb 2010 13:10:38 -0000
From: Justin C <justin.0911@purestblue.com>
Subject: Re: (lack of) Helpfulness of Perl error messages.
Message-Id: <61fe.4b7e8dce.2f02f@zem>
On 2010-02-18, Ben Morrow <ben@morrow.me.uk> wrote:
>
> Quoth Justin C <justin.0911@purestblue.com>:
>> As some of you are probably aware I often have difficulty with Perl and
>> I ask for help here usually about once a month. I try to help myself
>> where I can, and sometimes, when I'm preparing a minimal example for
>> posting here, I find the solution to my problem. That's just happened
>> again, but only due to an error message I received from my text editor
>> and not Perl directly.
>>
>> I'm a Mac user, and code using TextMate <URL:http://macromates.com/>, it
>> has the ability to run code, I don't know how it does it, though, and
>> it's error message gave me the clue to the solution of my problem. The
>> error message on my Debian box was non-helpful.
>>
>> What is likely to be the cause of the non-helpful error message? Is the
>> version of Perl on my Mac likely more recent - I've just checked and on
>> my Debian box it's 5.10.0, while on the Mac it's 5.8.8. Does TextMate
>> have a built in Perl interpreter that gives better error messages?
>
> You could have answered this easily by running the code from the
> command-line on your Mac. (You would have got the same error message as
> from TextMate.)
>
>> The error I saw on Debian:
>> Not a HASH reference at ... line...
>>
>> The error I saw from TextMate:
>> Can't coerce array into hash at ... line...
>
> The change in error message is due to the different perl versions. The
> 'Can't coerce...' message comes from the pseudohash code, which was
> removed in 5.10, whereas the 'Not a %s reference' is a generic message
> for situations where a value holds the wrong kind of ref.
>
> Before you start thinking this change was a bad idea, try running
>
> perl -le'my $x = [{a => 1}, "b"]; print $x->{a}'
>
> on both machines and consider how hard *that* would have been to debug
> with the 5.8 behaviour :).
That looks a bit circular, I suppose that that is your point. Under
5.8.8 I get 'b' and under 5.10.0 I get 'Not a HASH reference...', how
$x->{a} gets to be 'b' is the circular part. If you were expecting '1'
then, yes I can see how debugging that would be tough - especially as
"it worked", quite a shortage of warnings!
I have added "use diagnostics" to my "tesp.pl" file, where I put problem
code reduced to it's minimum parts so that I can work through the
problem. I'm in that file often enough that I'll see it and add it to
anything I'm working on that's giving me grief.
Thanks for the reply.
Justin.
--
Justin C, by the sea.
------------------------------
Date: Thu, 18 Feb 2010 22:25:14 -0700
From: Phred Phungus <Phred@example.invalid>
Subject: Re: benchmarks for perl?
Message-Id: <7u6llsFbe0U1@mid.individual.net>
sln@netherlands.com wrote:
> On Thu, 18 Feb 2010 16:25:33 +0000, bugbear <bugbear@trim_papermule.co.uk_trim> wrote:
>
>> No, I'm not starting yet another perl vs C thread.
>>
>> I have some concerns about the performance
>> of perl varying more than I would expect
>> between different installations I'm maintaining
>> (and running my perl code on)
>>
> I don't know but I just found out that the percentage
> of time involved with the 'Growing' (only) of scalars
> on a Windows box is from 35 to 100 times more than
> on a *nix box. This is due to win32 realloc in the
> linked crt library (and this is due to calling heap
> primatives), not to Perl itself.
>
> Though pre-allocating buffers will solve the problem
> as it calls malloc once and avoids realloc() flavors,
> but this is not dynamic.
>
> I'd say this is a big deal, depending on your code.
>
> http://www.perlmonks.org/?node_id=810276
>
> -sln
And then there's the time for coding as opposed to the time for execution.
I've been working up the same material with differing syntaxes for the
*nix platform, and the perl version may have taken me 48 hours.
I'm getting closer to a C solution, because I'm hauling Heathfield's DL
list library with me this time, but it's been a month at least.
I'm a person who would gladly leave this task to the implementation.
--
fred
------------------------------
Date: Fri, 19 Feb 2010 09:21:28 +0000
From: bugbear <bugbear@trim_papermule.co.uk_trim>
Subject: Re: benchmarks for perl?
Message-Id: <jfadnXYxxLWFxePWnZ2dnUVZ7tCdnZ2d@brightview.co.uk>
Ben Morrow wrote:
> Quoth bugbear <bugbear@trim_papermule.co.uk_trim>:
>> No, I'm not starting yet another perl vs C thread.
>>
>> I have some concerns about the performance
>> of perl varying more than I would expect
>> between different installations I'm maintaining
>> (and running my perl code on)
>
> Are these different versions of perl? There are often large differences
> in performance between major version, in both directions (depending on
> what exactly you're doing).
>
>> Is there a standard benchmark, used (perhaps)
>> when people port Perl to different CPUs/OS/compilers?
>
> There is perlbench on CPAN, but I believe it's not considered to be as
> representative as it used to be.
I downloaded this (shortly after my first post).
I must be missing something - it only runs 8 tests, none
of which look very "general";
perl-5.10.0 (DEBUGGING)
@bugbear-dell
app/podhtml 674.190 ms �-11.429
startup/noprog 2.484 ms �-2.098
statement/func-call-empty-5arg 1.058 �s �-0.020
statement/func-call-empty-2arg 670.138 ns �-20.012
statement/func-call-empty-1arg 397.798 ns �-7.001
statement/func-call-empty-0arg 215.374 ns �-2.893
statement/assign-int 68.174 ns �-1.229
statement/inc 46.290 ns �-1.217
is there a separate Module of tests, with perlbench being
just a harness?
(the funny character appears to be a further perlbench bug).
> Running the core test suite, or the test suite of any large CPAN
> distribution that does the sort of work you are interested in, is often
> good enough.
Interesting suggestion - can you recommend a "Generic" package
with a good test suite?
I really am concerned with Perl itself at the moment - literally
stuff like regexp evaluation, code parse time, has lookup, integer
arithmetic, real "nuts and bolts".
BugBear
------------------------------
Date: Fri, 19 Feb 2010 02:13:43 -0600
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <UMadnfx7ELmq1ePWnZ2dnUVZ_gCdnZ2d@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/"
------------------------------
Date: Thu, 18 Feb 2010 23:44:07 -0800 (PST)
From: Patrick Hartman <patrickh@gmail.com>
Subject: Re: weird behavior when passing hashes to subroutine
Message-Id: <7b0e2fe2-2ca5-4b15-9322-fe8fac1de530@b2g2000yqi.googlegroups.com>
On Feb 18, 8:11=A0pm, John Bokma <j...@castleamber.com> wrote:
> You have to be aware that the hash eats up @_ (it's the same if you use
> an array, i.e. my ( @foo, $bar ) =3D @_; will result in all of @_ ending
> up in @foo).
Thanks John, that explanation made the most sense. I was unaware that
using a hash or array gobbled up all the @_ contents, this behavior
makes sense now I know that.
Thanks everyone else for the input and suggestions. Hash references
are still foreign to me (I have seen them but don't really understand
them). I am still working through the end of the Llama book, but I
have the Alpaca book waiting on my desk for when I am done. I know it
covers references so hoping that will give me some clarity.
I am still in the beginning of the learning process, so I appreciate
all the help on here.
Patrick
------------------------------
Date: Fri, 19 Feb 2010 05:55:33 -0600
From: Don Piven <spamtrap@piven.net>
Subject: Re: weird behavior when passing hashes to subroutine
Message-Id: <IqGdnfgPU4So4ePWnZ2dnUVZ_vOdnZ2d@speakeasy.net>
sreservoir wrote:
> On 2/18/2010 9:21 PM, Don Piven wrote:
>> That's a compile-time error, since the compiler has to know how many
>> elements are in the initializer in order to know if it's an odd number.
>> The compiler won't see a problem with %hash = @_ since it has no clue
>> how long @_ is going to be.
>
> no. it is not.
>
> perl -We 'sub a { %_ = @_ } a(0)' -> warning
> perl -e 'sub a { %_ = @_ } a(0)' -> nothing
>
I stand corrected :-) Thanks.
------------------------------
Date: Fri, 19 Feb 2010 13:39:46 -0000
From: Justin C <justin.0911@purestblue.com>
Subject: Re: weird behavior when passing hashes to subroutine
Message-Id: <63a7.4b7e94a2.b4fda@zem>
On 2010-02-19, Patrick Hartman <patrickh@gmail.com> wrote:
> Hi all, I was working on a program today and made a sub routine that I
> was passing a few scalars and also a hash to as arguments. This is
> what I initially tried:
>
> my %foo = qw(pepsi cola doctor pepper seven up);
> my $bar = 'soda is yummy!';
>
> &drink(%foo,$bar);
see 'Pass by Reference' in perdoc perlsub
The scalar isn't a problem, it's the hash so I'd do:
&drink(\%foo, $bar); # passes a reference to the hash, not the hash
(someone will probably come along in a minute and tell you that you
shouldn't be using the & calling your subs unless you know why you need
to. I still don't understand this so I keep out of those discussions and
never use the & anyway).
>
> sub drink {
my ($foo, $bar) = @_;
> my (%sodas,$opinion) = @_;
>
> # do whatever here
dereference the hashref here (it's all in perlsub)
> print "yummy!";
> }
>
> The result was not what I was expecting. The $bar value that I was
> expecting to be the $opinion scalar ended up as a extra key in the
> %sodas hash as undef, and $opinion was empty. I played around a little
> and found that if I reverse the order so the scalar is passed before
> the hash, it worked like I was hoping:
>
> my %foo = qw(pepsi cola doctor pepper seven up);
> my $bar = 'soda is yummy!';
>
> &drink($bar,%foo);
>
> sub drink {
> my ($opinion,%sodas) = @_;
>
> # do whatever here
> print "yummy!";
> }
>
> Is there a rule as to what order to pass types to a subroutine? I'm a
> little confused on this one. Thanks,
>
> Patrick
Justin.
--
Justin C, by the sea.
------------------------------
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 2826
***************************************
