[22594] in Perl-Users-Digest
Perl-Users Digest, Issue: 4815 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Apr 4 06:11:20 2003
Date: Fri, 4 Apr 2003 03:10:11 -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, 4 Apr 2003 Volume: 10 Number: 4815
Today's topics:
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Problems with perlembed under Linux (xs_init and bo <kalinabears@hdc.com.au>
Re: subroutine ref makes a script hang using strict <tunmaster@hotmail.com>
Re: subroutine ref makes a script hang using strict <noreply@gunnar.cc>
Re: Text::ParseWords (Malcolm Dew-Jones)
Trouble addressing a variable (Andrew Fayle)
Re: Trouble addressing a variable (Anno Siegel)
Re: Trouble addressing a variable <abigail@abigail.nl>
Re: webhosts that support perl well? <Andrew.Tune@splitlock.com>
Re: Which is better - hashes or subroutines <tassilo.parseval@rwth-aachen.de>
Re: Which is better - hashes or subroutines <ubl@schaffhausen.de>
Re: Which is better - hashes or subroutines <tassilo.parseval@rwth-aachen.de>
Re: Win32::Sound::Volume() setting balance <Thomas.Kratz@lrp.de.nospam>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 04 Apr 2003 02:22:10 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <_f-dnZl8TK8v3RCjXTWcpQ@august.net>
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.4 $)
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.
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://mail.augustmail.com/~tadmc/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
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_group_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
"Jeopardy" (because the answer comes before the question), or
"TOFU".
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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Fri, 4 Apr 2003 15:35:34 +1000
From: "Sisyphus" <kalinabears@hdc.com.au>
Subject: Re: Problems with perlembed under Linux (xs_init and boot_Socket issues)
Message-Id: <3e8d1a90$0$20133@echo-01.iinet.net.au>
"David Topper" <topper@virginia.edu> wrote in message
news:3E8CDB64.9060505@virginia.edu...
<snip>
> here's the error:
>
> Can't locate loadable object for module RT in @INC (@INC ...
>
> I do have the RT.pm module in the right place. Note that the above
> error is different from:
>
> Can't locate RT.pm in @INC ...
>
> which is what it would say if it couldn't find RT.pm.
That's correct. What it's saying is that it can't find RT.so.
Why is RT.so not where it should be ? It should be in the '/auto/RT/'
sub-folder in one of your @INC directories.
Cheers,
Rob
------------------------------
Date: Fri, 04 Apr 2003 08:45:12 GMT
From: "joe" <tunmaster@hotmail.com>
Subject: Re: subroutine ref makes a script hang using strict
Message-Id: <sCbja.1495782$Wr.56047752@Flipper>
Great, I'll try this! Thanks a lot...
------------------------------
Date: Fri, 04 Apr 2003 11:36:10 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: subroutine ref makes a script hang using strict
Message-Id: <b6jk48$62qla$1@ID-184292.news.dfncis.de>
joe wrote:
> Ok, I've got slightly stuck at the following piece of code, using 'strict'.
>
> $::action = param('a');
> $::action = ($::action =~ /^(\w*)$/) ? $1:"";
>
> if (defined &$::action) {&$::action}
> else {&printPage}
>
> [snip]
>
> Isn't there a way to do this without turning 'strict' partially off?
This works:
if (defined &$::action) { &{\&$::action} }
else {&printPage}
If there are subroutines in your script, that you want to protect from
being accessed that way, you'd better use a dispatch table as
suggested by Steven and Uri.
/ Gunnar
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: 3 Apr 2003 23:34:54 -0800
From: yf110@vtn1.victoria.tc.ca (Malcolm Dew-Jones)
Subject: Re: Text::ParseWords
Message-Id: <3e8d359e@news.victoria.tc.ca>
Bob Walton (bwalton@rochester.rr.com) wrote:
: Robert Brooks wrote:
: > In article <3E8B9266.5020205@rochester.rr.com>
: > Bob Walton <bwalton@rochester.rr.com> wrote:
: >
: >> Robert Brooks wrote:
: ...
: >>> my $string = ' alpha beta';
: ...
: > I dismissed out-of-hand, and refused to believe,
: > that anyone would write a parser that returns
: > an empty value. Another example of TMTOWTDI
: ...
: Well, the reason Text::ParseWords returned an empty value was because
: your text started with a delimiter (whitespace). The word before the
: delimiter was, well, empty. Perhaps it is hard to believe anyone would
: give a parser text which starts with a delimiter?
Yes, but shellwords does claim to parse the same way as various shells,
and I don't think any normal shells parse that way.
------------------------------
Date: 4 Apr 2003 00:53:53 -0800
From: andrew.fayle@dilithiumnetworks.com (Andrew Fayle)
Subject: Trouble addressing a variable
Message-Id: <dc3b4479.0304040053.6f54e87@posting.google.com>
Hi,
I have a set of arrays numbered @OLC_0 through @OLC_9. I need to write
some code that will allow me to access any of these arrays depending
on the vailue of $num. I know this sound like I should just use a 2
dimensional array but that is not possible because this data needs to
be shared between two threads.
I have tried the code below but it doesn't work. Does anyone know how
to change this code so that it will doi what I want.
my $num=0;
my $vars = "@OLC_$num";
print STDOUT $vars."\n";
push("$vars", 5);
printf STDOUT "NUMBER = ".$OLC_0[0]."\n";
Any help is greatly appreciated
Andrew
------------------------------
Date: 4 Apr 2003 09:16:30 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Trouble addressing a variable
Message-Id: <b6jihe$e6l$1@mamenchi.zrz.TU-Berlin.DE>
Andrew Fayle <andrew.fayle@dilithiumnetworks.com> wrote in comp.lang.perl.misc:
> Hi,
>
> I have a set of arrays numbered @OLC_0 through @OLC_9. I need to write
Upper-case variables are normally reserved for special cases (system
variables, constants, package filehandles).
> some code that will allow me to access any of these arrays depending
> on the vailue of $num. I know this sound like I should just use a 2
> dimensional array but that is not possible because this data needs to
> be shared between two threads.
I'm not sure what this restriction is about (no thread experience yet).
However, you can have both. With not quite as many variables:
# declare variavles
my ( @OLC_0, @OLC_1, @OLC_2, @OLC_3, @OLC_4, @OLC_5);
# create array of refs to these
my @varlist = \ ( @OLC_0, @OLC_1, @OLC_2, @OLC_3, @OLC_4, @OLC_5);
# access some variables through the list
push @{ $varlist[ $_]}, 123 for 1, 3, 5;
push @{ $varlist[ $_]}, 456 for 2, 3, 4;
# show it worked
print "@OLC_3\n";
Anno
------------------------------
Date: 04 Apr 2003 09:34:26 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: Trouble addressing a variable
Message-Id: <slrnb8qkd1.h9b.abigail@alexandra.abigail.nl>
Andrew Fayle (andrew.fayle@dilithiumnetworks.com) wrote on MMMDIII
September MCMXCIII in <URL:news:dc3b4479.0304040053.6f54e87@posting.google.com>:
:: Hi,
::
:: I have a set of arrays numbered @OLC_0 through @OLC_9. I need to write
:: some code that will allow me to access any of these arrays depending
:: on the vailue of $num. I know this sound like I should just use a 2
:: dimensional array but that is not possible because this data needs to
:: be shared between two threads.
I fail to see why you can share 10 arrays between threads, but not a
single, multidimensional array.
:: I have tried the code below but it doesn't work. Does anyone know how
:: to change this code so that it will doi what I want.
::
:: my $num=0;
:: my $vars = "@OLC_$num";
:: print STDOUT $vars."\n";
:: push("$vars", 5);
:: printf STDOUT "NUMBER = ".$OLC_0[0]."\n";
#!/usr/bin/perl
use strict;
use warnings;
my $num = 0;
my $vars = "OLC_$num";
print $vars, "\n";
{
no strict 'refs';
push @$vars => 5;
print "NUMBER = " . $$vars [0] . "\n";
}
__END__
OLC_0
NUMBER = 5
Abigail
--
perl -MTime::JulianDay -lwe'@r=reverse(M=>(0)x99=>CM=>(0)x399=>D=>(0)x99=>CD=>(
0)x299=>C=>(0)x9=>XC=>(0)x39=>L=>(0)x9=>XL=>(0)x29=>X=>IX=>0=>0=>0=>V=>IV=>0=>0
=>I=>$==-2449231+gm_julian_day+time);do{until($=<$#r){$_.=$r[$#r];$=-=$#r}for(;
!$r[--$#r];){}}while$=;$,="\x20";print+$_=>September=>MCMXCIII=>=>=>=>=>=>=>=>'
------------------------------
Date: Fri, 04 Apr 2003 07:17:28 GMT
From: Andrew Tune <Andrew.Tune@splitlock.com>
Subject: Re: webhosts that support perl well?
Message-Id: <3E8D3186.3010006@splitlock.com>
Kevin:
Kevin Shay wrote:
> I've had good luck with Hostway: http://www.hostway.com/
My experience with Hostway has been distinctly mixed.
If all goes well, they're great. Their services (as in the attributes of
what they offer) are attractive, their reliability is good and their pricing
is attractive.
But if you need support they don't give you access to support people who
are much chop, at least not without you having to make a lot of fuss. You
end up dealing with those who don't have much clue. That wouldn't be so
much of a problem if _they_ didn't operating from the starting position
that the customer is always dumb. Not a pleasant experience.
Case in point: I needed a certain module (GDBM_File). I consulted their
documentation and they claimed to have it installed and supported.
I checked: they didn't.
I wrote them a pleasant note explaining this and asking them to install it.
They wrote back saying "Sorry, we can't help you debug your Perl scripts".
Red rag to a bull.
I wrote back with "Which part of 'perl -e "use GDBM_File;"' do you not
understand or do you think I might need help debugging? They finally
worked out I was not a moron and fixed it.
This has been my experience with them the majority of the time. I have
four or five good examples of this against one or two examples of intelligent
responses. However, in fairness to them I should say that I try hard not
to use support unless there's a REAL problem and I am pretty damn sure it's
REALLY theirs. Which I guess is an unusual approach - more's the pity.
But that shouldn't earn a customer support ethic of the sort they display.
Don't say you weren't warned. ;-) But at the same time, don't forget that
if all goes well you'll love them!
adt.
--
Andrew Tune, Splitlock Pty Ltd Cell: +61 (0) 419 654 321
ACN 101 925 642 People-proof data security. Fax: +61 3 9836 0681
http://www.splitlock.com Andrew.Tune@splitlock.com
------------------------------
Date: 4 Apr 2003 06:24:12 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: Which is better - hashes or subroutines
Message-Id: <b6j8ec$m2t$1@nets3.rz.RWTH-Aachen.DE>
Also sprach Benjamin Goldberg:
> "Tassilo v. Parseval" wrote:
> [snip]
>> sub AUTOLOAD {
>> my ($self) = @_;
>> (my $var = $AUTOLOAD) =~ s/^.+:://;
>> return if $var eq 'DESTROY';
>> if (exists $self->{$var}) {
>> *$AUTOLOAD = sub () { $self->{$var} };
>
> ITYM:
> *$AUTOLOAD = sub () { shift()->{$var} };
>
>> goto &$AUTOLOAD;
Hmmh, not sure whether I mean this. Is their a benefit of using shift() over
$self? I tested my code and it appeared to work fine.
>> } else {
>> die "Unknown word or phrase: $var\n";
>> }
>> }
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: Fri, 04 Apr 2003 08:44:15 +0200
From: Malte Ubl <ubl@schaffhausen.de>
Subject: Re: Which is better - hashes or subroutines
Message-Id: <b6jcpp$hsd$1@news.dtag.de>
Tassilo v. Parseval wrote:
> Also sprach Benjamin Goldberg:
>
>
>>"Tassilo v. Parseval" wrote:
>>[snip]
>>
>>> sub AUTOLOAD {
>>> my ($self) = @_;
>>> (my $var = $AUTOLOAD) =~ s/^.+:://;
>>> return if $var eq 'DESTROY';
>>> if (exists $self->{$var}) {
>>> *$AUTOLOAD = sub () { $self->{$var} };
What you are producing here is basically a singleton hidden behind the
generated methods. Which object is the singleton depends on which came
first.
>>
>>ITYM:
>> *$AUTOLOAD = sub () { shift()->{$var} };
This works with multiple objects, inheritance, etc.
> Hmmh, not sure whether I mean this. Is their a benefit of using shift() over
> $self? I tested my code and it appeared to work fine.
For the current application a singleton might not be such a bad idea;
however, one should probably state that more obvious.
->malte
------------------------------
Date: 4 Apr 2003 08:00:54 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: Which is better - hashes or subroutines
Message-Id: <b6je3m$qnn$1@nets3.rz.RWTH-Aachen.DE>
Also sprach Malte Ubl:
> Tassilo v. Parseval wrote:
>> Also sprach Benjamin Goldberg:
>>
>>
>>>"Tassilo v. Parseval" wrote:
>>>[snip]
>>>
>>>> sub AUTOLOAD {
>>>> my ($self) = @_;
>>>> (my $var = $AUTOLOAD) =~ s/^.+:://;
>>>> return if $var eq 'DESTROY';
>>>> if (exists $self->{$var}) {
>>>> *$AUTOLOAD = sub () { $self->{$var} };
>
> What you are producing here is basically a singleton hidden behind the
> generated methods. Which object is the singleton depends on which came
> first.
Yes, right. All derived objects will receive the value of the first
object this was called on.
>>>ITYM:
>>> *$AUTOLOAD = sub () { shift()->{$var} };
>
> This works with multiple objects, inheritance, etc.
>
>> Hmmh, not sure whether I mean this. Is their a benefit of using shift() over
>> $self? I tested my code and it appeared to work fine.
>
> For the current application a singleton might not be such a bad idea;
> however, one should probably state that more obvious.
Perhaps. When I wrote it I was more concerned with letting perl inline
the above. The shift() should make this impossible. I am no longer sure
whether mine can be inlined, but this should allow it:
*$AUTOLOAD = sub () { "$self->{$var}" };
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: Fri, 4 Apr 2003 11:10:48 +0200
From: "Thomas Kratz" <Thomas.Kratz@lrp.de.nospam>
Subject: Re: Win32::Sound::Volume() setting balance
Message-Id: <3e8d53e9.0@juno.wiesbaden.netsurf.de>
DQoiSWFuLkggW2RTXSIgPGlhbkBXSU5ET1pFZGlnaXNlcnYubmV0PiB3cm90ZS4uLg0KPiAtLS0t
LUJFR0lOIFBHUCBTSUdORUQgTUVTU0FHRS0tLS0tDQo+IEhhc2g6IFNIQTENCj4gDQo+IEEnbm9v
biBhbGwgPSkNCj4gDQo+IEV2ZW50dWFsbHkgZ2V0dGluZyBhcm91bmQgdG8gaXQsIEkga25vY2tl
ZCB1cCBhIHNtYWxsIHRlc3Qgc2NyaXB0IGZvcg0KPiB1c2luZyB0aGUgV2luMzI6OlNvdW5kIG1v
ZHVsZSBhcyBzdWdnZXN0ZWQgYnkgc29tZW9uZSBoZXJlIHdoZW4gSQ0KPiBlbnF1aXJlZCBiZWZv
cmUuIFRoZSBzY3JpcHQgaXMgYXMgZm9sbG93czoNCj4gDQo+IA0KPiAjIWQ6XHBlcmxcYmluXHBl
cmwNCj4gDQo+IHVzZSBzdHJpY3Q7DQo+IHVzZSB3YXJuaW5nczsNCj4gDQo+IHVzZSBXaW4zMjo6
U291bmQ7DQo+IFdpbjMyOjpTb3VuZDo6Vm9sdW1lKDB4RkZGRiwgMHhGRkZGKTsNCj4gV2luMzI6
OlNvdW5kOjpQbGF5KCJDOlxcV0lOTlRcXE1lZGlhXFxub3RpZnkud2F2Iik7DQo+ICNXaW4zMjo6
U291bmQ6OlZvbHVtZSgwKTsNCj4gV2luMzI6OlNvdW5kOjpTdG9wKCk7DQo+IA0KPiANCj4gVGhp
cyBkZW1vIHdvcmtzLCBidXQgaXQgc2VlbXMgdG8gc2V0IHRoZSBiYWxhbmNlIHRvIDEwMCUgbGVm
dCBhZnRlcg0KPiBwbGF5aW5nIHRoZSBzb3VuZC4gSSBhZGRlZCB0aGUgKGNvbW1lbnRlZCBvdXQp
IGxpbmUgdG8gc2V0IHRoZSB2b2x1bWUNCj4gdG8gMCBhZnRlciBhbmQgdGhpcyBhcHBlYXJzIHRv
IGxlYXZlIHRoZSBiYWxhbmNlIHNldCBjZW50cmFsbHksIGJ1dA0KPiBvYnZpb3VzbHkgc2V0cyB0
aGUgdm9sdW1lIHRvIDAgdG9vLg0KPiANCj4gSGFzIGFueW9uZSBlbHNlIGVuY291bnRlcmVkIHRo
aXMgaXNzdWUgYW5kL29yIGtub3dzIGEgd2F5IGFyb3VuZCBpdD8NCj4gDQoNCkkgaGF2ZSBoYWQg
dGhlIHNhbWUgcHJvYmxlbXMgbmVhcmx5IDIgeWVhcnMgYWdvLiBBZnRlciBsb29raW5nIGF0IHRo
ZSBXaW4zMiBBUEkgYW5kIHRoZSBYUyBjb2RlIGZvciB0aGUgbW9kdWxlIEkgY2hhbmdlZCB0aGUg
U291bmQueHMgZmlsZSBsaWtlIHRoaXMgKGRpZmYgb3V0cHV0KQ0KDQozNjIsMzYzYzM2MiwzNjMN
CjwgICAgICAgICAgICAgICAgIFhTVF9tSVYoMCwgKGxvbmcpIHZvbHVtZSAmIDB4MDBGRik7DQo8
ICAgICAgICAgICAgICAgICBYU1RfbUlWKDEsIChsb25nKSAodm9sdW1lICYgMHhGRjAwKSA+PiA4
KTsNCi0tLQ0KPiAgICAgICAgICAgICAgICAgWFNUX21JVigwLCAobG9uZykgdm9sdW1lICYgMHgw
MDAwRkZGRik7DQo+ICAgICAgICAgICAgICAgICBYU1RfbUlWKDEsIChsb25nKSAodm9sdW1lICYg
MHhGRkZGMDAwMCkgPj4gMTYpOw0KMzc0YzM3NA0KPCAgICAgICAgIHZvbHVtZSA9IFN2SVYoU1Qo
MCkpIHwgU3ZJVihTVCgwKSkgPDwgODsNCi0tLQ0KPiAgICAgICAgIHZvbHVtZSA9IFN2SVYoU1Qo
MCkpIHwgU3ZJVihTVCgwKSkgPDwgMTY7DQozODRjMzg0DQo8ICAgICAgICAgdm9sdW1lID0gU3ZJ
VihTVCgwKSkgfCBTdklWKFNUKDEpKSA8PCA4Ow0KLS0tDQo+ICAgICAgICAgdm9sdW1lID0gU3ZJ
VihTVCgwKSkgfCBTdklWKFNUKDEpKSA8PCAxNjsNCg0KQWZ0ZXIgcmVjb21waWxpbmcgdGhlIG1v
ZHVsZSBldmVyeXRoaW5nIHdvcmtlZCBhcyBkb2N1bWVudGVkLiBJIGhhdmUgc2VudCB0aGUgY2hh
Z2VzIHRvIHRoZSBhdXRob3IsIGJ1dCByZWNlaXZlZCBubyByZXNwb25zZSBhbmQgdGhlIG1vZHVs
ZSBpcyBzdGlsbCB1bmNoYW5nZWQuIEkgZG9uJ3Qga25vdyB3aGV0aGVyIHRoaXMgaXMgYmVjYXVz
ZSBvZiBteSBmaXggbm90IGJlaW5nIGNvcnJlY3Qgb3IgYmVjYXVzZSB0aGUgYXV0aG9yIHNpbXBs
eSBkb2Vzbid0IHdvcmsgb24gaXQgYW55bW9yZS4NCg0KVGhvbWFzDQo=
------------------------------
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:
The Perl-Users Digest is a retransmission of the USENET newsgroup
comp.lang.perl.misc. For subscription or unsubscription requests, send
the single line:
subscribe perl-users
or:
unsubscribe perl-users
to almanac@ruby.oce.orst.edu.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
To request back copies (available for a week or so), send your request
to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
where x is the volume number and y is the issue number.
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 V10 Issue 4815
***************************************
