[29379] in Perl-Users-Digest
Perl-Users Digest, Issue: 623 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jul 6 14:35:10 2007
Date: Fri, 6 Jul 2007 11:35:01 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 6 Jul 2007 Volume: 11 Number: 623
Today's topics:
Perl Menu Script <shmh@bigpond.net.au>
Re: Perl Menu Script (Randal L. Schwartz)
Re: Perl Menu Script <josef.moellers@fujitsu-siemens.com>
Re: Perl Menu Script <bik.mido@tiscalinet.it>
Re: Perl Menu Script <ts@dionic.net>
Re: Perl Menu Script <shmh@bigpond.net.au>
Re: Perl Menu Script <ts@dionic.net>
Re: Perl Menu Script <spamtrap@dot-app.org>
Re: Portable general timestamp format, not 2038-limited <bignose+hates-spam@benfinney.id.au>
Re: Portable general timestamp format, not 2038-limited <james.harris.1@googlemail.com>
Re: Portable general timestamp format, not 2038-limited <james.harris.1@googlemail.com>
Re: Portable general timestamp format, not 2038-limited <hjp-usenet2@hjp.at>
Re: Portable general timestamp format, not 2038-limited <james.harris.1@googlemail.com>
Re: Portable general timestamp format, not 2038-limited <greg@cosc.canterbury.ac.nz>
Re: Portable general timestamp format, not 2038-limited <roy@panix.com>
Re: Portable general timestamp format, not 2038-limited <wlfraed@ix.netcom.com>
Re: Portable general timestamp format, not 2038-limited <james.harris.1@googlemail.com>
Re: Portable general timestamp format, not 2038-limited <james.harris.1@googlemail.com>
Re: Portable general timestamp format, not 2038-limited <nospam-abuse@ilyaz.org>
Re: Portable general timestamp format, not 2038-limited <nowhere@a.com>
Re: Portable general timestamp format, not 2038-limited <wlfraed@ix.netcom.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 05 Jul 2007 04:00:40 GMT
From: "Simon" <shmh@bigpond.net.au>
Subject: Perl Menu Script
Message-Id: <I1_ii.3445$4A1.2631@news-server.bigpond.net.au>
Hi guys!
Id like to learn about creating a menu in a perl script.
What Id like to do is the following.
============================================
Print "Press 1 for this subroutine";
Print "Press 2 for this subroutine";
Print "Press 3 for this subroutine";
Print "Press 4 for this subroutine";
Print "Press 5 for this subroutine";
Print "Press 6 for this subroutine";
Then the stdin is captured and goes to the right subroutine to execute.
Any help appreciated.
------------------------------
Date: Wed, 04 Jul 2007 21:57:03 -0700
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: "Simon" <shmh@bigpond.net.au>
Subject: Re: Perl Menu Script
Message-Id: <861wfno3c0.fsf@blue.stonehenge.com>
>>>>> "Simon" == Simon <shmh@bigpond.net.au> writes:
Simon> Id like to learn about creating a menu in a perl script.
Simon> What Id like to do is the following.
Yeah, I'd like to get an "A" in class too, especially by cheating. Right.
Please don't post Homework problems here.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
--
Posted via a free Usenet account from http://www.teranews.com
------------------------------
Date: Thu, 05 Jul 2007 08:46:17 +0200
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: Perl Menu Script
Message-Id: <f6i43t$vh$1@nntp.fujitsu-siemens.com>
Simon wrote:
> Hi guys!
>=20
> Id like to learn about creating a menu in a perl script.
>=20
> What Id like to do is the following.
>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Print "Press 1 for this subroutine";
> Print "Press 2 for this subroutine";
> Print "Press 3 for this subroutine";
> Print "Press 4 for this subroutine";
> Print "Press 5 for this subroutine";
> Print "Press 6 for this subroutine";
>=20
> Then the stdin is captured and goes to the right subroutine to execute.=
>=20
>=20
> Any help appreciated.=20
Putting aside what Randal wrote: This is not the place to ask for code,=20
this is the place to discuss code, so: post whatever you have tried and=20
we're glad to help you get/stay on the right track.
BTW: Don't assume your teachers are stupid.
--=20
These are my personal views and not those of Fujitsu Siemens Computers!
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize (T. Pratchett)
Company Details: http://www.fujitsu-siemens.com/imprint.html
------------------------------
Date: Thu, 05 Jul 2007 09:22:56 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Perl Menu Script
Message-Id: <d17p835r5v5fjfu12lnjhbich5bin8adhg@4ax.com>
On Thu, 05 Jul 2007 04:00:40 GMT, "Simon" <shmh@bigpond.net.au> wrote:
>Id like to learn about creating a menu in a perl script.
In which context? A GUI? A Web interface? A console based UI?
Michele
--
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
.'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,
------------------------------
Date: Thu, 05 Jul 2007 09:17:45 +0100
From: Tim Southerwood <ts@dionic.net>
Subject: Re: Perl Menu Script
Message-Id: <468ca929$0$648$5a6aecb4@news.aaisp.net.uk>
Simon wrote:
> Hi guys!
>
> Id like to learn about creating a menu in a perl script.
>
> What Id like to do is the following.
>
>
> ============================================
>
> Print "Press 1 for this subroutine";
> Print "Press 2 for this subroutine";
> Print "Press 3 for this subroutine";
> Print "Press 4 for this subroutine";
> Print "Press 5 for this subroutine";
> Print "Press 6 for this subroutine";
>
> Then the stdin is captured and goes to the right subroutine to execute.
>
>
> Any help appreciated.
I honesly don't know if this is homework or not, so I'll give you some hints
in semi-good faith:
Have a look at ncurses and perl - you'll do a better job than the above and
it won't be hard.
Otherwise I would google for: "reading keypress perl" and, if you want to be
neat, subroutine references to achieve exactly what you outline.
Cheers
Tim
------------------------------
Date: Thu, 05 Jul 2007 09:23:48 GMT
From: "Simon" <shmh@bigpond.net.au>
Subject: Re: Perl Menu Script
Message-Id: <EM2ji.3571$4A1.2169@news-server.bigpond.net.au>
Hi Guys!
Dont know if any of you were waiting for a response from me...pretty sure
the first guy is :>)....amusing!
No need to dignify that first comment with any comeback...better things to
do :>)
Moving on....
We have a requirement at work for this and as such I will take on board your
guys' suggestions.
Thanku :>)
"Tim Southerwood" <ts@dionic.net> wrote in message
news:468ca929$0$648$5a6aecb4@news.aaisp.net.uk...
> Simon wrote:
>
>> Hi guys!
>>
>> Id like to learn about creating a menu in a perl script.
>>
>> What Id like to do is the following.
>>
>>
>> ============================================
>>
>> Print "Press 1 for this subroutine";
>> Print "Press 2 for this subroutine";
>> Print "Press 3 for this subroutine";
>> Print "Press 4 for this subroutine";
>> Print "Press 5 for this subroutine";
>> Print "Press 6 for this subroutine";
>>
>> Then the stdin is captured and goes to the right subroutine to execute.
>>
>>
>> Any help appreciated.
>
> I honesly don't know if this is homework or not, so I'll give you some
> hints
> in semi-good faith:
>
> Have a look at ncurses and perl - you'll do a better job than the above
> and
> it won't be hard.
>
> Otherwise I would google for: "reading keypress perl" and, if you want to
> be
> neat, subroutine references to achieve exactly what you outline.
>
> Cheers
>
> Tim
------------------------------
Date: Thu, 05 Jul 2007 11:11:26 +0100
From: Tim Southerwood <ts@dionic.net>
Subject: Re: Perl Menu Script
Message-Id: <468cc3d0$0$646$5a6aecb4@news.aaisp.net.uk>
Simon wrote:
> Hi Guys!
>
> Dont know if any of you were waiting for a response from me...pretty sure
> the first guy is :>)....amusing!
> No need to dignify that first comment with any comeback...better things to
> do :>)
>
> Moving on....
>
> We have a requirement at work for this and as such I will take on board
> your guys' suggestions.
>
> Thanku :>)
>
Hi,
You have to understand that USENET gets a fair few postings that are
genuinely homework or university assignments.
Unfortunately, rightly or wrongly, your query fits the format.
USENET isn't a pay-for-professional-advice service, so people are free to
answer any way they like.
If you have a problem, post the code (minimal example to demonstrate the
problem) and I'm sure you will get many helpful responses.
Just the way it works.
Anyway, good luck with your project,
Tim
------------------------------
Date: Thu, 05 Jul 2007 06:41:22 -0400
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: Perl Menu Script
Message-Id: <m28x9v8759.fsf@dot-app.org>
Tim Southerwood <ts@dionic.net> writes:
> Otherwise I would google for: "reading keypress perl" and, if you want to be
> neat, subroutine references to achieve exactly what you outline.
I wouldn't. Google is my first choice as a search engine, but "perldoc -q
keyboard input" gives a perfectly cromulent answer. Also, "perldoc perlreftut"
is a great introduction to references. If you don't know what perldocs are
included with Perl, "perldoc perl" will give you a list.
The docs included with Perl are authoritative. Google will give you some good
links, true - but for every good one, it will also give you fifty hits that
were written by someone who wrote "#!/usr/bin/perl" for the first time last
Friday, who thinks that it's spelled PERL, and who thinks "use strict" causes
bugs in your code.
sherm--
--
Web Hosting by West Virginians, for West Virginians: http://wv-www.net
Cocoa programming in Perl: http://camelbones.sourceforge.net
------------------------------
Date: Wed, 04 Jul 2007 17:09:53 +1000
From: Ben Finney <bignose+hates-spam@benfinney.id.au>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <87tzskoda6.fsf@benfinney.id.au>
CBFalconer <cbfalconer@yahoo.com> writes:
> "Peter J. Holzer" wrote:
> > Hardly. That hasn't been in use for over 35 years (according to
> > Wikipedia).
>
> I am glad to see you depend on absolutely reliable sources.
Wikipedia is not an absolutely reliable source. I know of no
"absolutely resliable source". We work with imperfect human-provided
data all the time.
--
\ "If you ever teach a yodeling class, probably the hardest thing |
`\ is to keep the students from just trying to yodel right off. |
_o__) You see, we build to that." -- Jack Handey |
Ben Finney
------------------------------
Date: Wed, 04 Jul 2007 11:46:00 -0700
From: James Harris <james.harris.1@googlemail.com>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <1183574760.225389.266470@o61g2000hsh.googlegroups.com>
On 1 Jul, 15:11, "Peter J. Holzer" <hjp-usen...@hjp.at> wrote:
...
> Stick to unix timestamps but store them as a double precision floating
> point number. The 53 bit mantissa gives you currently a resolution of
> about 200 ns, slowly deteriorating (you will hit ms resolution in about
> 280,000 years, if I haven't miscalculated). Any language and database
> should be able to handle double-precision FP numbers, so that's as
> portable as it gets and conversion from/to system time should be
> trivial.
>
> If you need to represent milliseconds exactly, you can just multiply the
> timestamp with 1000 (and get java timestamps).
Interesting option. I think my choice is between separate day and sub-
day 32-bit unsigned integers, text, and this 64-bit float option.
I'm not clear, though. Did you mean to store double precision numbers
where the seconds are the units (I assume this) or where the days are
the units? And what do you think of the other option?
------------------------------
Date: Wed, 04 Jul 2007 12:10:55 -0700
From: James Harris <james.harris.1@googlemail.com>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <1183576255.668414.256990@q69g2000hsb.googlegroups.com>
On 3 Jul, 06:12, Scott David Daniels <scott.dani...@acm.org> wrote:
...
> Inspired format:
> Days since a some standard date (the TAI date may be a good such
> date) expressed as fixed point 64-bit (32-bit day part, 32-bit
> day-fraction part) or floating point (using Intel's double-precision,
> for example, gives you 26 bits each for day and day-fraction, though
> the binary point moves for particular stamps).
This is close to or the same as my original suggestion. The break
between days and sub-days seems to make more sense than breaking the
fractional part elsewhere. It also gives a convenient point to hang
datestamps on rather than just timestamps.
FWIW I wonder if a 64-bit version of the above would cope with all
practical time needs. With that the time would range to +/- 9000
quintillion years (18 digits) and there would be over 200 trillion
ticks per second or 200 in a picosecond making, I think, each tick 5
femtoseconds.
------------------------------
Date: Wed, 4 Jul 2007 23:18:10 +0200
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <slrnf8o3ki.rhk.hjp-usenet2@zeno.hjp.at>
On 2007-07-04 18:46, James Harris <james.harris.1@googlemail.com> wrote:
> On 1 Jul, 15:11, "Peter J. Holzer" <hjp-usen...@hjp.at> wrote:
> ...
>> Stick to unix timestamps but store them as a double precision floating
>> point number. The 53 bit mantissa gives you currently a resolution of
>> about 200 ns, slowly deteriorating (you will hit ms resolution in about
>> 280,000 years, if I haven't miscalculated). Any language and database
>> should be able to handle double-precision FP numbers, so that's as
>> portable as it gets and conversion from/to system time should be
>> trivial.
>>
>> If you need to represent milliseconds exactly, you can just multiply the
>> timestamp with 1000 (and get java timestamps).
>
> Interesting option. I think my choice is between separate day and sub-
> day 32-bit unsigned integers, text, and this 64-bit float option.
>
> I'm not clear, though. Did you mean to store double precision numbers
> where the seconds are the units (I assume this) or where the days are
> the units? And what do you think of the other option?
I was thinking about using the seconds as units (so
2007-07-04T23:02:04.123 CET is represented as 1183582924.123).
It's a natural extension of the unix time stamp, so you can often just
pass the values to the normal date routines (especially in languages
like perl which don't really distinguish between integers and floating
point numbers).
But it really doesn't matter much. If you ignore leap seconds, using
days instead of seconds is just a constant factor (in fact, the unix
timestamp ignores leap seconds, too, so it's always a constant factor).
You can't represent a second exactly if the unit is one day (1/86400 is
not a multiple of a power of two), but that probably doesn't matter.
hp
--
_ | Peter J. Holzer | I know I'd be respectful of a pirate
|_|_) | Sysadmin WSR | with an emu on his shoulder.
| | | hjp@hjp.at |
__/ | http://www.hjp.at/ | -- Sam in "Freefall"
------------------------------
Date: Wed, 04 Jul 2007 16:04:10 -0700
From: James Harris <james.harris.1@googlemail.com>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <1183590250.478207.139190@k79g2000hse.googlegroups.com>
On 4 Jul, 22:18, "Peter J. Holzer" <hjp-usen...@hjp.at> wrote:
...
> But it really doesn't matter much. If you ignore leap seconds, using
> days instead of seconds is just a constant factor (in fact, the unix
> timestamp ignores leap seconds, too, so it's always a constant factor).
> You can't represent a second exactly if the unit is one day (1/86400 is
> not a multiple of a power of two), but that probably doesn't matter.
Sure. However, the proposal was to define ticks as 25 microseconds.
------------------------------
Date: Thu, 05 Jul 2007 13:53:52 +1200
From: greg <greg@cosc.canterbury.ac.nz>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <5f31fvF3asl6lU1@mid.individual.net>
James Harris wrote:
> With that the time would range to +/- 9000
> quintillion years (18 digits)
Use the Big Bang as the epoch, and you won't have
to worry about negative timestamps.
--
Greg
------------------------------
Date: Wed, 04 Jul 2007 22:12:46 -0400
From: Roy Smith <roy@panix.com>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <roy-ACB718.22124604072007@032-325-625.area1.spcsdns.net>
ames Harris <james.harris.1@googlemail.com> wrote:
> I have a requirement to store timestamps in a database. Simple enough
> you might think but finding a suitably general format is not easy. The
> specifics are
>
> 1) subsecond resolution - milliseconds or, preferably, more detailed
> 2) not bounded by Unix timestamp 2038 limit
> 3) readable in Java
> 4) writable portably in Perl which seems to mean that 64-bit values
> are out
> 5) readable and writable in Python
> 6) storable in a free database - Postgresql/MySQL
Astronomers use Julian Date (http://en.wikipedia.org/wiki/Julian_date) for
calculations like this. It's a widely used format and highly portable.
I'm sure there are libraries to deal with it in all the languages you
mention (and more). Ask on sci.astro for more information.
------------------------------
Date: Thu, 05 Jul 2007 07:46:18 GMT
From: Dennis Lee Bieber <wlfraed@ix.netcom.com>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <el1ji.3946$rR.1090@newsread2.news.pas.earthlink.net>
On Wed, 04 Jul 2007 22:12:46 -0400, Roy Smith <roy@panix.com> declaimed
the following in comp.lang.python:
> Astronomers use Julian Date (http://en.wikipedia.org/wiki/Julian_date) for
> calculations like this. It's a widely used format and highly portable.
> I'm sure there are libraries to deal with it in all the languages you
> mention (and more). Ask on sci.astro for more information.
<playing devils advocate> But do you also need to account for
Besselian or Julian centuries (Astronomy used to use B1900 as a
computational epoch, but now uses J2000. A Julian century is 36525 days,
Besselian century was 36524.22 days.
--
Wulfraed Dennis Lee Bieber KD6MOG
wlfraed@ix.netcom.com wulfraed@bestiaria.com
HTTP://wlfraed.home.netcom.com/
(Bestiaria Support Staff: web-asst@bestiaria.com)
HTTP://www.bestiaria.com/
------------------------------
Date: Thu, 05 Jul 2007 12:56:10 -0700
From: James Harris <james.harris.1@googlemail.com>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <1183665370.643503.157060@m36g2000hse.googlegroups.com>
On 5 Jul, 02:53, greg <g...@cosc.canterbury.ac.nz> wrote:
> James Harris wrote:
> > With that the time would range to +/- 9000
> > quintillion years (18 digits)
>
> Use the Big Bang as the epoch, and you won't have
> to worry about negative timestamps.
Good idea if only they didn't keep shifting the femtosecond on which
it happened...... :-)
------------------------------
Date: Thu, 05 Jul 2007 13:07:55 -0700
From: James Harris <james.harris.1@googlemail.com>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <1183666075.705846.283660@c77g2000hse.googlegroups.com>
On 5 Jul, 08:46, Dennis Lee Bieber <wlfr...@ix.netcom.com> wrote:
> On Wed, 04 Jul 2007 22:12:46 -0400, Roy Smith <r...@panix.com> declaimed
> the following in comp.lang.python:
>
> > Astronomers use Julian Date (http://en.wikipedia.org/wiki/Julian_date) for
> > calculations like this. It's a widely used format and highly portable.
> > I'm sure there are libraries to deal with it in all the languages you
> > mention (and more). Ask on sci.astro for more information.
>
> <playing devils advocate> But do you also need to account for
> Besselian or Julian centuries (Astronomy used to use B1900 as a
> computational epoch, but now uses J2000. A Julian century is 36525 days,
> Besselian century was 36524.22 days.
Whew! It was for reasons such as this that I suggested treating a day
(i.e. a /nominal/ 24-hour period) as the primary unit. The Gregorian
switch to Julian, for example, missed out a bunch of days to adjust
the calendars of Christendom but they had to be whole numbers of days.
In terms of real people (about the level I need) once a dividing line
has been chosen between one day and the next it becomes a reference
point.
Incidentally I have chosen to store /average/ values in the
application so if the sample period is 10 seconds and the count
increases by 45 I will store 4.5. This is plottable directly and I
could even allow an 11 second sample when a leap second is added (if I
needed that detail).
Is your Julian century a bit long, on average, 2000, 2400, 2800 etc
having 28 days in Feb?
------------------------------
Date: Thu, 5 Jul 2007 20:48:08 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <f6jle8$1inq$1@agate.berkeley.edu>
[A complimentary Cc of this posting was sent to
James Harris
<james.harris.1@googlemail.com>], who wrote in article <1183665370.643503.157060@m36g2000hse.googlegroups.com>:
> On 5 Jul, 02:53, greg <g...@cosc.canterbury.ac.nz> wrote:
> > James Harris wrote:
> > > With that the time would range to +/- 9000
> > > quintillion years (18 digits)
> >
> > Use the Big Bang as the epoch, and you won't have
> > to worry about negative timestamps.
In pedantic mode: negative timestamps make sense with Big Bang as the
epoch as well. (AFAIU, the current way of thinking is that it was
"just too hot" before the big bang, it is not that "there was
nothing".)
Hope this helps,
Ilya
------------------------------
Date: Thu, 05 Jul 2007 20:57:32 GMT
From: Wojtek <nowhere@a.com>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <mn.2b457d778de67d3d.70216@a.com>
James Harris wrote :
> I have a requirement to store timestamps in a database. Simple enough
> you might think but finding a suitably general format is not easy. The
> specifics are
>
> 2) not bounded by Unix timestamp 2038 limit
I use the Java Calendar class for storing dates, which as I understand
it, uses a long to store the date/time/milliseconds.
In my application I use the date 9999.12.31 23:59:59.000 to store a
blank date. Calendar has no problem storing that date, and returning
the correct year, month, day, hour, minute, and second.
Note: Since I am using the year 9999 as a "magic number", some of you
may think that I am repeating the Y2K problem. Hey, if my application
is still being used in the year 9998 I am not being paid nearly
enough...
--
Wojtek :-)
------------------------------
Date: Fri, 06 Jul 2007 06:12:39 GMT
From: Dennis Lee Bieber <wlfraed@ix.netcom.com>
Subject: Re: Portable general timestamp format, not 2038-limited
Message-Id: <r3lji.4203$rR.3533@newsread2.news.pas.earthlink.net>
On Thu, 05 Jul 2007 13:07:55 -0700, James Harris
<james.harris.1@googlemail.com> declaimed the following in
comp.lang.python:
> Is your Julian century a bit long, on average, 2000, 2400, 2800 etc
> having 28 days in Feb?
Astronomy doesn't care about the seasons <G>
--
Wulfraed Dennis Lee Bieber KD6MOG
wlfraed@ix.netcom.com wulfraed@bestiaria.com
HTTP://wlfraed.home.netcom.com/
(Bestiaria Support Staff: web-asst@bestiaria.com)
HTTP://www.bestiaria.com/
------------------------------
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 623
**************************************
