[20015] in Perl-Users-Digest
Perl-Users Digest, Issue: 2210 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Nov 26 14:16:13 2001
Date: Mon, 26 Nov 2001 11:15:18 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Message-Id: <1006802118-v10-i2210@ruby.oce.orst.edu>
Content-Type: text
Perl-Users Digest Mon, 26 Nov 2001 Volume: 10 Number: 2210
Today's topics:
Statistics for comp.lang.perl.misc <gbacon@cs.uah.edu>
Re: String matching... irc hostmasks <mercutio@digitalrice.com>
System call return value 256 - Bad file descriptor (Bryce Pursley)
Re: System call return value 256 - Bad file descriptor <godzilla@stomp.stomp.tokyo>
Top-posts <admin@asarian-host.net>
Re: Top-posts <rsherman@ce.gatech.edu>
Re: Top-posts <5l259r001@sneakemail.com>
Re: Top-posts <admin@asarian-host.net>
Re: Why doesn't Perl define an evaluation order? <dan@tuatha.sidhe.org>
Why use backslash before the array and hash varible? (Andrew Meng)
Re: Why use backslash before the array and hash varible <5l259r001@sneakemail.com>
Re: win32::ole - change excel worksheet name (Bobby Ray)
Re: win32::ole - change excel worksheet name <jimbo@soundimages.co.uk>
Re: { in s///; ? <jeffp@crusoe.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 26 Nov 2001 17:38:59 -0000
From: Greg Bacon <gbacon@cs.uah.edu>
Subject: Statistics for comp.lang.perl.misc
Message-Id: <u04vhj2e3r7aa3@corp.supernews.com>
Following is a summary of articles spanning a 7 day period,
beginning at 19 Nov 2001 17:40:50 GMT and ending at
26 Nov 2001 15:45:30 GMT.
Notes
=====
- A line in the body of a post is considered to be original if it
does *not* match the regular expression /^\s{0,3}(?:>|:|\S+>|\+\+)/.
- All text after the last cut line (/^-- $/) in the body is
considered to be the author's signature.
- The scanner prefers the Reply-To: header over the From: header
in determining the "real" email address and name.
- Original Content Rating (OCR) is the ratio of the original content
volume to the total body volume.
- Find the News-Scan distribution on the CPAN!
<URL:http://www.perl.com/CPAN/modules/by-module/News/>
- Please send all comments to Greg Bacon <gbacon@cs.uah.edu>.
- Copyright (c) 2001 Greg Bacon.
Verbatim copying and redistribution is permitted without royalty;
alteration is not permitted. Redistribution and/or use for any
commercial purpose is prohibited.
Excluded Posters
================
perlfaq-suggestions\@(?:.*\.)?perl\.com
faq\@(?:.*\.)?denver\.pm\.org
Totals
======
Posters: 269
Articles: 954 (401 with cutlined signatures)
Threads: 219
Volume generated: 1981.1 kb
- headers: 829.6 kb (15,862 lines)
- bodies: 1087.1 kb (35,543 lines)
- original: 707.8 kb (25,408 lines)
- signatures: 63.5 kb (1,457 lines)
Original Content Rating: 0.651
Averages
========
Posts per poster: 3.5
median: 1 post
mode: 1 post - 138 posters
s: 6.2 posts
Posts per thread: 4.4
median: 3 posts
mode: 1 post - 63 threads
s: 6.2 posts
Message size: 2126.5 bytes
- header: 890.5 bytes (16.6 lines)
- body: 1166.8 bytes (37.3 lines)
- original: 759.7 bytes (26.6 lines)
- signature: 68.2 bytes (1.5 lines)
Top 10 Posters by Number of Posts
=================================
(kb) (kb) (kb) (kb)
Posts Volume ( hdr/ body/ orig) Address
----- -------------------------- -------
46 112.9 ( 43.1/ 60.8/ 33.3) mgjv@tradingpost.com.au
37 93.8 ( 33.9/ 58.8/ 43.5) "Godzilla!" <godzilla@stomp.stomp.tokyo>
33 93.3 ( 37.6/ 51.1/ 38.3) tadmc@augustmail.com
31 70.9 ( 27.5/ 33.8/ 14.9) Uri Guttman <uri@stemsystems.com>
25 92.1 ( 26.7/ 65.3/ 58.9) "Steffen Müller" <5l259r001@sneakemail.com>
22 36.7 ( 20.4/ 16.1/ 10.7) Bart Lateur <bart.lateur@skynet.be>
21 31.4 ( 18.0/ 13.4/ 6.3) Bernard El-Hagin <bernard.el-hagin@lido-tech.net>
19 33.8 ( 18.0/ 15.6/ 9.1) Bart Lateur <bart.lateur@pandora.be>
18 40.2 ( 16.2/ 18.5/ 11.7) Mark Jason Dominus <mjd@plover.com>
17 28.4 ( 13.1/ 15.3/ 7.3) Anno Siegel <anno4000@lublin.zrz.tu-berlin.de>
These posters accounted for 28.2% of all articles.
Top 10 Posters by Volume
========================
(kb) (kb) (kb) (kb)
Volume ( hdr/ body/ orig) Posts Address
-------------------------- ----- -------
112.9 ( 43.1/ 60.8/ 33.3) 46 mgjv@tradingpost.com.au
93.8 ( 33.9/ 58.8/ 43.5) 37 "Godzilla!" <godzilla@stomp.stomp.tokyo>
93.3 ( 37.6/ 51.1/ 38.3) 33 tadmc@augustmail.com
92.1 ( 26.7/ 65.3/ 58.9) 25 "Steffen Müller" <5l259r001@sneakemail.com>
71.5 ( 0.6/ 70.9/ 66.4) 1 Gary <healthrx@yahoo.com>
70.9 ( 27.5/ 33.8/ 14.9) 31 Uri Guttman <uri@stemsystems.com>
47.8 ( 21.9/ 25.9/ 16.6) 17 "Mark" <admin@asarian-host.net>
40.2 ( 16.2/ 18.5/ 11.7) 18 Mark Jason Dominus <mjd@plover.com>
36.7 ( 20.4/ 16.1/ 10.7) 22 Bart Lateur <bart.lateur@skynet.be>
33.8 ( 18.0/ 15.6/ 9.1) 19 Bart Lateur <bart.lateur@pandora.be>
These posters accounted for 35.0% of the total volume.
Top 10 Posters by OCR (minimum of five posts)
==============================================
(kb) (kb)
OCR orig / body Posts Address
----- -------------- ----- -------
0.993 ( 2.8 / 2.8) 6 "MisterSoftware" <moodie@fast.net>
0.992 ( 2.7 / 2.8) 6 "Jason Gray" <perl@cableone.net>
0.930 ( 4.0 / 4.3) 5 Dale Henderson <nilram@boisdarc.tamu-commerce.edu>
0.901 ( 58.9 / 65.3) 25 "Steffen Müller" <5l259r001@sneakemail.com>
0.794 ( 4.3 / 5.5) 6 robtompc@yahoo.com
0.766 ( 12.5 / 16.4) 10 Joe Schaefer <joe+usenet@sunstarsys.com>
0.766 ( 4.4 / 5.7) 8 "Alan J. Flavell" <flavell@mail.cern.ch>
0.759 ( 3.8 / 4.9) 5 mike <mjc@drizzle.net>
0.748 ( 38.3 / 51.1) 33 tadmc@augustmail.com
0.740 ( 43.5 / 58.8) 37 "Godzilla!" <godzilla@stomp.stomp.tokyo>
Bottom 10 Posters by OCR (minimum of five posts)
=================================================
(kb) (kb)
OCR orig / body Posts Address
----- -------------- ----- -------
0.455 ( 2.8 / 6.2) 8 Chris Fedde <cfedde@fedde.littleton.co.us>
0.440 ( 14.9 / 33.8) 31 Uri Guttman <uri@stemsystems.com>
0.437 ( 2.5 / 5.8) 6 "MAGiC MANiAC^mTo" <no_mto@hotmail.com>
0.432 ( 2.6 / 6.1) 7 Mona Wuerz <wuerz@yahoo.com>
0.429 ( 5.1 / 11.9) 7 Benjamin Goldberg <goldbb2@earthlink.net>
0.411 ( 3.3 / 8.0) 5 hugo <hugo@fractalgraphics.com.au>
0.360 ( 4.1 / 11.4) 12 Ilya Martynov <ilya@martynov.org>
0.352 ( 2.3 / 6.4) 6 Amer Neely <aneely@softouch.on.ca>
0.333 ( 2.0 / 6.0) 6 "John W. Krahn" <krahnj@acm.org>
0.217 ( 2.3 / 10.4) 5 "Mina Naguib" <spam@thecouch.homeip.net>
54 posters (20%) had at least five posts.
Top 10 Threads by Number of Posts
=================================
Posts Subject
----- -------
38 variable scope
36 A Perl Bug?
31 Can I avoid 2 passes?
24 Using CGI.pm to obtain a list of params
19 How can you do a safe unlink?
17 using sendmail from perl
17 Traversing directories
17 File locking question
15 Enigma encryption
14 use File:Find non-recursive
These threads accounted for 23.9% of all articles.
Top 10 Threads by Volume
========================
(kb) (kb) (kb) (kb)
Volume ( hdr/ body/ orig) Posts Subject
-------------------------- ----- -------
90.8 ( 39.6/ 47.1/ 29.1) 38 variable scope
88.8 ( 20.4/ 66.7/ 49.1) 19 How can you do a safe unlink?
85.3 ( 33.8/ 47.7/ 26.6) 36 A Perl Bug?
75.2 ( 2.2/ 72.5/ 68.0) 3 Perl Programmer Needed to modify shopping cart
62.7 ( 29.3/ 31.0/ 19.7) 31 Can I avoid 2 passes?
52.7 ( 25.1/ 27.0/ 17.0) 24 Using CGI.pm to obtain a list of params
40.4 ( 11.9/ 27.0/ 15.9) 13 Creating a Perl app. Help with installation?
35.2 ( 10.3/ 24.8/ 8.5) 10 IO::Select and IO::Socket question: multiple connections
33.8 ( 16.2/ 16.0/ 11.6) 17 Traversing directories
33.1 ( 14.9/ 17.5/ 10.0) 17 using sendmail from perl
These threads accounted for 30.2% of the total volume.
Top 10 Threads by OCR (minimum of five posts)
==============================================
(kb) (kb)
OCR orig / body Posts Subject
----- -------------- ----- -------
0.890 ( 12.4/ 14.0) 7 File position of of every word in a file
0.810 ( 5.9/ 7.3) 5 Fastest way to eliminate words < 4 characters long except month abbreviations?
0.797 ( 2.0/ 2.5) 5 a beginner
0.796 ( 10.5/ 13.2) 11 replacing certain 'bad' words globally
0.789 ( 8.5/ 10.7) 14 modify arguments in a sub / function...
0.737 ( 49.1/ 66.7) 19 How can you do a safe unlink?
0.723 ( 11.6/ 16.0) 17 Traversing directories
0.706 ( 2.5/ 3.5) 5 How do I extract the rest of a string when encounter a specific word?
0.701 ( 11.2/ 16.0) 13 need help with a seemingly simple regex
0.680 ( 2.0/ 2.9) 8 EOF testing
Bottom 10 Threads by OCR (minimum of five posts)
=================================================
(kb) (kb)
OCR orig / body Posts Subject
----- -------------- ----- -------
0.479 ( 1.9 / 4.0) 7 bareword?
0.468 ( 2.8 / 5.9) 6 Template System
0.467 ( 1.9 / 4.0) 8 a simple question
0.460 ( 2.5 / 5.4) 5 help w/ error: 'package does not return true'
0.439 ( 4.2 / 9.6) 11 Problems with Mirror - ftp.pl doesn't get the right octal for chmod
0.428 ( 7.5 / 17.4) 14 use File:Find non-recursive
0.412 ( 2.0 / 4.8) 6 [Newbie] Iterating through dirs recursively
0.404 ( 2.6 / 6.4) 7 Perl generating JavaScript problem
0.343 ( 8.5 / 24.8) 10 IO::Select and IO::Socket question: multiple connections
0.331 ( 1.1 / 3.4) 6 .htaccess with Perl
61 threads (27%) had at least five posts.
Top 10 Targets for Crossposts
=============================
Articles Newsgroup
-------- ---------
18 comp.lang.perl.modules
10 alt.perl
5 nyc.food
5 comp.lang.java.programmer
5 comp.lang.basic.visual
5 comp.lang.ada
5 comp.object
5 comp.lang.c++
5 comp.lang.eiffel
3 comp.lang.perl
Top 10 Crossposters
===================
Articles Address
-------- -------
7 Mark Jason Dominus <mjd@plover.com>
7 jerry@iss.u-net.com
7 Patrick Doyle <doylep@eecg.toronto.edu>
7 IsraelRT <israelrt@optushome.com.au>
7 Gregor <gg@gg.net>
6 Zoltan Kandi <zoltan.kandi@tellabs.com>
4 Brice Ruth <brice@webprojkt.com>
3 "Jason Gray" <perl@cableone.net>
3 "Mina Naguib" <spam@thecouch.homeip.net>
3 "Eric McDaniel" <ericm@vertical.com>
------------------------------
Date: Mon, 26 Nov 2001 15:00:29 -0000
From: "Mercutio" <mercutio@digitalrice.com>
Subject: Re: String matching... irc hostmasks
Message-Id: <9ttlqh$24p$1@newsg1.svr.pol.co.uk>
Jonas Nilsson wrote in message <9ttaf3$e4g$1@news.island.liu.se>...
>| I'm looking for a snippet of code that will match a host address to a
host
>| mask.
>|
>Try this:
>use strict;
>my $address = 'Nickname!~name@nice.address.org';
>my @nomatch =
>('Nickname!~xxxx@nice.address.org','Nickname!~name@nice.address.com');
>my $hostmask = '*!*name*@*.address.org';
>my $hostmatch='^'.join('.*',map "\Q$_",split('\*',$hostmask)).'$';
>for ($address,@nomatch) {
> print "$_ is a match\n" if /$hostmatch/i;
> print "$_ isn't a match\n" unless /$hostmatch/i;
>}
>/jN
Cheers, that seems to do the job ok... as a sidenote, I was also sent this
snippet of code by a friend...
@hostmasks = ("*!*name@*.address.com", "*!*other@*.other.org");
if (checkAddress("SomeName!myname@this.address.com")) {
...
}
sub checkAddress {
my $hostname = shift;
foreach $mask (@hostmasks) {
$hostmask = $mask;
$hostmask =~ s/\./\\\./g;
$hostmask =~ s/\*/\.\*/g;
if ($hostname =~ /$hostmask/) {
return 1;
}
}
return 0;
}
Can I get an opinion or two on this by you guys?
I'm still looking into different ways, I want to find the most foolproof
method of doing it...
Cheers,
Tony
------------------------------
Date: Mon, 26 Nov 2001 16:15:52 GMT
From: hbpursle@duke-energy.com (Bryce Pursley)
Subject: System call return value 256 - Bad file descriptor
Message-Id: <3c0267b3.5762586@news.infoave.net>
A line of code that has worked for over a month has all of a sudden
gone "intermittent." One day it won't work at all and the next day it
will work on every other file passed to it. If it wasn't for the
"every other file" thing, I would have guessed I had a path or
permission problem but when it works on every other file it doesn't
make any sense to me. I can't find any detailed help for this error
message either. It seems to be a fairly generic error msg from what I
read. I have included the key line of code, a portion of the
subroutine it lives in and some output from my logfile below. Thanks
for any help on this.
Bryce
This is the line of code that is generating the error:
$rtn_val = system ("$dirapps\\batch2raw.exe -t -n $file >>
$dircdrpro\\$cdname.pol");
This is "a portion" of the subroutine that contains the line just in
case it is helpful to see how I get to this point.
sub cdrprocess
{
my $file;
chdir ($dircdrpro) or die "can't change to . . . $dircdrpro : $!";
opendir THISDIR, "." or die "can't open current directory: $!";
@allfiles = grep !/^\.\.?$/, readdir THISDIR;
closedir THISDIR;
foreach $file (@allfiles)
{
if (-d $file)
{
#print2both ("\tDIR - $file\n");
}
else # continue process if file is not a directory
{
open (CDRFILE, $file) or die "can't open CDRFILE = $file: $!";
while (<CDRFILE>)
{
if (/^CD:(.*)/)
{
$cdname = $1;
last;
}
} #end while
$rtn_val = system ("$dirapps\\batch2raw.exe -t -n $file >>
$dircdrpro\\$cdname.pol");
if ($rtn_val)
{
print2both ("\tSystem call failed. Return value is $rtn_val. Error
is $!\n");
}
else
{
print2both ("\tSystem call succeeded.\n");
} #end else for system call
} #end else to process files
} #end foreach
This is some output from my logfile:
ALLENSTM - CDR FILE -> 1006660839-8.dat
System call succeeded.
BADCREEK - CDR FILE -> 1006660913-9.dat
System call failed. Return value is 256. Error is Bad file descriptor
BELWSCRK - CDR FILE -> 1006660977-9.dat
System call succeeded.
BUCKSTEM - CDR FILE -> 1006660989-8.dat
System call failed. Return value is 256. Error is Bad file descriptor
BUZZROST - CDR FILE -> 1006661008-7.dat
System call succeeded.
CATAWBA - CDR FILE -> 1006661133-8.dat
System call failed. Return value is 256. Error is Bad file descriptor
CHESTER - CDR FILE -> 1006661152-7.dat
System call succeeded.
CHAPHILL - CDR FILE -> 1006661153-9.dat
System call failed. Return value is 256. Error is Bad file descriptor
CLEMSCMC - CDR FILE -> 1006661216-7.dat
System call succeeded.
CLEMSON - CDR FILE -> 1006661253-8.dat
System call failed. Return value is 256. Error is Bad file descriptor
CLIFSIDE - CDR FILE -> 1006661315-7.dat
System call succeeded.
------------------------------
Date: Mon, 26 Nov 2001 10:31:27 -0800
From: "Godzilla!" <godzilla@stomp.stomp.tokyo>
Subject: Re: System call return value 256 - Bad file descriptor
Message-Id: <3C028A7F.67CD7847@stomp.stomp.tokyo>
Bryce Pursley wrote:
(snipped)
> A line of code that has worked for over a month has all of a sudden
> gone "intermittent." One day it won't work at all and the next day it
> will work on every other file passed to it.
Nothing else needs to be said. It is clear based on your
statements something has changed. Either ascertain what
you have changed or contact your server and ascertain
what they have changed. Doing so will provide you with
a clear definitive answer.
Godzilla!
------------------------------
Date: Mon, 26 Nov 2001 16:41:14 GMT
From: "Mark" <admin@asarian-host.net>
Subject: Top-posts
Message-Id: <KguM7.46316$YD.3975386@news2.aus1.giganews.com>
It never ceases to amaze me what gets people's hair in a knot. :) So, let me
get un-entangled myself, and fling out some apodictic opinions of my own. :)
I guess the most compelling reason not to top-post is because, in Western
society, people read from left to right, and from top to bottom. In our
thinking and language we transpose that same "chronology": we take things
from the top, not from the bottom.
Although I am not a huge proponent of whacking people over the head with
netiquette for no greater reason than that someone maintains a netiquette
document somewhere that he angrily refers to, still, netiquette is not an
arbitrarily jumbled together batch of rules either. The chronology aspect of
things, as I mentioned, is one rather decent argument to state why posting
from top to bottom is very intuitive, and why top-posting kinda breaks that
flow and should thus, imo, be discouraged.
Netiquette has no leading industry institution behind its formation that
lends it any formal authority. Netiquette is not an RFC, for instance, and
should not be treated with the same authority. Since Netiquette is really no
more than a collected reflection of how things are currently, and
predominantly, done, that concept, by its very definition, does not preclude
the possibility for change -- any grinding of teeth despite. :) So, he who
concerns himself with Netiquette should always keep in mind that Netiquette
is dynamic.
It is often argued that newbies are derelict in doing their homework, for
instance. They receive angry responses as to why they did not visit
news.newusers.questions or something. And why did they not do so? Because
they did not know of its existence, as simple as that. This may well elicit
some surly comments to the effect of that they should come prepared and
such. But the underlying reason for their ignorance is simply because
computers have become more and more "domesticated", as it were. And if the
history of science shows one thing with glaring clarity, then it is this
inevitable law:
"The more people use it, the less people will know how it works."
This law seems rather self-evident, because it is has a "clear and present"
correlation with how intelligence is distributed in a population; simply
put: not everybody is smart, so, if everybody uses a computer, it logically
follows, as night does day, that almost nobody knows what they are doing
(both technically as Netiquette-wise.) It used to be that way with cars. The
first people who had car knew everything about it; they were the "geeks" of
their time; nowadays, however, when everybody has a car, practically no one
really knows anything about their car. And yet, they still use their car. If
any of these people were to get a thrashing by a mechanic for not having
read some geek manual, and why they did not know this or that, people would
simply shudder and say: "Because I do not care; it is just a tool to me."
Same with computers. Lotsa people have computers; and they simply hit
'reply' when they email or post. And since their posting software brings
them to the top of the post, that is where they post. Now, hear my argument
well, because I am not qualifying this as good or bad per se. It simply
"is". Arguably, one can retort that the required level of knowledge depends
on where one posts. And this is true, of course. A perl programmer in a perl
group can be expected to have reasonably familiarized himself with current
Netiquette prior to his arrival. But for a newbie who just installed his
first perl on his windoze machine, things may differ.
One could say, to my example of using a car, that he who drives a car does
well to have a working knowledge of the rules that come with driving a car.
And I would not disagree with you. But those rules themselves, and this is
my point, are not cast in stone, but highly subject to what people deem
appropriate at some time. I am sure the British "pioneers" who first
suggested people should drive on the left side of the road met with fierce
opposition, and were angrily referred to new.carusers.questions or the like.
:) But they nonetheless became a majority and changed the Netiquette
accordingly.
Which brings me back to the start of my case, in which I said that
Netiquette is really no more than a reflection of how things currently are.
So, my point being: in a world where more and more people will use
computers, Netiquette, to the detriment of earlier standards perhaps, can
and will change. I am not saying this change is desirable even, as, I too,
for example, find good cause to discourage top-posts, for reasons outlined.
But I can nonetheless see that this may well be an area where change is to
occur at some point. And I have decided that I will not bash any newbies
over it. :)
Speaking of cars, YMMV,
- Mark
------------------------------
Date: Mon, 26 Nov 2001 16:59:58 +0000 (UTC)
From: Robert Sherman <rsherman@ce.gatech.edu>
Subject: Re: Top-posts
Message-Id: <9ttsee$c00$1@news-int.gatech.edu>
In article <KguM7.46316$YD.3975386@news2.aus1.giganews.com>, Mark wrote:
> Netiquette has no leading industry institution behind its formation that
> lends it any formal authority. Netiquette is not an RFC, for instance, and
> should not be treated with the same authority. Since Netiquette is really no
> more than a collected reflection of how things are currently, and
>
it is an informational RFC...
from RFC1855 (http://www.rfc-editor.org/rfc/rfc1855.txt):
If you are sending a reply to a message or a posting be sure you
summarize the original at the top of the message, or include just
enough text of the original to give a context. This will make
sure readers understand when they start to read your response.
Since NetNews, especially, is proliferated by distributing the
postings from one host to another, it is possible to see a
response to a message before seeing the original. Giving context
helps everyone. But do not include the entire original!
just being difficult :)
--
robert sherman
css, cee
georgia institute of technology
atlanta, ga, usa
------------------------------
Date: Mon, 26 Nov 2001 18:12:44 +0100
From: "Steffen Müller" <5l259r001@sneakemail.com>
Subject: Re: Top-posts
Message-Id: <9ttt43$rvt$05$1@news.t-online.com>
"Robert Sherman" <rsherman@ce.gatech.edu> schrieb im Newsbeitrag
news:9ttsee$c00$1@news-int.gatech.edu...
| In article <KguM7.46316$YD.3975386@news2.aus1.giganews.com>, Mark wrote:
| > Netiquette has no leading industry institution behind its formation that
| > lends it any formal authority. Netiquette is not an RFC, for instance,
and
| > should not be treated with the same authority. Since Netiquette is
really no
| > more than a collected reflection of how things are currently, and
| >
| it is an informational RFC...
|
| from RFC1855 (http://www.rfc-editor.org/rfc/rfc1855.txt):
|
| If you are sending a reply to a message or a posting be sure you
| summarize the original at the top of the message, or include just
| enough text of the original to give a context. This will make
| sure readers understand when they start to read your response.
| Since NetNews, especially, is proliferated by distributing the
| postings from one host to another, it is possible to see a
| response to a message before seeing the original. Giving context
| helps everyone. But do not include the entire original!
+ Do not get fooled by Godzilla. It is a troll.
Steffen
--
$_=q;0cb212c210b0bb010c0113bb0c410c0b516c0bb3d212c2b0b0b016b6cb2b2c21010c0
b41110b3bba0e0c0d2c4b2b6bc013d2c0d0b01012b0b0;;s/\n//g;s/(\d)/$1<2?$1:'0'x
$1/ge;s/([a-f])/'1'x(ord($1)-97)/ge;$o=$_;push@o,substr($o,$_*8,8) for(0..
24);for(@o){print"\0"x(26-$i).chr(oct('0b'.($_)))."\r";$i++};print"\n"#stm
------------------------------
Date: Mon, 26 Nov 2001 17:25:21 GMT
From: "Mark" <admin@asarian-host.net>
Subject: Re: Top-posts
Message-Id: <5WuM7.64599$uB.10730301@bin3.nnrp.aus1.giganews.com>
"Robert Sherman" <rsherman@ce.gatech.edu> wrote in message
news:9ttsee$c00$1@news-int.gatech.edu...
> In article <KguM7.46316$YD.3975386@news2.aus1.giganews.com>, Mark wrote:
> > Netiquette has no leading industry institution behind its formation
> > that lends it any formal authority. Netiquette is not an RFC, for
> > instance, and should not be treated with the same authority. Since
> > Netiquette is really no more than a collected reflection of how
> > things are currently, and
> >
> it is an informational RFC...
>
> from RFC1855 (http://www.rfc-editor.org/rfc/rfc1855.txt):
>
> If you are sending a reply to a message or a posting be sure you
> summarize the original at the top of the message, or include just
> enough text of the original to give a context. This will make
> sure readers understand when they start to read your response.
> Since NetNews, especially, is proliferated by distributing the
> postings from one host to another, it is possible to see a
> response to a message before seeing the original. Giving context
> helps everyone. But do not include the entire original!
>
> just being difficult :)
And justly so. :) Yeah, the RFC is merely advisory; but it is sound advice.
- Mark
------------------------------
Date: Mon, 26 Nov 2001 16:14:18 GMT
From: Dan Sugalski <dan@tuatha.sidhe.org>
Subject: Re: Why doesn't Perl define an evaluation order?
Message-Id: <uTtM7.69691$Y6.7665742@news1.rdc1.ct.home.com>
Joe Schaefer <joe+usenet@sunstarsys.com> wrote:
> From a language designer's point of view, what is the advantage
> of leaving the order of evaluation undefined in Perl?
Well, generally it means you just don't have to. One fewer thing
to worry about, and one fewer constraint on the implementation.
This may well get taken care of for perl 6, though.
> (I'm told APL is another such language). It appears to me, from
> reading the clp* google archives, that although perl tries to obey
> a left-to-right rule in most cases, the canonical answer is that
> evaluation order is still an undefined aspect of the language;
> so much so that AFAIK even C's notion of _sequence point_ has
> *no* recognizable analog in Perl.
Nope, sequence points don't mean much. Statement boundaries
are it.
> I'm wondering what the real advantage of this situation is for Perl.
None, really, besides having one fewer thing to worry about with
the implementation.
> In C/C++, it is often said that leaving the evaluation order undefined
> (between sequence points) allows compiler manufacturers greater freedom
> in optimization; however some recent benchmarks show that Java keeps
> up quite well (I'd post a url if it really mattered here, but I'd like
> to avoid straying too far offtopic.)
It doesn't make much difference because generally most expressions don't
have that many different ways they can be evaluated. You'll find the
difference does tend to come into play with aggressive optimizations
on systems with lots of registers. Unfortunately most systems don't
have one or the other of those, lacking either aggressive optimizations
(because of gcc) or lots of registers (x86). (The GCC folks are working
on their end, of course, but there's not much you can do to make up
for limited hardware)
Dan
------------------------------
Date: 26 Nov 2001 09:00:12 -0800
From: andrew.meng@capitalone.com (Andrew Meng)
Subject: Why use backslash before the array and hash varible?
Message-Id: <13b1c65f.0111260900.4713ef63@posting.google.com>
Hello,
I often see somebody uses \ before the array and hash varible(for
example: \@ARGV, \%tags). Can you tell me what benefit we can get for
using backslash? Thanks a lot!
Andrew
------------------------------
Date: Mon, 26 Nov 2001 18:10:19 +0100
From: "Steffen Müller" <5l259r001@sneakemail.com>
Subject: Re: Why use backslash before the array and hash varible?
Message-Id: <9ttsvj$gvc$07$1@news.t-online.com>
"Andrew Meng" <andrew.meng@capitalone.com> schrieb im Newsbeitrag
news:13b1c65f.0111260900.4713ef63@posting.google.com...
| Hello,
|
| I often see somebody uses \ before the array and hash varible(for
| example: \@ARGV, \%tags). Can you tell me what benefit we can get for
| using backslash? Thanks a lot!
This will make a reference to the array or hash. It works with scalars, too.
my @array = ('a'..'z');
my $ref = \@array;
print $ref->[0]; # prints a
my @new_ary = @$ref; # @new_ary is now the same as @array
my @new_ary = @{$ref}; # Complete syntax. The above is a shortcut
Please read perldata dn perlref for more info.
Steffen
--
$_=q;0cb212c210b0bb010c0113bb0c410c0b516c0bb3d212c2b0b0b016b6cb2b2c21010c0
b41110b3bba0e0c0d2c4b2b6bc013d2c0d0b01012b0b0;;s/\n//g;s/(\d)/$1<2?$1:'0'x
$1/ge;s/([a-f])/'1'x(ord($1)-97)/ge;$o=$_;push@o,substr($o,$_*8,8) for(0..
24);for(@o){print"\0"x(26-$i).chr(oct('0b'.($_)))."\r";$i++};print"\n"#stm
------------------------------
Date: 26 Nov 2001 08:39:04 -0800
From: bobby@nationalgoat.com (Bobby Ray)
Subject: Re: win32::ole - change excel worksheet name
Message-Id: <699478d4.0111260839.202a5bd@posting.google.com>
>> $Book->Worksheets($count - $current)->Name = $Sheets[$current];
>> Can't modify non-lvalue subroutine call at excel.pl line 33.
"jimbo" <jimbo@soundimages.co.uk> wrote
> This may work:
>
> $Book->Worksheets($count - $current)->{Name} = $Sheets[$current];
>
> It may be that the without the braces the offending line is being
> interpreted as a call to a subroutine rather than a reference to the
> name property of the worksheet.
Your suggestion works, jimbo. The braces put the statement into proper
shape. In addition to the win32::ole documentation, and Visual
Basic Object Browser, do you know of a good reference, with
examples, that shows Perl and win32::ole working with Excel?
Thanks,
Bobby
------------------------------
Date: Mon, 26 Nov 2001 17:22:24 -0000
From: "jimbo" <jimbo@soundimages.co.uk>
Subject: Re: win32::ole - change excel worksheet name
Message-Id: <tTuM7.29014$SJ3.292337@NewsReader>
"Bobby Ray" <bobby@nationalgoat.com> wrote
> shape. In addition to the win32::ole documentation, and Visual
> Basic Object Browser, do you know of a good reference, with
> examples, that shows Perl and win32::ole working with Excel?
The best and most complete examples I have seen are in Dave Roth's
'Win32 perl Programming: The Standard Extentions'. More book info at
http://www.roth.net/. Your further resource will be the Office
Developers documentation which will show the various bits and bobs Excel
exposes so you can automate it. Although the examples will be VBA, that
shouldn't make much difference, really.
jimbo
;-)
------------------------------
Date: Mon, 26 Nov 2001 09:39:21 -0500
From: Jeff 'japhy' Pinyan <jeffp@crusoe.net>
Subject: Re: { in s///; ?
Message-Id: <Pine.GSO.4.21.0111260936450.23999-100000@crusoe.crusoe.net>
On Nov 26, Martien Verbruggen said:
>On 26 Nov 2001 03:35:59 -0600,
> Dale Henderson <nilram@boisdarc.tamu-commerce.edu> wrote:
>>
>> Now I'm wondering why the next line:
>>
>> s/@/@@/g;
>>
>> works perfectly. I've experimented and found that @@ is a valid
>> name for a perl list.
>
>Array.
What might be "odd" though is that s/@/@@/g turns all '@'s into '@@'s.
How? Because Perl doesn't interpolate punctuation arrays (except for
@_) in double-quoted strings.
@a = (1,2,3);
@_ = (4,5);
@& = (6);
print "@a;@_;@&\n"; # 1 2 3;4 5;@&
--
Jeff "japhy" Pinyan japhy@pobox.com http://www.pobox.com/~japhy/
RPI Acacia brother #734 http://www.perlmonks.org/ http://www.cpan.org/
** Look for "Regular Expressions in Perl" published by Manning, in 2002 **
------------------------------
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 2210
***************************************
