[23837] in Perl-Users-Digest

home help back first fref pref prev next nref lref last post

Perl-Users Digest, Issue: 6040 Volume: 10

daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Jan 29 22:07:02 2004

Date: Thu, 29 Jan 2004 19:01:12 -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           Thu, 29 Jan 2004     Volume: 10 Number: 6040

Today's topics:
        print scalar localtime <Rahul@hotmail.com>
    Re: print scalar localtime <notpublic@restricted.com>
    Re: print scalar localtime <krahnj@acm.org>
    Re: print scalar localtime <bernard.el-haginDODGE_THIS@lido-tech.net>
    Re: print scalar localtime <notpublic@restricted.com>
    Re: print scalar localtime ctcgag@hotmail.com
    Re: print scalar localtime <uri@stemsystems.com>
    Re: printf appears to not be working, file size never g <kevin@invalid.com>
    Re: printf appears to not be working, file size never g (Anno Siegel)
    Re: printf appears to not be working, file size never g <tadmc@augustmail.com>
        printing sub results in heredocs <nospam@nospam.net>
    Re: printing sub results in heredocs (Anno Siegel)
    Re: printing sub results in heredocs <uri@stemsystems.com>
    Re: printing sub results in heredocs <nobull@mail.com>
    Re: printing sub results in heredocs <tassilo.parseval@rwth-aachen.de>
    Re: printing sub results in heredocs <bik.mido@tiscalinet.it>
    Re: printing sub results in heredocs <tassilo.parseval@rwth-aachen.de>
    Re: printing sub results in heredocs <nospam@nospam.net>
    Re: printing sub results in heredocs <tassilo.parseval@rwth-aachen.de>
    Re: printing sub results in heredocs <bmb@ginger.libs.uga.edu>
        Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)

----------------------------------------------------------------------

Date: Thu, 29 Jan 2004 15:01:25 GMT
From: "Rahul" <Rahul@hotmail.com>
Subject: print scalar localtime
Message-Id: <9f9Sb.7968$k4.174583@news1.nokia.com>

Hi ,
Sorry if this pisses of someone
But

When I say  "print scalar localtime" I get the result as Thu Jan 29 16:59:52
2004
now if I remove scalar I get 210172901044280.

The result are as expected,

my question is How does adding "Scalar" changes the format of localtime.




------------------------------

Date: Thu, 29 Jan 2004 16:11:38 +0100
From: "kz" <notpublic@restricted.com>
Subject: Re: print scalar localtime
Message-Id: <Hq9Sb.11$eQ2.18286@news.uswest.net>

"Rahul" <Rahul@hotmail.com> wrote in message
news:9f9Sb.7968$k4.174583@news1.nokia.com...
> Hi ,
> Sorry if this pisses of someone
> But
>
> When I say  "print scalar localtime" I get the result as Thu Jan 29
16:59:52
> 2004
> now if I remove scalar I get 210172901044280.
>
> The result are as expected,
>
> my question is How does adding "Scalar" changes the format of localtime.
>
perldoc -f  localtime

<quote>
           In scalar context, "localtime()" returns the ctime(3) value:
           $now_string = localtime;  # e.g., "Thu Oct 13 04:54:34 1994"
</quote>

HTH,

Zoltan




------------------------------

Date: Thu, 29 Jan 2004 15:18:34 GMT
From: "John W. Krahn" <krahnj@acm.org>
Subject: Re: print scalar localtime
Message-Id: <4019243E.5F169A4A@acm.org>

Rahul wrote:
> 
> When I say  "print scalar localtime" I get the result as Thu Jan 29 16:59:52
> 2004
> now if I remove scalar I get 210172901044280.
> 
> The result are as expected,
> 
> my question is How does adding "Scalar" changes the format of localtime.

Because localtime returns a scalar in scalar context and a list in list
context and since print forces a list context you need to insert
"scalar" to force a scalar context.


John
-- 
use Perl;
program
fulfillment


------------------------------

Date: Thu, 29 Jan 2004 16:22:24 +0100
From: Bernard El-Hagin <bernard.el-haginDODGE_THIS@lido-tech.net>
Subject: Re: print scalar localtime
Message-Id: <slrnc1i947.id.bernard.el-haginDODGE_THIS@gdndev25.lido-tech>

On 2004-01-29, Rahul <Rahul@hotmail.com> wrote:
> Hi ,
> Sorry if this pisses of someone
> But
>
> When I say  "print scalar localtime" I get the result as Thu Jan 29 16:59:52
> 2004
> now if I remove scalar I get 210172901044280.
>
> The result are as expected,
>
> my question is How does adding "Scalar" changes the format of localtime.


