[30917] in Perl-Users-Digest
Perl-Users Digest, Issue: 2162 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Jan 27 00:14:27 2009
Date: Mon, 26 Jan 2009 21:14:18 -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 Mon, 26 Jan 2009 Volume: 11 Number: 2162
Today's topics:
Re: inputting the ephemerides sln@netherlands.com
Re: inputting the ephemerides sln@netherlands.com
Re: inputting the ephemerides sln@netherlands.com
Re: inputting the ephemerides <jurgenex@hotmail.com>
Re: inputting the ephemerides <jurgenex@hotmail.com>
Re: inputting the ephemerides sln@netherlands.com
Re: inputting the ephemerides <uri@stemsystems.com>
Re: inputting the ephemerides <larry@example.invalid>
Re: inputting the ephemerides <jimsgibson@gmail.com>
Re: inputting the ephemerides sln@netherlands.com
Re: inputting the ephemerides <jurgenex@hotmail.com>
Re: inputting the ephemerides <jurgenex@hotmail.com>
Re: inputting the ephemerides <larry@example.invalid>
Re: inputting the ephemerides <tim@burlyhost.com>
Re: inputting the ephemerides sln@netherlands.com
Re: inputting the ephemerides <larry@example.invalid>
Re: inputting the ephemerides <tim@burlyhost.com>
Re: inputting the ephemerides sln@netherlands.com
Re: inputting the ephemerides <larry@example.invalid>
Re: inputting the ephemerides <larry@example.invalid>
Re: inputting the ephemerides <tim@burlyhost.com>
Re: inputting the ephemerides <tim@burlyhost.com>
Perl Peeves (Tim McDaniel)
Re: Perl Peeves <jurgenex@hotmail.com>
Re: Perl Peeves <tadmc@seesig.invalid>
Re: There is no such thing as Circular Lists (was: FAQ <tim@burlyhost.com>
Re: Vista x64 + DBD::Pg driver <tim@burlyhost.com>
Re: Which is faster - hash or array lookup <whynot@pozharski.name>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 26 Jan 2009 23:20:43 GMT
From: sln@netherlands.com
Subject: Re: inputting the ephemerides
Message-Id: <f9hsn4l3nlb6pb1c9iq4566m9d2veg9o3m@4ax.com>
On Mon, 26 Jan 2009 16:51:51 -0600, Tad J McClellan <tadmc@seesig.invalid> wrote:
>Larry Gates <larry@example.invalid> wrote:
>
>>
>>> Larry Gates <larry@example.invalid> wrote:
>>>> while (my $line = <$fh>) {
>>>> $line =~ s/\t/ /g;
>>>> $line =~ s/ER/ /g;
>>>> $line =~ s/°/ /g;
>>>> }
>
>>> This is a giant NOOP. Why are you doing that?
>
>
>You have not answered the question.
>
>Why do you think you need those lines in your program?
>
>
>> I'm pleased to roll out
>> my first output that I can call a solution:
>
>
>> while (my $line = <$fh>) {
>> $line =~ s/\t/ /g;
>> $line =~ s/ER/ /g;
>> $line =~ s/°/ /g;
>> }
>> close($fh);
>
>
>Delete those lines and compare the output to when those lines
>are included.
>
>There will be no differences.
>
>ie. those lines do not do anything useful, so remove them.
Rofl ........
sln
------------------------------
Date: Mon, 26 Jan 2009 23:27:42 GMT
From: sln@netherlands.com
Subject: Re: inputting the ephemerides
Message-Id: <2ihsn41ar19pqek0dojmn7srr1le526a5l@4ax.com>
On Sun, 25 Jan 2009 17:20:44 -0700, Larry Gates <larry@example.invalid> wrote:
>On Sun, 25 Jan 2009 01:25:36 GMT, sln@netherlands.com wrote:
>
>
>> You are truly an attention troll.
>>
>> sln
>
>Please fuck your dutch self.
>
>[comp.lang.perl.misc]
>!delete From {sln}
Americans, your all the same.
Am Bushed once, er, remember that, er,
am Bushed twice, er, forget me not...
Americans are the 'decider', makes me puke..
sln
------------------------------
Date: Mon, 26 Jan 2009 23:29:31 GMT
From: sln@netherlands.com
Subject: Re: inputting the ephemerides
Message-Id: <dphsn49d9bpo9i7b3mpvidjdpsqav3mgun@4ax.com>
On Wed, 21 Jan 2009 12:25:11 -0700, Larry Gates <larry@example.invalid> wrote:
>On Wed, 21 Jan 2009 07:07:02 GMT, sln@netherlands.com wrote:
>
>> I'm falling down laughing. This is better than the Comedy chanel.
>
>Apparently this regex has a side effect that involves a catastrophic loss
>of seating stability.
>
Apparently your mind involves catastrophic loss of stability.
sln
------------------------------
Date: Mon, 26 Jan 2009 15:37:01 -0800
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: inputting the ephemerides
Message-Id: <dlhsn4lo2jph4q8petnvnu9kpnhga89tae@4ax.com>
Larry Gates <larry@example.invalid> wrote:
>On Mon, 26 Jan 2009 12:35:38 -0800, Jürgen Exner wrote:
>
>> Larry Gates <larry@example.invalid> wrote:
>>> while (my $line = <$fh>) {
>>> $line =~ s/\t/ /g;
>>> $line =~ s/ER/ /g;
>>> $line =~ s/°/ /g;
>>> }
>>
>> What is the section above supposed to do?
>> It reads a line from a file into memory, alters the line, and then
>> happily throws it away by reading the next line without doing anything
>> with that altered line. This is a giant NOOP. Why are you doing that?
>>
>
>I've been doing this in bite-sixed chunks. The problems that dogged me for
>a long time were what to do with tabs, the ER that followed the moon's
>distance from earth and no other body's, and the degree sign, which is B0
>hex and therefore not ascii.
>
>I don't know what noop is, but I suspect it's a loop that does a whole lot
Short for "No Operation", a commonly used placeholder in assembler
languages..
>of nothing.
Right.
>I *do* use the $line, because that's what I split on:
No, you don't. The one line that you conveniently snipped is
> while (my $line = <$gh>) {
where you declare and define a new $line, which has nothing to do with
the $line from the code segment above, and you re-read the whole,
unaltered file again line by line and
> my @s = split / /, $line;
uses those newly read $line.
>my @s = split /\s+/, $line;
Do you want to split on space or on white space? You rmight want to make
up your mind.
> use strict;
> use warnings;
> my $filename = 'eph6.txt';
> my $filename2 = 'outfile1.txt';
> open(my $fh, '<', $filename) or die "cannot open $filename: $!";
> open(my $gh, $filename2) or die "cannot open $filename2: $!";
>
> while (my $line = <$fh>) {
> $line =~ s/\t/ /g;
> $line =~ s/ER/ /g;
> $line =~ s/°/ /g;
> }
You are still reading the while file, modifying all read strings, and
happily throwing them away.
> close($fh);
>
> seek($gh,0,0);
At this point $gh has been opened, but never been read from or written
to. Therefore this seek is a NOOP, too.
jue
------------------------------
Date: Mon, 26 Jan 2009 15:42:13 -0800
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: inputting the ephemerides
Message-Id: <vcisn45lks24votni3ebp6ti958qfilhjf@4ax.com>
Larry Gates <larry@example.invalid> wrote:
> seek($gh,0,0);
Here you are seek()ing $gh (for no good reason, I might add).
> while (my $line = <$gh>) {
Here you are reading from $gh.
> print $hh "$line\n";
Here you are printing to $hh.
> I thought I was
>reading and writing from $gh but apparently not.
There is no place in all of your code where you are writing to $gh.
>I wonder how I ever got
>output at all.??
Because print() by default prints to STDOUT if no other filehandle is
specified.
jue
------------------------------
Date: Tue, 27 Jan 2009 00:21:33 GMT
From: sln@netherlands.com
Subject: Re: inputting the ephemerides
Message-Id: <ajksn4hflbu564oggh5c4lihnmr88i9np5@4ax.com>
On Mon, 26 Jan 2009 15:37:01 -0800, Jürgen Exner <jurgenex@hotmail.com> wrote:
>Larry Gates <larry@example.invalid> wrote:
>>On Mon, 26 Jan 2009 12:35:38 -0800, Jürgen Exner wrote:
>>
>>> Larry Gates <larry@example.invalid> wrote:
>>>> while (my $line = <$fh>) {
>>>> $line =~ s/\t/ /g;
>>>> $line =~ s/ER/ /g;
>>>> $line =~ s/°/ /g;
>>>> }
>>>
>>> What is the section above supposed to do?
>>> It reads a line from a file into memory, alters the line, and then
>>> happily throws it away by reading the next line without doing anything
>>> with that altered line. This is a giant NOOP. Why are you doing that?
>>>
>>
>>I've been doing this in bite-sixed chunks. The problems that dogged me for
>>a long time were what to do with tabs, the ER that followed the moon's
>>distance from earth and no other body's, and the degree sign, which is B0
>>hex and therefore not ascii.
>>
>>I don't know what noop is, but I suspect it's a loop that does a whole lot
>
>Short for "No Operation", a commonly used placeholder in assembler
>languages..
>
Noopy, aka 00, the black hole, an instruction your cpu does every cycle
when not active, otherwise known as idle. I don't think that relates to Perl
does it ? Such bullshit !!
sln
------------------------------
Date: Mon, 26 Jan 2009 19:59:27 -0500
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: inputting the ephemerides
Message-Id: <x7myddmumo.fsf@mail.sysarch.com>
>>>>> "LG" == Larry Gates <larry@example.invalid> writes:
LG> my $filename = 'eph6.txt';
LG> my $filename2 = 'outfile1.txt';
LG> open(my $fh, '<', $filename) or die "cannot open $filename: $!";
LG> open(my $gh, $filename2) or die "cannot open $filename2: $!";
LG> while (my $line = <$fh>) {
LG> $line =~ s/\t/ /g;
LG> $line =~ s/ER/ /g;
LG> $line =~ s/°/ /g;
LG> }
LG> close($fh);
i said this before. WHY ARE YOU WRITING out the changed data and then
reading it back in again? just use the lines you cleaned up as you get
them.
LG> seek($gh,0,0);
no need for the seek, the extra file opens, the extra readlines, etc. a
total waste of resources.
LG> while (my $line = <$gh>) {
and you keep not getting how perl is different from c and fortran. i
learned perl from the first camel (the pink one) having used c for many
years. it wasn't so hard to learn if you have been programming as long
as you seem to claim.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Free Perl Training --- http://perlhunter.com/college.html ---------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Mon, 26 Jan 2009 18:22:38 -0700
From: Larry Gates <larry@example.invalid>
Subject: Re: inputting the ephemerides
Message-Id: <1quz1k8yst968$.ukur9r3ro8lh.dlg@40tude.net>
On Mon, 26 Jan 2009 15:42:13 -0800, Jürgen Exner wrote:
> Larry Gates <larry@example.invalid> wrote:
>
>> seek($gh,0,0);
>
> Here you are seek()ing $gh (for no good reason, I might add).
>
>> while (my $line = <$gh>) {
>
> Here you are reading from $gh.
>
>> print $hh "$line\n";
>
> Here you are printing to $hh.
>
>> I thought I was
>>reading and writing from $gh but apparently not.
>
> There is no place in all of your code where you are writing to $gh.
>
>>I wonder how I ever got
>>output at all.??
>
> Because print() by default prints to STDOUT if no other filehandle is
> specified.
>
> jue
I went back and tried to use STDOUT as my temp file but couldn't get it
together. This purports again to be a solution:
use strict;
use warnings;
my $filename = 'eph6.txt';
open(my $fh, '<', $filename) or die "cannot open $filename: $!";
my $filename2 = 'temp6.txt';
open(my $gh, '+>', $filename2) or die "cannot open $filename2: $!";
while (my $line = <$fh>) {
$line =~ s/\t/ /g;
$line =~ s/ER/ /g;
$line =~ s/°/ /g;
print STDOUT $line;
print $gh $line;
}
close($fh);
close($gh);
open(my $hh, '<', $filename2) or die "cannot open $filename2: $!";
my $outfile = 'outfile7.txt';
open(my $ih, '>', $outfile) or die "cannot open $outfile: $!";
while (my $line = <$hh>) {
my @s = split /\s+/, $line;
$s[1] =~ s/h//;
$s[2] =~ s/m//;
$s[3] =~ s/s//;
$s[5] =~ s/'//;
for my $i (0..9) {
print STDOUT "s$i is $s[$i]\n";
}
print "@s\n";
print $ih "@s\n";
}
close($hh);
close($ih);
# perl reg12.pl
C:\MinGW\source>type outfile7.txt
Sun 19 43 51 -21 17.8 0.984 -35.020 87.148 Set
Mercury 20 36 41 -16 59.3 0.747 -22.075 84.236 Set
Venus 22 51 18 -7 46.9 0.691 10.142 72.919 Up
Moon 10 24 21 +7 29.5 58.6 -4.992 -102.785 Set
Mars 18 58 51 -23 33.8 2.398 -45.280 90.860 Set
Jupiter 20 17 22 -20 8.1 6.082 -27.618 83.843 Set
Saturn 11 32 29 +5 16.0 8.806 -19.672 -111.729 Set
Uranus 23 23 12 -4 46.5 20.638 18.211 70.235 Up
Neptune 21 41 17 -14 13.9 30.892 -7.527 77.864 Set
Pluto 18 6 40 -17 44.9 32.485 -52.833 108.052 Set
C:\MinGW\source>
--
larry gates
Maybe we should take a clue from FTP and put in an option like "print
hash marks on every 1024 iterations". :-)
-- Larry Wall in <199807171819.LAA13771@wall.org>
------------------------------
Date: Mon, 26 Jan 2009 17:37:55 -0800
From: Jim Gibson <jimsgibson@gmail.com>
Subject: Re: inputting the ephemerides
Message-Id: <260120091737557758%jimsgibson@gmail.com>
In article <47zzbigltdib.vqcn6up708fj.dlg@40tude.net>, Larry Gates
<larry@example.invalid> wrote:
OK. Here is a quick version of your program with most of the logic
errors removed. Since I did test it, there still may be bugs, but it
should give you the overall logic flow:
use strict;
use warnings;
# open input file
my $filename = 'eph6.txt';
open(my $fh, '<', $filename) or
die "cannot open $filename for reading: $!";
# open output file
my $filename2 = 'outfile1.txt';
open(my $gh, '>', $filename2) or
die "cannot open $filename2 for writing: $!";
# process all lines in input file
while( my $line = <$fh> ) {
chomp($line);
my @s = split /\s+/, $line;
# modify fields
$s[1] =~ s/h//;
$s[2] =~ s/m//;
$s[3] =~ s/s//;
$s[5] =~ s/'//;
# print modified fields
for my $i (0..$#s) {
print "s[$i] = $s[$i]\n";
}
# write modified fields to output file
my $outline = join(' ', @s);
print $gh "$outline\n";
}
# close input and output files
close($gh) or die("Error closing $filename2: $!");
close($fh) or die("Error closing $filename: $!");
__END__
Note that aside from your explicit field modifications, this program
will compress two or more spaces in your input file to one space. If
this is a problem, then you should consider using unpack on the input
data and pack for the output data.
Hope this helps.
--
Jim Gibson
------------------------------
Date: Tue, 27 Jan 2009 01:38:05 GMT
From: sln@netherlands.com
Subject: Re: inputting the ephemerides
Message-Id: <6apsn41fg4184cn54ne0n5f226uhj1ovbs@4ax.com>
On Mon, 26 Jan 2009 18:22:38 -0700, Larry Gates <larry@example.invalid> wrote:
>On Mon, 26 Jan 2009 15:42:13 -0800, Jürgen Exner wrote:
>
>> Larry Gates <larry@example.invalid> wrote:
>>
>>> seek($gh,0,0);
>>
>> Here you are seek()ing $gh (for no good reason, I might add).
>>
>>> while (my $line = <$gh>) {
>>
>> Here you are reading from $gh.
>>
>>> print $hh "$line\n";
>>
>> Here you are printing to $hh.
>>
>>> I thought I was
>>>reading and writing from $gh but apparently not.
>>
>> There is no place in all of your code where you are writing to $gh.
>>
>>>I wonder how I ever got
>>>output at all.??
>>
>> Because print() by default prints to STDOUT if no other filehandle is
>> specified.
>>
>> jue
>
>I went back and tried to use STDOUT as my temp file but couldn't get it
>together. This purports again to be a solution:
>
> use strict;
> use warnings;
>
> my $filename = 'eph6.txt';
> open(my $fh, '<', $filename) or die "cannot open $filename: $!";
> my $filename2 = 'temp6.txt';
> open(my $gh, '+>', $filename2) or die "cannot open $filename2: $!";
>
> while (my $line = <$fh>) {
> $line =~ s/\t/ /g;
> $line =~ s/ER/ /g;
> $line =~ s/°/ /g;
> print STDOUT $line;
> print $gh $line;
> }
> close($fh);
> close($gh);
>
> open(my $hh, '<', $filename2) or die "cannot open $filename2: $!";
> my $outfile = 'outfile7.txt';
> open(my $ih, '>', $outfile) or die "cannot open $outfile: $!";
> while (my $line = <$hh>) {
> my @s = split /\s+/, $line;
>
> $s[1] =~ s/h//;
> $s[2] =~ s/m//;
> $s[3] =~ s/s//;
> $s[5] =~ s/'//;
> for my $i (0..9) {
> print STDOUT "s$i is $s[$i]\n";
> }
> print "@s\n";
> print $ih "@s\n";
> }
> close($hh);
> close($ih);
>
># perl reg12.pl
>
>C:\MinGW\source>type outfile7.txt
>Sun 19 43 51 -21 17.8 0.984 -35.020 87.148 Set
>Mercury 20 36 41 -16 59.3 0.747 -22.075 84.236 Set
>Venus 22 51 18 -7 46.9 0.691 10.142 72.919 Up
>Moon 10 24 21 +7 29.5 58.6 -4.992 -102.785 Set
>Mars 18 58 51 -23 33.8 2.398 -45.280 90.860 Set
>Jupiter 20 17 22 -20 8.1 6.082 -27.618 83.843 Set
>Saturn 11 32 29 +5 16.0 8.806 -19.672 -111.729 Set
>Uranus 23 23 12 -4 46.5 20.638 18.211 70.235 Up
>Neptune 21 41 17 -14 13.9 30.892 -7.527 77.864 Set
>Pluto 18 6 40 -17 44.9 32.485 -52.833 108.052 Set
>
>C:\MinGW\source>
Jeez, give it a rest attention hound.
sln
------------------------------
Date: Mon, 26 Jan 2009 18:00:31 -0800
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: inputting the ephemerides
Message-Id: <mgqsn4pggno814uc62hplh9kkvod34ucbf@4ax.com>
Uri Guttman <uri@stemsystems.com> wrote:
>>>>>> "LG" == Larry Gates <larry@example.invalid> writes:
>
> LG> my $filename = 'eph6.txt';
> LG> my $filename2 = 'outfile1.txt';
> LG> open(my $fh, '<', $filename) or die "cannot open $filename: $!";
> LG> open(my $gh, $filename2) or die "cannot open $filename2: $!";
>
> LG> while (my $line = <$fh>) {
> LG> $line =~ s/\t/ /g;
> LG> $line =~ s/ER/ /g;
> LG> $line =~ s/°/ /g;
> LG> }
> LG> close($fh);
>
>i said this before. WHY ARE YOU WRITING out the changed data and then
>reading it back in again?
If at least he would write them out. But he is reading them, modifying
the read text, and then discarding the modified text by overwriting it
with the next line from the file.
jue
------------------------------
Date: Mon, 26 Jan 2009 18:07:58 -0800
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: inputting the ephemerides
Message-Id: <9nqsn4hlokgmj6opjnjibg9ifbfodv3tm3@4ax.com>
Larry Gates <larry@example.invalid> wrote:
>>I wonder how I ever got
>>>output at all.??
>>
>> Because print() by default prints to STDOUT if no other filehandle is
>> specified.
>
>I went back and tried to use STDOUT as my temp file but couldn't get it
>together. This purports again to be a solution:
AAAAARRRRRRRGGGGGGGG!!!!! HHHHHHEEEEEELLLLPPPPP!!!
Who on earth said anything about using STDOUT as a temp file? You asked
why you got output and I answered that specific question by telling you
that print() defaults to STDOUT if no other filehandle is specified (and
implied that STDOUT is opened automatically at the start of any
program).
What the devil moved you to turn STDOUT into a temp file? Nobody ever
suggested something so stupid! Do you know what STDOUT is? You are
claiming to be familiar with C. I cannot believe that, considering that
stdout is a concept coming from C.
jue
------------------------------
Date: Mon, 26 Jan 2009 20:06:29 -0700
From: Larry Gates <larry@example.invalid>
Subject: Re: inputting the ephemerides
Message-Id: <1pk8lm285qkpr.1vhohpal8mgwr.dlg@40tude.net>
On Mon, 26 Jan 2009 16:51:51 -0600, Tad J McClellan wrote:
> Larry Gates <larry@example.invalid> wrote:
>
>>
>>> Larry Gates <larry@example.invalid> wrote:
>>>> while (my $line = <$fh>) {
>>>> $line =~ s/\t/ /g;
>>>> $line =~ s/ER/ /g;
>>>> $line =~ s/°/ /g;
>>>> }
>
>>> This is a giant NOOP. Why are you doing that?
>
>
> You have not answered the question.
>
> Why do you think you need those lines in your program?
>
>
>> I'm pleased to roll out
>> my first output that I can call a solution:
>
>
>> while (my $line = <$fh>) {
>> $line =~ s/\t/ /g;
>> $line =~ s/ER/ /g;
>> $line =~ s/°/ /g;
>> }
>> close($fh);
>
>
> Delete those lines and compare the output to when those lines
> are included.
>
> There will be no differences.
>
> ie. those lines do not do anything useful, so remove them.
Well, I'll be dipped in shit. You're right. I can understand the
non-necessity of replacing tabs with spaces for the split, but what
happened to the ER and the ° ?
input:
Sun 20h 38m 32s -18° 27.9' 0.985 -11.352 75.301 Set
Mercury 19h 39m 38s -17° 59.0' 0.693 -22.929 83.538 Set
Venus 23h 35m 40s -1° 34.9' 0.595 32.958 60.291 Up
Moon 21h 10m 19s -15° 43.1' 62.6 ER -3.535 73.245 Set
Mars 19h 41m 30s -22° 18.7' 2.365 -24.747 79.217 Set
Jupiter 20h 30m 0s -19° 26.4' 6.089 -13.572 75.592 Set
Saturn 11h 30m 54s +5° 29.7' 8.641 -29.340 -121.942 Set
Uranus 23h 25m 10s -4° 33.4' 20.808 29.003 59.973 Up
Neptune 21h 43m 4s -14° 4.9' 30.978 3.795 69.844 Up
Pluto 18h 8m 27s -17° 44.7' 32.385 -41.418 97.063 Set
output:
Sun 20 38 32 -18 27.9 0.985 -11.352 75.301 Set
Mercury 19 39 38 -17 59.0 0.693 -22.929 83.538 Set
Venus 23 35 40 -1 34.9 0.595 32.958 60.291 Up
Moon 21 10 19 -15 43.1 62.6 -3.535 73.245 Set
Mars 19 41 30 -22 18.7 2.365 -24.747 79.217 Set
Jupiter 20 30 0 -19 26.4 6.089 -13.572 75.592 Set
Saturn 11 30 54 +5 29.7 8.641 -29.340 -121.942 Set
Uranus 23 25 10 -4 33.4 20.808 29.003 59.973 Up
Neptune 21 43 4 -14 4.9 30.978 3.795 69.844 Up
Pluto 18 8 27 -17 44.7 32.385 -41.418 97.063 Set
--
larry gates
We question most of the mantras around here periodically, in case
you hadn't noticed. :-)
-- Larry Wall in <199705101952.MAA00756@wall.org>
------------------------------
Date: Mon, 26 Jan 2009 19:23:00 -0800
From: Tim Greer <tim@burlyhost.com>
Subject: Re: inputting the ephemerides
Message-Id: <o6vfl.46839$8a4.25393@newsfe08.iad>
sln@netherlands.com wrote:
> Americans, your all the same.
> Am Bushed once, er, remember that, er,
> am Bushed twice, er, forget me not...
>
> Americans are the 'decider', makes me puke..
>
> sln
Do you suppose you are making a valid (or sane) point, by accusing 300+
million people of "all being the same"?
--
Tim Greer, CEO/Founder/CTO, BurlyHost.com, Inc.
Shared Hosting, Reseller Hosting, Dedicated & Semi-Dedicated servers
and Custom Hosting. 24/7 support, 30 day guarantee, secure servers.
Industry's most experienced staff! -- Web Hosting With Muscle!
------------------------------
Date: Tue, 27 Jan 2009 03:28:21 GMT
From: sln@netherlands.com
Subject: Re: inputting the ephemerides
Message-Id: <fqvsn455v5up41mk853reo3ktqi7an5mp8@4ax.com>
On Mon, 26 Jan 2009 19:23:00 -0800, Tim Greer <tim@burlyhost.com> wrote:
>sln@netherlands.com wrote:
>
>> Americans, your all the same.
>> Am Bushed once, er, remember that, er,
>> am Bushed twice, er, forget me not...
>>
>> Americans are the 'decider', makes me puke..
>>
>> sln
>
>Do you suppose you are making a valid (or sane) point, by accusing 300+
>million people of "all being the same"?
YES !!!
sln
------------------------------
Date: Mon, 26 Jan 2009 20:34:47 -0700
From: Larry Gates <larry@example.invalid>
Subject: Re: inputting the ephemerides
Message-Id: <3m0vnh57dvfo$.1mc3rdk9ng6es.dlg@40tude.net>
On Mon, 26 Jan 2009 18:07:58 -0800, Jürgen Exner wrote:
> Larry Gates <larry@example.invalid> wrote:
>>>I wonder how I ever got
>>>>output at all.??
>>>
>>> Because print() by default prints to STDOUT if no other filehandle is
>>> specified.
>>
>>I went back and tried to use STDOUT as my temp file but couldn't get it
>>together. This purports again to be a solution:
>
> AAAAARRRRRRRGGGGGGGG!!!!! HHHHHHEEEEEELLLLPPPPP!!!
>
> Who on earth said anything about using STDOUT as a temp file? You asked
> why you got output and I answered that specific question by telling you
> that print() defaults to STDOUT if no other filehandle is specified (and
> implied that STDOUT is opened automatically at the start of any
> program).
>
> What the devil moved you to turn STDOUT into a temp file? Nobody ever
> suggested something so stupid! Do you know what STDOUT is? You are
> claiming to be familiar with C. I cannot believe that, considering that
> stdout is a concept coming from C.
>
> jue
I had no explanation why I was getting output at all, given that I wasn't
writing to the file. I thought I was reading what had gone to stdout
earlier in the program. Yes, this notion was completely errant and points
to an uncareful reading of your post. On reflection, the reason I was
getting output was that I'd run the script before, so there already existed
a file that I thought I was creating every time.
Much of perl emulates the way the Bourne shell works, where it is trivial
to pipe STDOUT. So many things work "magically" around here; I thought it
was another example.
While I tried to do that, unsuccessfully, I successfully read portions of
perldoc perlvar, perldoc perlrun, and studied several functions in the
camel book. These are not the habits of a dullard.
--
larry gates
What about WRITING it first and rationalizing it afterwords? :-)
-- Larry Wall in <8162@jpl-devvax.JPL.NASA.GOV>
------------------------------
Date: Mon, 26 Jan 2009 19:39:54 -0800
From: Tim Greer <tim@burlyhost.com>
Subject: Re: inputting the ephemerides
Message-Id: <fmvfl.161294$H12.139649@newsfe12.iad>
sln@netherlands.com wrote:
> On Mon, 26 Jan 2009 19:23:00 -0800, Tim Greer <tim@burlyhost.com>
> wrote:
...
>>
>>Do you suppose you are making a valid (or sane) point, by accusing
>>300+ million people of "all being the same"?
>
> YES !!!
>
> sln
I guess this explains your "160+ IQ" at work, huh?
--
Tim Greer, CEO/Founder/CTO, BurlyHost.com, Inc.
Shared Hosting, Reseller Hosting, Dedicated & Semi-Dedicated servers
and Custom Hosting. 24/7 support, 30 day guarantee, secure servers.
Industry's most experienced staff! -- Web Hosting With Muscle!
------------------------------
Date: Tue, 27 Jan 2009 03:43:47 GMT
From: sln@netherlands.com
Subject: Re: inputting the ephemerides
Message-Id: <ml0tn4t48hmh01rj5ac8n0cdujnf3bbm4c@4ax.com>
On Mon, 26 Jan 2009 19:39:54 -0800, Tim Greer <tim@burlyhost.com> wrote:
>sln@netherlands.com wrote:
>
>> On Mon, 26 Jan 2009 19:23:00 -0800, Tim Greer <tim@burlyhost.com>
>> wrote:
>...
>>>
>>>Do you suppose you are making a valid (or sane) point, by accusing
>>>300+ million people of "all being the same"?
>>
>> YES !!!
>>
>> sln
>
>I guess this explains your "160+ IQ" at work, huh?
It only took up .1 of a single IQ to figure that out. Americans.. jeez
sln
------------------------------
Date: Mon, 26 Jan 2009 20:47:59 -0700
From: Larry Gates <larry@example.invalid>
Subject: Re: inputting the ephemerides
Message-Id: <w84mbvuk0uvd.1xibhp02curxk.dlg@40tude.net>
On Mon, 26 Jan 2009 17:37:55 -0800, Jim Gibson wrote:
> In article <47zzbigltdib.vqcn6up708fj.dlg@40tude.net>, Larry Gates
> <larry@example.invalid> wrote:
>
>
> OK. Here is a quick version of your program with most of the logic
> errors removed. Since I did test it, there still may be bugs, but it
> should give you the overall logic flow:
>
> use strict;
> use warnings;
>
> # open input file
> my $filename = 'eph6.txt';
> open(my $fh, '<', $filename) or
> die "cannot open $filename for reading: $!";
>
> # open output file
> my $filename2 = 'outfile1.txt';
> open(my $gh, '>', $filename2) or
> die "cannot open $filename2 for writing: $!";
>
> # process all lines in input file
> while( my $line = <$fh> ) {
> chomp($line);
> my @s = split /\s+/, $line;
>
> # modify fields
> $s[1] =~ s/h//;
> $s[2] =~ s/m//;
> $s[3] =~ s/s//;
> $s[5] =~ s/'//;
>
> # print modified fields
> for my $i (0..$#s) {
> print "s[$i] = $s[$i]\n";
> }
>
> # write modified fields to output file
> my $outline = join(' ', @s);
> print $gh "$outline\n";
> }
>
> # close input and output files
> close($gh) or die("Error closing $filename2: $!");
> close($fh) or die("Error closing $filename: $!");
>
> __END__
>
> Note that aside from your explicit field modifications, this program
> will compress two or more spaces in your input file to one space. If
> this is a problem, then you should consider using unpack on the input
> data and pack for the output data.
>
> Hope this helps.
It does. I appreciate your comment. What this illustrates is what I
thought I was going to run into with my NOOP lines:
C:\MinGW\source>perl reg14.pl
s[0] = Sun
s[1] = 20
s[2] = 38
s[3] = 32
...
s[0] = Moon
s[1] = 21
s[2] = 10
s[3] = 19
s[4] = -15
s[5] = 43.1
s[6] = 62.6
s[7] = ER
s[8] = -3.535
s[9] = 73.245
s[10] = Set
...
s[0] = Pluto
s[1] = 18
s[2] = 8
s[3] = 27
s[4] = -17
s[5] = 44.7
s[6] = 32.385
s[7] = -41.418
s[8] = 97.063
s[9] = Set
C:\MinGW\source>type outfile10.txt
Sun 20 38 32 -18 27.9 0.985 -11.352 75.301 Set
Mercury 19 39 38 -17 59.0 0.693 -22.929 83.538 Set
Venus 23 35 40 -1 34.9 0.595 32.958 60.291 Up
Moon 21 10 19 -15 43.1 62.6 ER -3.535 73.245 Set
Mars 19 41 30 -22 18.7 2.365 -24.747 79.217 Set
Jupiter 20 30 0 -19 26.4 6.089 -13.572 75.592 Set
Saturn 11 30 54 +5 29.7 8.641 -29.340 -121.942 Set
Uranus 23 25 10 -4 33.4 20.808 29.003 59.973 Up
Neptune 21 43 4 -14 4.9 30.978 3.795 69.844 Up
Pluto 18 8 27 -17 44.7 32.385 -41.418 97.063 Set
C:\MinGW\source>
Here we see the black-shaded character that dos renders upper-ascii as, as
well as an eleventh field for the ER in the moon, which is definitely
trouble.
I would think that adding
$line =~ s/ER//g;
$line =~ s/œ//g;
would be the fix, but clearly there's another way that obviates this.
I just don't why.
--
larry gates
I'd put my money where my mouth is, but my mouth keeps moving.
-- Larry Wall in <199704051723.JAA28035@wall.org>
------------------------------
Date: Mon, 26 Jan 2009 20:54:05 -0700
From: Larry Gates <larry@example.invalid>
Subject: Re: inputting the ephemerides
Message-Id: <15iqjqshy0k3c.t3ofsjdhpc5s$.dlg@40tude.net>
On Mon, 26 Jan 2009 19:39:54 -0800, Tim Greer wrote:
> sln@netherlands.com wrote:
>
>> On Mon, 26 Jan 2009 19:23:00 -0800, Tim Greer <tim@burlyhost.com>
>> wrote:
> ...
>>>
>>>Do you suppose you are making a valid (or sane) point, by accusing
>>>300+ million people of "all being the same"?
>>
>> YES !!!
>>
>> sln
>
> I guess this explains your "160+ IQ" at work, huh?
Tim,
I'd appreciate if you didn't respond to someone I, as OP, killfiled on this
thread. Thx.
--
larry gates
: I've heard that there is a shell (bourne or csh) to perl filter, does
: anyone know of this or where I can get it?
Yeah, you filter it through Tom Christiansen. :-) -- Larry Wall
------------------------------
Date: Mon, 26 Jan 2009 20:17:21 -0800
From: Tim Greer <tim@burlyhost.com>
Subject: Re: inputting the ephemerides
Message-Id: <lVvfl.37212$1L3.25205@newsfe20.iad>
sln@netherlands.com wrote:
> On Mon, 26 Jan 2009 19:39:54 -0800, Tim Greer <tim@burlyhost.com>
> wrote:
>
>>sln@netherlands.com wrote:
>>
>>> On Mon, 26 Jan 2009 19:23:00 -0800, Tim Greer <tim@burlyhost.com>
>>> wrote:
>>...
>>>>
>>>>Do you suppose you are making a valid (or sane) point, by accusing
>>>>300+ million people of "all being the same"?
>>>
>>> YES !!!
>>>
>>> sln
>>
>>I guess this explains your "160+ IQ" at work, huh?
>
> It only took up .1 of a single IQ to figure that out. Americans.. jeez
>
> sln
Yes, yes, "all" Americans are dumb compared to you, and "all" Americans
are the same. Okay then.
--
Tim Greer, CEO/Founder/CTO, BurlyHost.com, Inc.
Shared Hosting, Reseller Hosting, Dedicated & Semi-Dedicated servers
and Custom Hosting. 24/7 support, 30 day guarantee, secure servers.
Industry's most experienced staff! -- Web Hosting With Muscle!
------------------------------
Date: Mon, 26 Jan 2009 20:18:11 -0800
From: Tim Greer <tim@burlyhost.com>
Subject: Re: inputting the ephemerides
Message-Id: <7Wvfl.37213$1L3.25239@newsfe20.iad>
Larry Gates wrote:
> On Mon, 26 Jan 2009 19:39:54 -0800, Tim Greer wrote:
>
>> sln@netherlands.com wrote:
>>
>>> On Mon, 26 Jan 2009 19:23:00 -0800, Tim Greer <tim@burlyhost.com>
>>> wrote:
>> ...
>>>>
>>>>Do you suppose you are making a valid (or sane) point, by accusing
>>>>300+ million people of "all being the same"?
>>>
>>> YES !!!
>>>
>>> sln
>>
>> I guess this explains your "160+ IQ" at work, huh?
>
> Tim,
>
> I'd appreciate if you didn't respond to someone I, as OP, killfiled on
> this
> thread. Thx.
Add a filter so you don't see people replying to him (or killfile me,
too, if that's easier).
--
Tim Greer, CEO/Founder/CTO, BurlyHost.com, Inc.
Shared Hosting, Reseller Hosting, Dedicated & Semi-Dedicated servers
and Custom Hosting. 24/7 support, 30 day guarantee, secure servers.
Industry's most experienced staff! -- Web Hosting With Muscle!
------------------------------
Date: Tue, 27 Jan 2009 01:48:09 +0000 (UTC)
From: tmcd@panix.com (Tim McDaniel)
Subject: Perl Peeves
Message-Id: <gllp4p$psn$1@reader1.panix.com>
Just venting.
(1) I hate that
Unary "+" has no effect whatsoever, even on strings.
(per "man perlop"). Unary plus LOOKS like a unary arithmetic
operator, like "-". I was using it like "+@a", as a shorter form of
"scalar @a", until I finally found the above statement in the 5.010000
man page and realized that "+@a" was working only because I happened
to be using it in a scalar context already.
(I could do "- -@a", but that's just not as elegant as "+@a" would be.)
(2) That had effect but wasn't documented in "man perlop" in 5.005,
the version on my ISP's shell accounts.
(3) "man perlop" has
Binary "<" returns true if the left argument is numerically less
than the right argument.
et cetera, but it doesn't even mention "false" in that context and
doesn't define "true". I finally tracked down the definition not in
"man perlop", but in "man perlsyn":
Truth and Falsehood
The number 0, the strings '0' and '', the empty list "()", and
"undef" are all false in a boolean context. All other values are
true. Negation of a true value by "!" or "not" returns a special
false value. When evaluated as a string it is treated as '', but
as a number, it is treated as 0.
(4) It doesn't say which true value is returned. It could return
'0 ', it appears, and too bad if you happen to do arithmetic on it or
print it without output delimiters. And it doesn't say that the
relational operators ever return false, much less that it's the
special false.
(5) That "special false". I was going nuts trying to figure out what
was different between
$ perl -w -e 'my $j = (17 < 5); print "<$j>\n"'
<>
$ perl -w -e 'my $j = 0+(17 < 5); print "<$j>\n"'
<0>
$ perl -w -e 'my $j = 0+("" ); print "<$j>\n"'
Argument "" isn't numeric in addition (+) at -e line 1.
<0>
(6) The stupidity that I've mentioned before, of the -r / -w / -x
being defined as being ignorant of ACLs, when they should truly follow
their definitions in "man perlfunc":
-r File is readable by effective uid/gid.
-w File is writable by effective uid/gid.
-x File is executable by effective uid/gid.
--
Tim McDaniel, tmcd@panix.com
------------------------------
Date: Mon, 26 Jan 2009 18:24:15 -0800
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Perl Peeves
Message-Id: <7crsn4hardgt8fvgn3p0uopfv1mtgdfj7k@4ax.com>
tmcd@panix.com (Tim McDaniel) wrote:
>Just venting.
>
>(1) I hate that
>
> Unary "+" has no effect whatsoever, even on strings.
Agree, that is not very user friendly.
>(3) "man perlop" has
>
> Binary "<" returns true if the left argument is numerically less
> than the right argument.
>
>et cetera, but it doesn't even mention "false" in that context
Well, ok, wording might be better as
"... returns true if and only if the left argument..."
No big deal. Most people will understand it that way anyway.
>doesn't define "true".
Why should it? There is no point in repeating the definition of true for
every single operator or function that returns a boolean value.
>(4) It doesn't say which true value is returned.
Why should it? True is true is true. As a programmer you really don't
care about its implementation by the compiler.
>(5) That "special false". I was going nuts trying to figure out what
>was different between
>
> $ perl -w -e 'my $j = (17 < 5); print "<$j>\n"'
> <>
>
> $ perl -w -e 'my $j = 0+(17 < 5); print "<$j>\n"'
> <0>
Why on earth would you do something like that? It is not logical (and a
_VERY_ bad practice carried over from C) to add a number and a boolean
value? What + operator and what algebra is that supposed to be?
Operators for boolean values are e.g. and, or, ||, not.
Granted, Perl does a lot of implicit type conversions or rather any
scalar automatically has numerical, boolean, and text values. But if you
make use of them, then you better know exactly what they do, e.g. what
is the value of
5 + "Hello World"
or
"The answer is 42" + 9
> $ perl -w -e 'my $j = 0+("" ); print "<$j>\n"'
> Argument "" isn't numeric in addition (+) at -e line 1.
Good! Exactly as it is supposed to be.
>(6) The stupidity that I've mentioned before, of the -r / -w / -x
>being defined as being ignorant of ACLs, when they should truly follow
>their definitions in "man perlfunc":
Yeah, you got a point. Feel free to submit a patch.
jue
------------------------------
Date: Mon, 26 Jan 2009 21:30:14 -0600
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: Perl Peeves
Message-Id: <slrngnsvu6.tkh.tadmc@tadmc30.sbcglobal.net>
Tim McDaniel <tmcd@panix.com> wrote:
> Just venting.
> (4) It doesn't say which true value is returned.
Because the programmer does not need do know.
You only need to know if it is one of the true values or one of the false values.
> It could return
> '0 ', it appears,
Yes, it could.
And the true value that it returns with today's perl version
may be different from the true value that it returns in
the next perl version.
It is not specified, so code that relies on it being a particular
value is bad code.
> and too bad if you happen to do arithmetic on it or
Bad things happen when you use numeric operators with boolean operands.
That is supposed to be surprising?
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Mon, 26 Jan 2009 19:35:44 -0800
From: Tim Greer <tim@burlyhost.com>
Subject: Re: There is no such thing as Circular Lists (was: FAQ 4.47 How do I handle circular lists?)
Message-Id: <kivfl.161289$H12.129542@newsfe12.iad>
sln@netherlands.com wrote:
> At least get your head out of your ass FAQ workers.
Feel free to submit your revision.
--
Tim Greer, CEO/Founder/CTO, BurlyHost.com, Inc.
Shared Hosting, Reseller Hosting, Dedicated & Semi-Dedicated servers
and Custom Hosting. 24/7 support, 30 day guarantee, secure servers.
Industry's most experienced staff! -- Web Hosting With Muscle!
------------------------------
Date: Mon, 26 Jan 2009 19:36:42 -0800
From: Tim Greer <tim@burlyhost.com>
Subject: Re: Vista x64 + DBD::Pg driver
Message-Id: <ejvfl.161293$H12.18399@newsfe12.iad>
mysiar wrote:
> Hi
> does anybody have this driver working ?
> If so could share "prescription" how to run it ?
>
> Regards
> Piotr
Are you having issues installing it, running it, or? If it's installed
without errors, what relevant portions of code can you post and detail
the issue (any errors, etc.)
--
Tim Greer, CEO/Founder/CTO, BurlyHost.com, Inc.
Shared Hosting, Reseller Hosting, Dedicated & Semi-Dedicated servers
and Custom Hosting. 24/7 support, 30 day guarantee, secure servers.
Industry's most experienced staff! -- Web Hosting With Muscle!
------------------------------
Date: Tue, 27 Jan 2009 02:34:45 +0200
From: Eric Pozharski <whynot@pozharski.name>
Subject: Re: Which is faster - hash or array lookup
Message-Id: <slrngnsll6.4ko.whynot@orphan.zombinet>
On 2009-01-26, Rasmus Villemoes <burner+usenet@imf.au.dk> wrote:
*SKIP*
> Now the question is, should I store these in an array or a hash,
> if I want to access a random entry as fast as possible?
(damn it, it doesn't fit in terminal)
perl -we '
use Benchmark qw|cmpthese timethese|;
my(@ar, $hs);
$ar10[$_] = $_ for 0 .. 10;
$hs10{$_} = $_ for 0 .. 10;
$ar100[$_] = $_ for 0 .. 100;
$hs100{$_} = $_ for 0 .. 100;
$ar1000[$_] = $_ for 0 .. 1000;
$hs1000{$_} = $_ for 0 .. 1000;
$ar10000[$_] = $_ for 0 .. 10000;
$hs10000{$_} = $_ for 0 .. 10000;
my $t = timethese -10, {
hash10 => sub { my $x = $hs10{int rand 11} },
array10 => sub { my $x = $ar10[int rand 11] },
hash100 => sub { my $x = $hs100{int rand 101} },
array100 => sub { my $x = $ar100[int rand 101] },
hash1000 => sub { my $x = $hs1000{int rand 1001} },
array1000 => sub { my $x = $ar1000[int rand 1001] },
hash10000 => sub { my $x = $hs10000{int rand 10001} },
array10000 => sub { my $x = $ar10000[int rand 10001] },
};
cmpthese $t;
print qq|$_ | for map scalar %$_, \%hs10, \%hs100, \%hs1000, \%hs10000;
print "\n";
'
Benchmark: running array10, array100, array1000, array10000, hash10,
hash100, hash1000, hash10000 for at least 10 CPU seconds...
array10: 14 wallclock secs (10.69 usr + 0.19 sys = 10.88 CPU) @
359942.56/s (n=3916175)
array100: 14 wallclock secs ( 9.95 usr + 0.05 sys = 10.00 CPU) @
381987.30/s (n=3819873)
array1000: 14 wallclock secs (10.20 usr + 0.05 sys = 10.25 CPU) @
366950.15/s (n=3761239)
array10000: 14 wallclock secs (10.37 usr + 0.03 sys = 10.40 CPU) @
344956.92/s (n=3587552)
hash10: 13 wallclock secs ( 9.98 usr + 0.04 sys = 10.02 CPU) @
284447.80/s (n=2850167)
hash100: 14 wallclock secs (10.16 usr + 0.04 sys = 10.20 CPU) @
281098.04/s (n=2867200)
hash1000: 13 wallclock secs (10.25 usr + 0.04 sys = 10.29 CPU) @
268208.65/s (n=2759867)
hash10000: 14 wallclock secs (10.08 usr + 0.05 sys = 10.13 CPU) @
208555.18/s (n=2112664)
Rate hash10000 hash1000 hash100 hash10 array10000 array10 array1000 array100
hash10000 208555/s -- -22% -26% -27% -40% -42% -43% -45%
hash1000 268209/s 29% -- -5% -6% -22% -25% -27% -30%
hash100 281098/s 35% 5% -- -1% -19% -22% -23% -26%
hash10 284448/s 36% 6% 1% -- -18% -21% -22% -26%
array10000 344957/s 65% 29% 23% 21% -- -4% -6% -10%
array10 359943/s 73% 34% 28% 27% 4% -- -2% -6%
array1000 366950/s 76% 37% 31% 29% 6% 2% -- -4%
array100 381987/s 83% 42% 36% 34% 11% 6% 4% --
10/16 74/128 630/1024 7391/16384
Please note, that systime varies a lot for me (YMMV). That's 5.10.0.
While for 5.8.8 (even on P200 64M (that's router)) systime is C<0.00>
*always*. Go figure.
However, even I<array10000> is 20 .. 40 percent faster that I<hash10>.
--
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom
------------------------------
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.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
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 V11 Issue 2162
***************************************
