[29670] in Perl-Users-Digest
Perl-Users Digest, Issue: 914 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sun Oct 7 16:09:43 2007
Date: Sun, 7 Oct 2007 13:09:07 -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 Sun, 7 Oct 2007 Volume: 11 Number: 914
Today's topics:
Re: Getting file size before closing the file <nobull67@gmail.com>
Re: Huge cgi!Help! <Zazen85@gmail.com>
Re: perl join on a non printable variable character ? <nobull67@gmail.com>
Re: perl join on a non printable variable character ? <nobull67@gmail.com>
Perl-ish mail formatting question regarding "\t" <uctraing@ultranet.com>
Re: Perl-ish mail formatting question regarding "\t" <bill@ts1000.us>
Re: print a number in hex <mritty@gmail.com>
Re: print a number in hex <sting.t2@gmail.com>
Re: print a number in hex <mritty@gmail.com>
Script not able to work on Server 2003 <jruffino@gailborden.info>
Re: The Modernization of Emacs: terminology buffer and (Bent C Dalager)
Re: The Modernization of Emacs: terminology buffer and <lew@lewscanon.com>
Re: The Modernization of Emacs: terminology buffer and <dak@gnu.org>
Re: The Modernization of Emacs: terminology buffer and <lew@lewscanon.com>
Re: The Modernization of Emacs: terminology buffer and <lew@lewscanon.com>
Re: The Modernization of Emacs: terminology buffer and <lew@lewscanon.com>
Re: The Modernization of Emacs: terminology buffer and <cor@clsnet.nl>
Re: The Modernization of Emacs: terminology buffer and <keramida@ceid.upatras.gr>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sun, 07 Oct 2007 17:46:38 -0000
From: Brian McCauley <nobull67@gmail.com>
Subject: Re: Getting file size before closing the file
Message-Id: <1191779198.088102.312090@r29g2000hsg.googlegroups.com>
On Oct 7, 1:39 pm, Josef Moellers <5502109103600...@t-online.de>
wrote:
> select((select($dst), $| = 1)[0]); # <<<<<<<<<<<<<<<<<
> print $dst "Hello, my dear\n";
> my $size = -s $dst;
> print "Destination file is $size\n";
If there's more than on print it would reduce the inefficiency to
flush the handle _after_ all the prints().
Although the above works it's more idiomatic to say:
use IO::Handle;
$dst->flush;
my $size = -s $dst;
Or, since we know the cursor will be at a the end we can do away with
the flush and simply:
my $size = tell $dst;
------------------------------
Date: Sun, 07 Oct 2007 19:55:21 -0000
From: Zazen <Zazen85@gmail.com>
Subject: Re: Huge cgi!Help!
Message-Id: <1191786921.591101.130450@v3g2000hsg.googlegroups.com>
Mark wrote:
> You need to read the group posting guidelines.
>
> However, you can try the following:
>
> put "use strict;" at the top of your script and fix the resulting errors.
>
> run the script from the command-line
>
> put
>
> use CGI::Carp qw(fatalsToBrowser);
>
> at the top of your script. This may help you to better diagnose any
> problems.
>
> When I run the script, connetti *is* called, but the pop connection
> isn't succeeding and you aren't testing for that. From the perldoc:
>
> *State* The internal state of the connection: DEAD, AUTHORIZATION,
> TRANSACTION.
>
> so try checking $pop->State();
>
> Mark
Thanks Mark,i begin to find all the things that cause to fall the
script,Thanks a lot!
------------------------------
Date: Sun, 07 Oct 2007 17:27:06 -0000
From: Brian McCauley <nobull67@gmail.com>
Subject: Re: perl join on a non printable variable character ?
Message-Id: <1191778026.285806.297140@22g2000hsm.googlegroups.com>
On Oct 6, 8:18 pm, brian d foy <brian.d....@gmail.com> wrote:
> In article <1191689627.684691.213...@19g2000hsx.googlegroups.com>,
>
> Brian McCauley <nobul...@gmail.com> wrote:
> > Be aware, however, that the FAQ answer to "How can I expand variables
> > in text strings?" is full of half-truths and misdirection. See
> > numerous previous threads on the subject "How can I expand variables
> > in text strings?" for details.
>
> I thought we'd fixed the problems you had.
No, there were two parts. There was the big issue, on which, I thought
we'd agreed to differ and there were a number of smaller issues about
minor details which you have fixed in the version that'll ship with
5.10.
> What's the problem now?
OK this is also partly an issue of tense when we speak of "now". When
I speak of "The Perl FAQ" in the present tense (without further
qualification) I refer to the FAQ as released with the current
x.even.x release of Perl.
http://search.cpan.org/~rgarcia/perl/pod/perlfaq4.pod#How_can_I_expand_variables_in_text_strings?
This is much much better that in used to be in that it fixes the
mistakes in what it was trying to say.
But it still a "half truth" in so far as it doesn't show people the
simple, obvious (and very dangerous) solution using eval(STRING) and a
here-doc.
In my experience, when most people ask come to the FAQ with a question
for which the closest approximation in the FAQ is "How can I expand
variables in text strings?" the question that's actually in their mind
is "How do I evaluate the contents of a scalar variable as if it were
a double-quotish string in Perl source?". The question the FAQ chooses
to answer is "How do I implement string templates in Perl?". In some
sense this is the right question to answer because the reader could
quite possibly be in an X-Y situation.
However since the question that's actually Frequently Asked is "How do
I evaluate the contents of a scalar variable as if it were a double-
quotish string in Perl source?" and since there exists a simple answer
to that question, IMNSHO it's somewhat intellectually dishonest not
to mention that answer.
[ slightly out of the original context, brian asked ... ]
> Now you're calling me a liar?
I consider it unhelpful to characterise my opinion that the answer in
5.9.5 remains somewhat intellectually dishonest with emotive terms
like "calling you a liar". But if you choose to see it that way then I
suppose I am.
Some people (maybe even you) have argued that the FAQ should not
include the simple answer because executing data is fraught with
dangers. The problem with this is, as I've said so many times before,
that when people come up with (or otherwise come across) the simple
solution they'll typically:
1) Not figure out the here-doc bit so get an inferior eval-based
solution.
2) Loose trust in the FAQ and/or feel insulted.
3) Not realise just how dangerous the simple eval-based solution can
be.
I stand by the position I've held consistently for many years. The FAQ
should mention, at least by reference, the eval-based templating
solution so that people can see it, be made fully aware of the danger
and make in informed choice whether or not to use it.
------------------------------
Date: Sun, 07 Oct 2007 17:31:55 -0000
From: Brian McCauley <nobull67@gmail.com>
Subject: Re: perl join on a non printable variable character ?
Message-Id: <1191778315.037351.319010@22g2000hsm.googlegroups.com>
On Oct 7, 5:32 am, "Mumia W." <paduille.4061.mumia.w
+nos...@earthlink.net> wrote:
> On 10/06/2007 04:48 PM, Jack wrote:
>
> > Thanks but still dont have an answer to the question - thanks for all
> > the other pointers, but how do I change my code to join on the
> > argument I passed in - specifically on the join call if possible.
>
> > Thanks in advance, Jack
>
> The delimiter needs to be converted before use. If you don't mind
> cheating, you could do this:
>
> $delimiter = eval("\"$delimiter\"");
>
> (Mumia ducks)
Wise :-)
> Okay, sorry about that. "Eval" is evil I know. You could also do this:
>
> $delimiter =~ s/^\\//;
> $delimiter = chr oct $delimiter;
>
> However, that can't deal with delimiters specified in hex on the command
> line.
The solution I posted (Sat, 06 Oct 2007 17:46:15 -0000) covers all
possibilities but I'm not 100% convinced that my escaping of ["$@]
characters would be sufficient to prevent a determined attacker from
exploiting the eval.
------------------------------
Date: Sun, 07 Oct 2007 15:18:19 GMT
From: - Bob - <uctraing@ultranet.com>
Subject: Perl-ish mail formatting question regarding "\t"
Message-Id: <l3uhg35nfpal7tr8563jo6vlegk04iq525@4ax.com>
I'm stringing together some output that gets sent in a "plain text"
email from Perl Net::SMTP to a POP server and is then pulled by the
client. There's no MIME type, just plain text.
I use \t to do some crude layout. Unfortunately the tab character
seems to be ignored in MS Outlook/Express. It's in there, and if I
view the raw message source in Outlook I can see the tabs working
properly. But, it doesn't show up in the regular message viewing
window. (Note: MS changes to a proportional font in the regular
viewing window but I'd expect the tab to still space to some sort of
indent).
Thoughts on this? Is there another character combo besides \t that
would force the tab? Is this just a specific MS Outlook specific flaw?
Do I need to spew MIME headers to get this to work properly? (If so, I
could use a pointer to a sample of proper MIME mail header spewing).
Thanks,
------------------------------
Date: Sun, 07 Oct 2007 09:10:36 -0700
From: Bill H <bill@ts1000.us>
Subject: Re: Perl-ish mail formatting question regarding "\t"
Message-Id: <1191773436.543837.27460@57g2000hsv.googlegroups.com>
On Oct 7, 11:18 am, - Bob - <uctra...@ultranet.com> wrote:
> I'm stringing together some output that gets sent in a "plain text"
> email from Perl Net::SMTP to a POP server and is then pulled by the
> client. There's no MIME type, just plain text.
>
> I use \t to do some crude layout. Unfortunately the tab character
> seems to be ignored in MS Outlook/Express. It's in there, and if I
> view the raw message source in Outlook I can see the tabs working
> properly. But, it doesn't show up in the regular message viewing
> window. (Note: MS changes to a proportional font in the regular
> viewing window but I'd expect the tab to still space to some sort of
> indent).
>
> Thoughts on this? Is there another character combo besides \t that
> would force the tab? Is this just a specific MS Outlook specific flaw?
> Do I need to spew MIME headers to get this to work properly? (If so, I
> could use a pointer to a sample of proper MIME mail header spewing).
> Thanks,
Its an Outlook thing. If you want to control the layout best thing is
to go with mime headers and then you can use the <TT> tag to get fixed
font size and use spaces instead of tabs.
Bill H
------------------------------
Date: Sun, 07 Oct 2007 08:15:12 -0700
From: Paul Lalli <mritty@gmail.com>
Subject: Re: print a number in hex
Message-Id: <1191770112.598117.305010@o80g2000hse.googlegroups.com>
On Oct 7, 8:31 am, Amir <sting...@gmail.com> wrote:
> I have a variable let's say $address, I would like to print it ,
> but in its Hex value and not Decimal, how can I do it?
Use printf() (or sprintf()), using either the %x or %X format
specifier:
$ perl -e'printf("%X\n", 30)'
1E
Paul Lalli
------------------------------
Date: Sun, 07 Oct 2007 17:51:02 -0000
From: Amir <sting.t2@gmail.com>
Subject: Re: print a number in hex
Message-Id: <1191779462.725237.55380@y42g2000hsy.googlegroups.com>
On Oct 7, 5:15 pm, Paul Lalli <mri...@gmail.com> wrote:
> On Oct 7, 8:31 am, Amir <sting...@gmail.com> wrote:
>
> > I have a variable let's say $address, I would like to print it ,
> > but in its Hex value and not Decimal, how can I do it?
>
> Use printf() (or sprintf()), using either the %x or %X format
> specifier:
>
> $ perl -e'printf("%X\n", 30)'
> 1E
>
> Paul Lalli
thanks guys,
I have one more question,
I have this code:
$address = ($address & zero_bits(3,11)) | (($col<<3) & 0xff8);
now, the function zero_bits returns a hex number, but it seems that
perl considers it as a decimal, and calculates wrongly the bitwise.
what should I do?!
thanks again
-Amir
------------------------------
Date: Sun, 07 Oct 2007 11:01:58 -0700
From: Paul Lalli <mritty@gmail.com>
Subject: Re: print a number in hex
Message-Id: <1191780118.418148.100370@y42g2000hsy.googlegroups.com>
On Oct 7, 1:51 pm, Amir <sting...@gmail.com> wrote:
> I have this code:
> $address = ($address & zero_bits(3,11)) | (($col<<3) & 0xff8);
> now, the function zero_bits returns a hex number,
No. Perl does not return hex nor decimal. It returns numbers.
"hex" and "decimal" and "octal" are simply ways of displaying
representations of numbers.
> but it seems that
> perl considers it as a decimal, and calculates wrongly the bitwise.
> what should I do?!
You should do what the Posting Guidelines tell you to do - create a
short-but-complete script that demonstrates your problem, and post
that.
Paul Lalli
------------------------------
Date: Sun, 07 Oct 2007 12:57:17 -0700
From: Joe <jruffino@gailborden.info>
Subject: Script not able to work on Server 2003
Message-Id: <1191787037.892019.155830@k79g2000hse.googlegroups.com>
I have PERL scripst that I created on a Windows 2000 Server, that work
great. We switched to a Windows 2003 Server, PERL is installed, but my
script that works on 2000, will not work with the 2003 server. I keep
getting the following error on all my scripts:
"Content-type: text/html
'C:\Inetpub\wwwroot\cgi-bin\Employee_Status\employee_status.cgi'
script produced no output"
Plus, I have tried changing the extension to cgi, and I get the same
error.
Does anyone have any suggestions for me? I'm almost positive it is
something simple, but I am just not seeing it.
------------------------------
Date: Sun, 7 Oct 2007 14:28:04 +0000 (UTC)
From: bcd@pvv.ntnu.no (Bent C Dalager)
Subject: Re: The Modernization of Emacs: terminology buffer and keybinding
Message-Id: <feaqdk$4mm$1@orkan.itea.ntnu.no>
In article <Xns99C252D1319CElhb123@140.99.99.130>, <lhb@nowhere.com> wrote:
>
>Words are defined by popular usage. In popular usage, the meaning of free
>as an adjective depends on the context. If the adjective is applied to
>people, it means the opposite of slavery or imprisonment. If it's applied
>to something other than people, it means free as in beer.
It's strange how that doesn't work for "speech" though isn't it? Or
"country" for that matter.
>(...) The meaning has to be
>adopted by popular usage, which free-as-in-GPL software has not been.
How do you suggest a term would come to be adopted by popular usage,
except by someone first starting to use it?
Cheers
Bent D
--
Bent Dalager - bcd@pvv.org - http://www.pvv.org/~bcd
powered by emacs
------------------------------
Date: Sun, 07 Oct 2007 12:29:35 -0400
From: Lew <lew@lewscanon.com>
Subject: Re: The Modernization of Emacs: terminology buffer and keybinding
Message-Id: <N5mdnYmOQ-7ylJTanZ2dnUVZ_vamnZ2d@comcast.com>
lhb@nowhere.com wrote:
> Words are defined by popular usage. In popular usage, the meaning of free
> as an adjective depends on the context. If the adjective is applied to
> people, it means the opposite of slavery or imprisonment. If it's applied
> to something other than people, it means free as in beer.
Unless it's applied to open-source software, which by popular usage has "free"
mean "free of restrictions on use."
Words are also defined by technical usage. Would you claim that "thread"
means only a yarn of fabric?
> For example, a dog with no owner, wandering freely (adverb), would not be
> called a free dog (adjective), to mean possessing freedom. Free dog means
> free as in beer.
"I was walking my dog, but he got free of the leash. Now he's running free
all over the neighborhood."
The "popular" usage of "free" with respect to open-source software is "free as
in speech", so your argument favors the FSF on this one.
--
Lew
------------------------------
Date: Sun, 07 Oct 2007 18:32:52 +0200
From: David Kastrup <dak@gnu.org>
Subject: Re: The Modernization of Emacs: terminology buffer and keybinding
Message-Id: <85wstykhqj.fsf@lola.goethe.zz>
Lew <lew@lewscanon.com> writes:
> lhb@nowhere.com wrote:
>> Words are defined by popular usage. In popular usage, the meaning
>> of free as an adjective depends on the context. If the adjective is
>> applied to people, it means the opposite of slavery or imprisonment.
>> If it's applied to something other than people, it means free as in
>> beer.
>
> Unless it's applied to open-source software, which by popular usage
> has "free" mean "free of restrictions on use."
>
> Words are also defined by technical usage. Would you claim that
> "thread" means only a yarn of fabric?
>
>> For example, a dog with no owner, wandering freely (adverb), would
>> not be called a free dog (adjective), to mean possessing freedom.
>> Free dog means free as in beer.
>
> "I was walking my dog, but he got free of the leash. Now he's running
> free all over the neighborhood."
Uh, neither of which contains "free dog".
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
------------------------------
Date: Sun, 07 Oct 2007 12:36:39 -0400
From: Lew <lew@lewscanon.com>
Subject: Re: The Modernization of Emacs: terminology buffer and keybinding
Message-Id: <j4idnUD3ktWKlpTanZ2dnUVZ_ujinZ2d@comcast.com>
David Kastrup wrote:
> Lew <lew@lewscanon.com> writes:
>
>> lhb@nowhere.com wrote:
>>> Words are defined by popular usage. In popular usage, the meaning
>>> of free as an adjective depends on the context. If the adjective is
>>> applied to people, it means the opposite of slavery or imprisonment.
>>> If it's applied to something other than people, it means free as in
>>> beer.
>> Unless it's applied to open-source software, which by popular usage
>> has "free" mean "free of restrictions on use."
>>
>> Words are also defined by technical usage. Would you claim that
>> "thread" means only a yarn of fabric?
>>
>>> For example, a dog with no owner, wandering freely (adverb), would
>>> not be called a free dog (adjective), to mean possessing freedom.
>>> Free dog means free as in beer.
>> "I was walking my dog, but he got free of the leash. Now he's running
>> free all over the neighborhood."
>
> Uh, neither of which contains "free dog".
"He ... free"
--
Lew
------------------------------
Date: Sun, 07 Oct 2007 12:37:59 -0400
From: Lew <lew@lewscanon.com>
Subject: Re: The Modernization of Emacs: terminology buffer and keybinding
Message-Id: <j4idnUP3ktX1lpTanZ2dnUVZ_ujinZ2d@comcast.com>
Lew wrote:
> David Kastrup wrote:
>> Lew <lew@lewscanon.com> writes:
>>
>>> lhb@nowhere.com wrote:
>>>> Words are defined by popular usage. In popular usage, the meaning
>>>> of free as an adjective depends on the context. If the adjective is
>>>> applied to people, it means the opposite of slavery or imprisonment.
>>>> If it's applied to something other than people, it means free as in
>>>> beer.
>>> Unless it's applied to open-source software, which by popular usage
>>> has "free" mean "free of restrictions on use."
>>>
>>> Words are also defined by technical usage. Would you claim that
>>> "thread" means only a yarn of fabric?
>>>
>>>> For example, a dog with no owner, wandering freely (adverb), would
>>>> not be called a free dog (adjective), to mean possessing freedom.
>>>> Free dog means free as in beer.
>>> "I was walking my dog, but he got free of the leash. Now he's running
>>> free all over the neighborhood."
>>
>> Uh, neither of which contains "free dog".
>
> "He ... free"
Sigh. It's "free" as an adjective, referring to the dog, thus refuting the
claim that "free" applied to "dog" must mean "free of charge". The claim
isn't limited to just the phrase "free dog" literally, but the application of
the adjective to dogs. I provided a counterexample.
--
Lew
------------------------------
Date: Sun, 07 Oct 2007 12:40:48 -0400
From: Lew <lew@lewscanon.com>
Subject: Re: The Modernization of Emacs: terminology buffer and keybinding
Message-Id: <j4idnUL3ktWNkZTanZ2dnUVZ_ujinZ2d@comcast.com>
Lew wrote:
> Lew wrote:
>> David Kastrup wrote:
>>> Lew <lew@lewscanon.com> writes:
>>>
>>>> lhb@nowhere.com wrote:
>>>>> Words are defined by popular usage. In popular usage, the meaning
>>>>> of free as an adjective depends on the context. If the adjective is
>>>>> applied to people, it means the opposite of slavery or imprisonment.
>>>>> If it's applied to something other than people, it means free as in
>>>>> beer.
>>>> Unless it's applied to open-source software, which by popular usage
>>>> has "free" mean "free of restrictions on use."
>>>>
>>>> Words are also defined by technical usage. Would you claim that
>>>> "thread" means only a yarn of fabric?
>>>>
>>>>> For example, a dog with no owner, wandering freely (adverb), would
>>>>> not be called a free dog (adjective), to mean possessing freedom.
>>>>> Free dog means free as in beer.
>>>> "I was walking my dog, but he got free of the leash. Now he's running
>>>> free all over the neighborhood."
>>>
>>> Uh, neither of which contains "free dog".
>>
>> "He ... free"
>
> Sigh. It's "free" as an adjective, referring to the dog, thus refuting
> the claim that "free" applied to "dog" must mean "free of charge". The
> claim isn't limited to just the phrase "free dog" literally, but the
> application of the adjective to dogs. I provided a counterexample.
But if you want to be so ridiculously anal about it:
"I have a caged dog and one I let wander. My neighbor got mad and shot the
free dog."
There, are you satisfied? Hmm?
--
Lew
------------------------------
Date: 07 Oct 2007 17:30:53 +0000
From: Cor Gest <cor@clsnet.nl>
Subject: Re: The Modernization of Emacs: terminology buffer and keybinding
Message-Id: <87641i4ysy.fsf@cleopatra.clsnet.nl>
Some entity, AKA lhb@nowhere.com,
wrote this mindboggling stuff:
(selectively-snipped-or-not-p)
> For example, a dog with no owner, wandering freely (adverb), would not be
> called a free dog (adjective), to mean possessing freedom. Free dog means
> free as in beer. Likewise, in popular usage, free software means free as
> in beer. People who use it with a different meaning are vainly trying to
> change its meaning. But the meanings of words can't be arbitrarily
> changed, just by dictating different meanings. The meaning has to be
> adopted by popular usage, which free-as-in-GPL software has not been.
>
> Therefore, I propose, using dog freedom as our logic, we call it stray
> software.
Oh Nice, there will be now:
the leashed owner,
the freely roaming dog-tagged owner,
the impounded owner after roaming without a tag,
Do we also get the right to shoot the rabiate ones on sight ?
That realy would clean up some newsgroups.
Cor
--
Alle schraifvauden zijn opzettelijk, teneinde ieder lafaard de kans te
geven over spelling te zeuren in plaats van in te gaan op de inhoud.
(defvar My-Computer '((OS . "GNU/Emacs") (IPL . "GNU/Linux")))
http://www.clsnet.nl/mail.php
------------------------------
Date: Sun, 07 Oct 2007 20:58:37 +0300
From: Giorgos Keramidas <keramida@ceid.upatras.gr>
Subject: Re: The Modernization of Emacs: terminology buffer and keybinding
Message-Id: <87r6k67qnm.fsf@kobe.laptop>
On Sun, 07 Oct 2007 13:07:16 GMT, lhb@nowhere.com wrote:
> Wildemar Wildenburger <lasses_weil@klapptsowieso.net> wrote in
> news:47016899$0$4524$9b4e6d93@newsspool3.arcor-online.net:
>
>> While I agree that the word "free" implies "free of monetary
>> cost" to many people societies, that is by no means set in
>> stone (talk to native americans, blacks, jews, palestinians,
>> etc. about the word free, see what they have to say).
>
> Words are defined by popular usage. In popular usage, the
> meaning of free as an adjective depends on the context. If the
> adjective is applied to people, it means the opposite of
> slavery or imprisonment. If it's applied to something other
> than people, it means free as in beer.
I don't think `free as in beer' has any reasonable meaning, which
is inherent to the word `beer' and universally true, as you seem
to imply by your oft repeated use of it as a very basic and
inalienable truth, upon which we can base all our logic when
discussing `freedom'.
For instance, there is nothing `free of cost' about beer where I
currently live. A person who feels like enjoying a healthy dose
of beer, is obliged either to *pay* for beer somebody else
prepared and bottled, or *pay* for the cost of the ingredients of
beer *and* spend some time preparing it.
Popular or not, the term `free beer' means exactly _nothing_ if
quoted often and out of any sort of context :(
------------------------------
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 914
**************************************