In the way you described above. Duh.


-- 
Cheers,
Bernard


------------------------------

Date: Thu, 29 Jan 2004 16:49:46 +0100
From: "kz" <notpublic@restricted.com>
Subject: Re: print scalar localtime
Message-Id: <t_9Sb.33$Ex1.11390@news.uswest.net>

"John W. Krahn" <krahnj@acm.org> wrote in message
news:4019243E.5F169A4A@acm.org...

[snip]

> Because localtime returns a scalar in scalar context and a list in list
> context and since print forces a list context you need to insert
> "scalar" to force a scalar context.

John,

Is "ref" THE (best) way to check the context of an expression, like this:

if (ref($r) eq "sometype") {
                    print "r is a reference to sometype.\n";
}

Regards,

Zoltan




------------------------------

Date: 29 Jan 2004 16:36:14 GMT
From: ctcgag@hotmail.com
Subject: Re: print scalar localtime
Message-Id: <20040129113614.451$E0@newsreader.com>

"Rahul" <Rahul@hotmail.com> wrote:
> Hi ,
> Sorry if this pisses of someone
> But
>
> When I say  "print scalar localtime" I get the result as Thu Jan 29
> 16:59:52 2004
> now if I remove scalar I get 210172901044280.
>
> The result are as expected,
>
> my question is How does adding "Scalar" changes the format of localtime.

Through wantarray, or some internal equivalent of it.

Xho

-- 
-------------------- http://NewsReader.Com/ --------------------
Usenet Newsgroup Service              New Rate! $9.95/Month 50GB


------------------------------

Date: Thu, 29 Jan 2004 18:26:34 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: print scalar localtime
Message-Id: <x765euy5k6.fsf@mail.sysarch.com>

>>>>> "k" == kz  <notpublic@restricted.com> writes:

  k> "John W. Krahn" <krahnj@acm.org> wrote in message
  k> news:4019243E.5F169A4A@acm.org...

  >> Because localtime returns a scalar in scalar context and a list in list
  >> context and since print forces a list context you need to insert
  >> "scalar" to force a scalar context.

  k> Is "ref" THE (best) way to check the context of an expression, like this:

  k> if (ref($r) eq "sometype") {
  k>                     print "r is a reference to sometype.\n";
  k> }

huh? where is the context checked there? do you have a basic
understanding of list vs scalar context? the code AROUND or NEAR an
expression provides the context, not the expression itself. you can't
directly check the context inside an expression but you don't need to,
you just look at the code and you can see what context is provided. but
there is a way to do so inside a sub and that is with wantarray.

uri

-- 
Uri Guttman  ------  uri@stemsystems.com  -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs  ----------------------------  http://jobs.perl.org


------------------------------

Date: Thu, 22 Jan 2004 05:06:32 GMT
From: kevin <kevin@invalid.com>
Subject: Re: printf appears to not be working, file size never grows
Message-Id: <sTIPb.6551$6o4.465@fe2.texas.rr.com>

kevin wrote:
> what i have done here is started writing to the filehandle TFILE, which 
> does exist and is not locked.  i have experiment with the file 
> permissions to make sure that when i open for write it fails with read 
> only permisions and vice versa. (linux)
> 
> i am trying to save the start location with the tell to use later in the 
> program.  the hash table contains all zeros, as if i am continually 
> re-opening or writing nothing to the file.  i have used a debugger and 
> have checked that i do not erronously find the 'close TFILE' line in the 
> program while in this loop.
> 
>
it turns out that i didn't close the file within the loop but before i started the loop.  i wasn't 
continually closing the file and re-opening.

after i closed it for write i, to flush the buffers, it immediately opened it for read.

i am a bit suprised that it/perl never complained about writing to a file opened for read only. it 
just wouldn't write the info

thanks to those who took the time to view this and respond..






------------------------------

Date: 22 Jan 2004 08:57:57 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: printf appears to not be working, file size never grows
Message-Id: <buo3al$38p$1@mamenchi.zrz.TU-Berlin.DE>

kevin  <kevin@invalid.com> wrote in comp.lang.perl.misc:

[...]

> i am a bit suprised that it/perl never complained about writing to a
> file opened for read only. it 
> just wouldn't write the info

It would have warned you, but you didn't ask it to.  Switch on warnings
in all non-trivial programs.  A program that's giving you trouble isn't
trivial.

Anno


------------------------------

Date: Thu, 22 Jan 2004 07:56:24 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: printf appears to not be working, file size never grows
Message-Id: <slrnc0vlk8.9hb.tadmc@magna.augustmail.com>


[ Please limit your line lengths to the conventional 70-72 characters ]


kevin <kevin@invalid.com> wrote:

> i am a bit suprised that it/perl never complained about writing 
> to a file opened for read only. 


You should always enable warnings when developing Perl code.


-- 
    Tad McClellan                          SGML consulting
    tadmc@augustmail.com                   Perl programming
    Fort Worth, Texas


------------------------------

Date: Mon, 26 Jan 2004 18:09:56 GMT
From: "Jeff Thies" <nospam@nospam.net>
Subject: printing sub results in heredocs
Message-Id: <UJcRb.27537$q4.3557@newsread3.news.atl.earthlink.net>

Seems like I'm always printing heredocs with breaks for CGI subs:

print <<thishtml;

some html and then have to end the heredoc for CGI method

thishtml

print $query->some_method(...);

print <<thishtml; ...

Is there another way to do this? To get the methods to execute?

Looking at this  now I guess this would be better:

my $cgi_popup1=$query->popup_menu(properties...);
my $cgi_popup2=$query->popup_menu(properties...);

print <<thishtml;

html here

$cgi_popup1

more html

$cgi_popup2
 ....

  Jeff




------------------------------

Date: 26 Jan 2004 19:48:51 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: printing sub results in heredocs
Message-Id: <bv3qv3$e8j$3@mamenchi.zrz.TU-Berlin.DE>

Jeff Thies <nospam@nospam.net> wrote in comp.lang.perl.misc:
> Seems like I'm always printing heredocs with breaks for CGI subs:
> 
> print <<thishtml;
> 
> some html and then have to end the heredoc for CGI method
> 
> thishtml
> 
> print $query->some_method(...);
> 
> print <<thishtml; ...
> 
> Is there another way to do this? To get the methods to execute?
> 
> Looking at this  now I guess this would be better:
> 
> my $cgi_popup1=$query->popup_menu(properties...);
> my $cgi_popup2=$query->popup_menu(properties...);
> 
> print <<thishtml;
> 
> html here
> 
> $cgi_popup1
> 
> more html
> 
> $cgi_popup2
> ....

Indeed, this would be the preferred method.  Just assign them to temporary
variables, or even a hash if there are many.

The "standard method" of forcing code evaluation during interpolation is
"string here @{[ $query->popup_menu(properties...)]} more string".  It
works as well in here-docs, but it's rarely appropriate.

Anno


------------------------------

Date: Mon, 26 Jan 2004 20:01:20 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: printing sub results in heredocs
Message-Id: <x7smi2a38w.fsf@mail.sysarch.com>

>>>>> "AS" == Anno Siegel <anno4000@lublin.zrz.tu-berlin.de> writes:

  AS> Indeed, this would be the preferred method.  Just assign them to
  AS> temporary variables, or even a hash if there are many.

i agree with this. much cleaner to use temp vars or a hash and then use
a here doc. this follows my rule of print rarely, print late. print is
slow and should be done rarely. also it is best done when all the text
is ready in one var for printing. then you can also control where it
gets printed or returned to a higher level caller.

  AS> The "standard method" of forcing code evaluation during interpolation is
  AS> "string here @{[ $query->popup_menu(properties...)]} more string".  It
  AS> works as well in here-docs, but it's rarely appropriate.

nice trick but i never use it in production code. faking a ref and
dereferencing it is too fugly IMO. there is an Interpolate module that
does more of this. perl6 will have a proper $() and @() way to
interpolate expressions.

uri

-- 
Uri Guttman  ------  uri@stemsystems.com  -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs  ----------------------------  http://jobs.perl.org


------------------------------

Date: 27 Jan 2004 09:13:44 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: printing sub results in heredocs
Message-Id: <u91xpl7nzr.fsf@wcl-l.bham.ac.uk>

Uri Guttman <uri@stemsystems.com> writes:

> >>>>> "AS" == Anno Siegel <anno4000@lublin.zrz.tu-berlin.de> writes:
> 
>   AS> Indeed, this would be the preferred method.  Just assign them to
>   AS> temporary variables, or even a hash if there are many.
> 
> i agree with this. much cleaner to use temp vars or a hash and then use
> a here doc. this follows my rule of print rarely, print late. print is
> slow and should be done rarely. also it is best done when all the text
> is ready in one var for printing. then you can also control where it
> gets printed or returned to a higher level caller.
> 
>   AS> The "standard method" of forcing code evaluation during interpolation is
>   AS> "string here @{[ $query->popup_menu(properties...)]} more string".  It
>   AS> works as well in here-docs, but it's rarely appropriate.
> 
> nice trick but i never use it in production code. faking a ref and
> dereferencing it is too fugly IMO.

I disagree.  It looks quite tidy.  Yeah, it creates a temporary
anonymous variable - but the alternative is to use a nonymous
temporary variable.  The aim should be to maximise readability.  When
an expression becomes to complex to take in the overall structure in a
glance it is time to split it into simpler expressions and use some
temporary variables.  This applies to all expressions not just ones
expressed in interplotative syntax.

Once again I say, do not completely reject a technique just because it
can lead to incomprehensible code when abused.  Just don't abuse
it. So for a non-trivial expression I'd say use a named temporary
variable and for a trivial one in-line it with @{[]}.

my $text = <<EOT;
[ dozens of lines ] 
Number of things: @{[ scalar @foo ]}
EOT

my $n_foo = @foo; # And dozens of similar assignments
my $text = <<EOT;
[ dozens of lines ] 
Number of things: $n_foo
EOT

> perl6 will have a proper $() and @() way to interpolate expressions.

IMHO this doesn't change the arguments much.  If @(EXPR) is readable
then so is @{[EXPR]}.

-- 
     \\   ( )
  .  _\\__[oo
 .__/  \\ /\@
 .  l___\\
  # ll  l\\
 ###LL  LL\\


------------------------------

Date: 27 Jan 2004 09:30:34 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: printing sub results in heredocs
Message-Id: <bv5b3q$bas$1@nets3.rz.RWTH-Aachen.DE>

Also sprach Brian McCauley:

> Uri Guttman <uri@stemsystems.com> writes:
> 
>> >>>>> "AS" == Anno Siegel <anno4000@lublin.zrz.tu-berlin.de> writes:

>>   AS> The "standard method" of forcing code evaluation during interpolation is
>>   AS> "string here @{[ $query->popup_menu(properties...)]} more string".  It
>>   AS> works as well in here-docs, but it's rarely appropriate.
>> 
>> nice trick but i never use it in production code. faking a ref and
>> dereferencing it is too fugly IMO.
> 
> I disagree.  It looks quite tidy.  Yeah, it creates a temporary
> anonymous variable - but the alternative is to use a nonymous
> temporary variable.  The aim should be to maximise readability.  When
> an expression becomes to complex to take in the overall structure in a
> glance it is time to split it into simpler expressions and use some
> temporary variables.  This applies to all expressions not just ones
> expressed in interplotative syntax.

I remember once writing a few CGI-scripts where I used this technique
almost exclusively. The CGI-scripts were mainly just a huge here-doc
with the dynamic part put into @{[]}. That way I had an extremely cheap
way of mimicking PHP's way of inline code into HTML. Using temporary
variables for that would have made the whole thing in fact less readable
and more awkward.

Tassilo
-- 
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval


------------------------------

Date: Thu, 29 Jan 2004 21:17:26 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: printing sub results in heredocs
Message-Id: <u2qi105d00dfukit99641gu878ipjqgtl3@4ax.com>

On 27 Jan 2004 09:13:44 +0000, Brian McCauley <nobull@mail.com> wrote:

>Once again I say, do not completely reject a technique just because it
>can lead to incomprehensible code when abused.  Just don't abuse
>it. So for a non-trivial expression I'd say use a named temporary
>variable and for a trivial one in-line it with @{[]}.

It has not been mentioned yet, so for completeness it may be worth to
let the OP know that, since scalars are interpolated as well (and IMHO
more frequently in actual code than arrays),

  perl -le 'print "There are ${\(1+1)} WTDI!"'
                   ^^^^^^^^^^^^^^^^^^^^^^^^^


Michele
-- 
you'll see that it shouldn't be so. AND, the writting as usuall is
fantastic incompetent. To illustrate, i quote:
- Xah Lee trolling on clpmisc,
  "perl bug File::Basename and Perl's nature"


------------------------------

Date: 28 Jan 2004 23:05:42 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: printing sub results in heredocs
Message-Id: <bv9f86$75a$1@nets3.rz.RWTH-Aachen.DE>

Also sprach Michele Dondi:

> On 27 Jan 2004 09:13:44 +0000, Brian McCauley <nobull@mail.com> wrote:
> 
>>Once again I say, do not completely reject a technique just because it
>>can lead to incomprehensible code when abused.  Just don't abuse
>>it. So for a non-trivial expression I'd say use a named temporary
>>variable and for a trivial one in-line it with @{[]}.
> 
> It has not been mentioned yet, so for completeness it may be worth to
> let the OP know that, since scalars are interpolated as well (and IMHO
> more frequently in actual code than arrays),
> 
>   perl -le 'print "There are ${\(1+1)} WTDI!"'
>                    ^^^^^^^^^^^^^^^^^^^^^^^^^

Only that you shouldn't assume that this always does what you expect
(namely providing scalar context because it doesn't):

    print "${ \localtime }\n";
    __END__
    0

Ever since I realized that, I never used ${\CODE} because @{[]} does at
least what you would expect.

Tassilo
-- 
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval


------------------------------

Date: Thu, 29 Jan 2004 07:32:07 GMT
From: "Jeff Thies" <nospam@nospam.net>
Subject: Re: printing sub results in heredocs
Message-Id: <XF2Sb.1082$jH6.1055@newsread1.news.atl.earthlink.net>

> Ever since I realized that, I never used ${\CODE} because @{[]} does at
> least what you would expect.

Why does it do that? It looks like an array dereference to an anonymous
array that has one element. I don't know why that would interpret the code
and am unsure of the need for the brackets.

  Jeff





------------------------------

Date: 29 Jan 2004 09:17:03 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: printing sub results in heredocs
Message-Id: <bvaj2f$e8g$1@nets3.rz.RWTH-Aachen.DE>

Also sprach Jeff Thies:

>> Ever since I realized that, I never used ${\CODE} because @{[]} does at
>> least what you would expect.
> 
> Why does it do that? It looks like an array dereference to an anonymous
> array that has one element. I don't know why that would interpret the code
> and am unsure of the need for the brackets.

The reason is that perl interpolates @arrays and $scalars in
double-quotish strings. You have to trick perl into thinking that there
is actually such an array or a string.

Consider this:

    my $ary_ref = [ qw/a b c/ ];
    print "@$ary_ref\n";

You are probably not surprised that perl will interpolate 'a b c' into
the string. Since

    @$ary_ref

is just a shortcut for

    @{ $ary_ref };

you can also write:

    print "@{ $ary_ref }\n";

Now we already have @{ ... }, where the three dots have to be an
array-reference. References can also be anonymous:

    my @array = @{ [1, 2, 3] };

This first creates an anonymous reference to an array ( [1, 2, 3] ) and
then immediately dereferences it (@{ $ANON_REF }).

In short: The brackets create a reference to an array. The array
contains whatever the code inside the brackets return. In particular,
they can also contain just one element. Here's an ultra-stupid way of
embedding a literal string inside another string:

    print "@{ [ 'literal string' ] }\n";

Tassilo
-- 
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval


------------------------------

Date: Thu, 29 Jan 2004 17:28:18 -0500
From: Brad Baxter <bmb@ginger.libs.uga.edu>
Subject: Re: printing sub results in heredocs
Message-Id: <Pine.A41.4.58.0401291714520.30816@ginger.libs.uga.edu>

On Wed, 28 Jan 2004, Tassilo v. Parseval wrote:

> Also sprach Michele Dondi:
> > It has not been mentioned yet, so for completeness it may be worth to
> > let the OP know that, since scalars are interpolated as well (and IMHO
> > more frequently in actual code than arrays),
> >
> >   perl -le 'print "There are ${\(1+1)} WTDI!"'
> >                    ^^^^^^^^^^^^^^^^^^^^^^^^^

> Only that you shouldn't assume that this always does what you expect
> (namely providing scalar context because it doesn't):
>
>     print "${ \localtime }\n";
>     __END__
>     0
>
> Ever since I realized that, I never used ${\CODE} because @{[]} does at
> least what you would expect.

Interesting ...

sub context {
    print <<"--";
@_:\tgot @{[wantarray?"list":defined wantarray?"scalar":"null"]}
--
    ''
}
                context 'Expect null';
my $x =         context 'Expect scalar';
( $x ) =        context 'Expect list';
$x = "@{[       context 'Expect list'    ]}";
$x = "@{[scalar context 'Expect scalar'  ]}";
$x = "${\       context 'Expect scalar?' }";
$x = "${\scalar context 'Expect scalar'  }";

__END__
Expect null:    got null
Expect scalar:  got scalar
Expect list:    got list
Expect list:    got list
Expect scalar:  got scalar
Expect scalar?: got list
Expect scalar:  got scalar


Regards,

Brad


------------------------------

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 V10 Issue 6040
***************************************


home help back first fref pref prev next nref lref last post