[28970] in Perl-Users-Digest

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

Perl-Users Digest, Issue: 214 Volume: 11

daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Sun Mar 11 00:10:02 2007

Date: Sat, 10 Mar 2007 21:09:05 -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           Sat, 10 Mar 2007     Volume: 11 Number: 214

Today's topics:
    Re: Convert IEEE single from integer representation <1usa@llenroc.ude.invalid>
        drugs <whoami@whereami.net>
    Re: Dumping Perl tie hash file <bik.mido@tiscalinet.it>
    Re: Dumping Perl tie hash file <DJStunks@gmail.com>
        invoking system commands from a perl script <vaibhav.aparimit@gmail.com>
    Re: invoking system commands from a perl script anno4000@radom.zrz.tu-berlin.de
    Re: invoking system commands from a perl script <someone@example.com>
    Re: invoking system commands from a perl script <jurgenex@hotmail.com>
    Re: invoking system commands from a perl script <rvtol+news@isolution.nl>
    Re: problem cgi <RedGrittyBrick@SpamWeary.foo>
    Re: problem cgi <RedGrittyBrick@SpamWeary.foo>
    Re: problem cgi anno4000@radom.zrz.tu-berlin.de
    Re: problem cgi <1usa@llenroc.ude.invalid>
    Re: Q on regex of LWP::Simple data <rvtol+news@isolution.nl>
    Re: Reading from a serial port (DF4OR)
    Re: Sending an incomplete file? anno4000@radom.zrz.tu-berlin.de
    Re: Sending an incomplete file? <bart.lateur@pandora.be>
        why doesn't this argument list need a comma after the 1 <evad.notyals@liamg.moc>
    Re: why doesn't this argument list need a comma after t <ben@morrow.me.uk>
        Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)

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

Date: Sat, 10 Mar 2007 23:18:14 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Convert IEEE single from integer representation
Message-Id: <Xns98EFBA3051F7Dasu1cornelledu@127.0.0.1>

Ilya Zakharevich <nospam-abuse@ilyaz.org> wrote in
news:esu72k$2i7$1@agate.berkeley.edu: 

> [A complimentary Cc of this posting was sent to
> A. Sinan Unur
> <1usa@llenroc.ude.invalid>], who wrote in article
> <Xns98EF717D7F9Dasu1cornelledu@127.0.0.1>: 
>> Well, this certainly does help (at least in those cases where I can 
>> assume the platform's internal format for representing floats matches
>> the IEEE format).
> 
> Keep in mind that there is no such thing as "an IEEE format".  IEEE
> requires a certain *semantic* of floats, not a particular way of
> binary representation.  However, IIRC, all but 2 architechtures use
> one of two representations, related to each other as V is to N
> (pack-parlance).

I was using the word 'format' not to refer to the way they were stored 
on disk but rather what the bits mean once you have it in the 
appropriate int. Thank you for the clarification.

Would you mind posting/letting me know which two architectures you are 
referring to above?

Thank you.

Sinan

-- 
A. Sinan Unur <1usa@llenroc.ude.invalid>
(remove .invalid and reverse each component for email address)
clpmisc guidelines: <URL:http://www.augustmail.com/~tadmc/clpmisc.shtml>



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

Date: Sat, 10 Mar 2007 16:08:22 -0000
From: "IanW" <whoami@whereami.net>
Subject: drugs
Message-Id: <45f2deba.0@entanet>

really interesting article on drugs:
http://www.biopsychiatry.com/ 




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

Date: Sat, 10 Mar 2007 15:18:46 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Dumping Perl tie hash file
Message-Id: <6ff5v2pj2an2kipst8rgqokcc3d07nvl7b@4ax.com>

On 9 Mar 2007 14:44:26 -0800, "Eric" <ecarlson@vmware.com> wrote:

>Thanks for your response, Michele. I have in fact tried Data::Dumper,
>but with limited success. Not sure what XML::Simple could do for me
>here. I've never heard of YAML::Syck, but I'll look into it.

AIUI you were not really needing to tie() but just wanting to dump to
human readable format. I may have got that wrong. In fact you "specs"
were somewhat hard to follow.


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: 10 Mar 2007 10:37:16 -0800
From: "DJ Stunks" <DJStunks@gmail.com>
Subject: Re: Dumping Perl tie hash file
Message-Id: <1173551836.312517.58630@n33g2000cwc.googlegroups.com>

On Mar 9, 12:28 pm, "Eric" <ecarl...@vmware.com> wrote:
> Hello,
>
> This is a repost of sorts. The code below is putting the info in a
> file, $mountsDBFile, but it's doing so in binary. The file has to be
> humanly readable.

The question is what your definition of "humanly readable" is - do you
mean you have to be able to use more/less/cat to view it?  If so,
why?  If you allow yourself to use some other tool to read the file,
and you get sensible output out the other side then it doesn't matter
if the file itself is "humanly readable" only that this tool can read
it and let you know what the file contains.

> I got a couple of responses on this. Someone responded and said that
> there are tools to translate the file, or I can write a Perl script to
> run on the file. (I'm assuming they meant post processing of the
> file.) I made desperate attempts to do the latter, but with no
> success.
>
> Does anyone know of any tools to do this, or how I would write a
> script to interpret this file in humanly readable text?

I believe that there are binary tools to read/write/edit DBM files
directly.  However, like I mentioned before, it's pretty
straightforward to do it in Perl - in fact you're already doing it.
You just need to reverse the process - tie a hash to the file then
print out the hash.

here's a Perl one-liner which does just that:

  jpeavy1@localhost:~/etc> /usr/bin/perl -MDB_File -MData::Dumper -e '
  tie %_,"DB_File",shift or die $!;
  print Dumper \%_
  ' dbm_file.dat

  $VAR1 = {
            'key1' => 'A',
            'key11' => 'B',
            'key111' => 'B',
            'key2' => 'A'
          };

-jp



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

Date: 10 Mar 2007 07:47:18 -0800
From: "vabby" <vaibhav.aparimit@gmail.com>
Subject: invoking system commands from a perl script
Message-Id: <1173541638.045282.57670@c51g2000cwc.googlegroups.com>

Hi
I want to know what is the diff b/w the following two ways of invoking
system commands from a perl script:
1) system(" rm abc.txt");
2)`rm abc.txt';

also of I mix and match the two styles, will i land into trouble, eg
if i have to create a file and in the next step delete it, which one
of the two ways will land me into trouble:
1)
system ("touch abc.txt");
'rm abc.txt';

or
2)

`touch abc.txt`;
system("abc.txt");



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

Date: 10 Mar 2007 16:46:53 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: invoking system commands from a perl script
Message-Id: <55g5ntF223q5qU1@mid.dfncis.de>

vabby <vaibhav.aparimit@gmail.com> wrote in comp.lang.perl.misc:
> Hi
> I want to know what is the diff b/w the following two ways of invoking
> system commands from a perl script:
> 1) system(" rm abc.txt");
> 2)`rm abc.txt';

Read "perldoc system" and the section about "qx" in "perldoc perlop".
The relationship is discussed in these documents.

> also of I mix and match the two styles, will i land into trouble, eg
> if i have to create a file and in the next step delete it, which one
> of the two ways will land me into trouble:
> 1)
> system ("touch abc.txt");
> 'rm abc.txt';
> 
> or
> 2)
> 
> `touch abc.txt`;
> system("abc.txt");

None of these will necessarily land you in trouble, except with Perl
stylists.  Using `` in void context is always bad style.

Anno


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

Date: Sat, 10 Mar 2007 16:54:17 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: invoking system commands from a perl script
Message-Id: <ZoBIh.64823$cE3.9536@edtnps89>

vabby wrote:
> 
> I want to know what is the diff b/w the following two ways of invoking
> system commands from a perl script:
> 1) system(" rm abc.txt");

perldoc -f system

> 2)`rm abc.txt';

perldoc -f qx


> also of I mix and match the two styles, will i land into trouble, eg
> if i have to create a file and in the next step delete it, which one
> of the two ways will land me into trouble:
> 1)
> system ("touch abc.txt");
> 'rm abc.txt';
> 
> or
> 2)
> 
> `touch abc.txt`;
> system("abc.txt");

How about using perl to do it (this is after all a Perl group.)

open my $fh, '>', 'abc.txt' or die "Cannot open 'abc.txt' $!";
close $fh                   or die "Cannot close 'abc.txt' $!";

unlink 'abc.txt'            or die "Cannot unlink 'abc.txt' $!";




John
-- 
Perl isn't a toolbox, but a small machine shop where you can special-order
certain sorts of tools at low cost and in short order.       -- Larry Wall


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

Date: Sat, 10 Mar 2007 18:05:24 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: invoking system commands from a perl script
Message-Id: <ErCIh.723$vV3.337@trndny09>

vabby wrote:
> I want to know what is the diff b/w the following two ways of invoking
> system commands from a perl script:
> 1) system(" rm abc.txt");
> 2)`rm abc.txt';

See the readily available documentation for each command:
    perldoc -f system
    perldoc -f perlop (and see the section about quotes and quote-like 
operators)

> also of I mix and match the two styles,

Those are not different styles. Those are two different commands that simply 
do different things.

> will i land into trouble, eg
> if i have to create a file and in the next step delete it, which one
> of the two ways will land me into trouble:

It's like asking if you can mix multiplication and addition in the same Perl 
program.
They just do different things. Choose the one that is the right for your 
task.

> system ("touch abc.txt");

You should check if your call to system was successful.

> 'rm abc.txt';

I suppose you mean
     `rm abc.txt`;
What output do you expect from the rm(1) command? Why are you asking for the 
output if you don't capture it?

jue 




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

Date: Sat, 10 Mar 2007 20:58:45 +0100
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: invoking system commands from a perl script
Message-Id: <esv69e.1k8.1@news.isolution.nl>

anno4000@radom.zrz.tu-berlin.de schreef:

> Read "perldoc system"

ITYM: perldoc -f system 
or:   perldoc -q system 

-- 
Affijn, Ruud

"Gewoon is een tijger."


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

Date: Sat, 10 Mar 2007 19:59:11 +0000
From: RedGrittyBrick <RedGrittyBrick@SpamWeary.foo>
Subject: Re: problem cgi
Message-Id: <tPKdnXq1Y4aRk27YRVnyjgA@bt.com>

john.swilting wrote:
> I continue my order for the site of sale of paintings for my friend
> I already posted several questions about the cgi one has to bring aide.i to
> me seeks to apply the councils that one me a gives
> I do not post the totality of the script.I post only what does not go
> I obtain the following error
> Unrecognized character \xC2 at /var/www/cgi-bin/vente0.02.cgi line 15.
> 
> my code:
> #!/usr/bin/perl -w
> use diagnostics;
> use strict;
> use CGI qw(:standard escapeHTML);
> use CGI::Carp qw(fatalsToBrowser);
> 
> my %params;
> my $cgi;
> 
> $cgi = new CGI;
> %params = $cgi->Vars;
> 
> print header,start_html('Commande'),h1('Bon de Commande'),start_form;
> 
>      for my $key (sort keys %params) {
>        print "The value for $key is '$params{$key}'\n",br;

I'd remove the ",br". It looks like a mistake to me.

> ##it is in thispart there that there is the problem but I cannot find it
>      }
> 
> print submit,end_form,end_html;
> 


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

Date: Sat, 10 Mar 2007 20:09:20 +0000
From: RedGrittyBrick <RedGrittyBrick@SpamWeary.foo>
Subject: Re: problem cgi
Message-Id: <16CdnWTaoMrxjW7YRVnyhAA@bt.com>

RedGrittyBrick wrote:
> john.swilting wrote:
>> I continue my order for the site of sale of paintings for my friend
>> I already posted several questions about the cgi one has to bring 
>> aide.i to
>> me seeks to apply the councils that one me a gives
>> I do not post the totality of the script.I post only what does not go
>> I obtain the following error
>> Unrecognized character \xC2 at /var/www/cgi-bin/vente0.02.cgi line 15.
>>
>> my code:
>> #!/usr/bin/perl -w
>> use diagnostics;
>> use strict;
>> use CGI qw(:standard escapeHTML);
>> use CGI::Carp qw(fatalsToBrowser);
>>
>> my %params;
>> my $cgi;
>>
>> $cgi = new CGI;
>> %params = $cgi->Vars;
>>
>> print header,start_html('Commande'),h1('Bon de Commande'),start_form;
>>
>>      for my $key (sort keys %params) {
>>        print "The value for $key is '$params{$key}'\n",br;
> 
> I'd remove the ",br". It looks like a mistake to me.
> 
>> ##it is in thispart there that there is the problem but I cannot find it
>>      }
>>
>> print submit,end_form,end_html;
>>

Oops, forget that, I missed the "use CGI".


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

Date: 10 Mar 2007 21:31:29 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: problem cgi
Message-Id: <55gmdhF23ur54U1@mid.dfncis.de>

john.swilting <john.swilting@wanadoo.fr> wrote in comp.lang.perl.misc:
> I continue my order for the site of sale of paintings for my friend
> I already posted several questions about the cgi one has to bring aide.i to
> me seeks to apply the councils that one me a gives

Your postings are hard to follow.  I suppose they are babelfish
translations from French.  That is insufficient, you can't communicate
about technical problems that way.  I suppose that is why you postings
hardly receive an echo.  Maybe fr.comp.lang.perl is worth a try?

> I do not post the totality of the script.I post only what does not go
> I obtain the following error
> Unrecognized character \xC2 at /var/www/cgi-bin/vente0.02.cgi line 15.
> 
> my code:
> #!/usr/bin/perl -w
> use diagnostics;
> use strict;
> use CGI qw(:standard escapeHTML);
> use CGI::Carp qw(fatalsToBrowser);
> 
> my %params;
> my $cgi;
> 
> $cgi = new CGI;
> %params = $cgi->Vars;
> 
> print header,start_html('Commande'),h1('Bon de Commande'),start_form;

The next two line start with non-printable characters...

>      for my $key (sort keys %params) {
>        print "The value for $key is '$params{$key}'\n",br;
> ##it is in thispart there that there is the problem but I cannot find it

 ...as does the next one.

>      }
> 
> print submit,end_form,end_html;

The indicated lines in your code contain characters at their beginning
that don't belong there.  Whatever they are in your original source,
try to delete them.

Anno


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

Date: Sat, 10 Mar 2007 22:46:49 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: problem cgi
Message-Id: <Xns98EFB4E0FCCF3asu1cornelledu@127.0.0.1>

anno4000@radom.zrz.tu-berlin.de wrote in
news:55gmdhF23ur54U1@mid.dfncis.de: 

> john.swilting <john.swilting@wanadoo.fr> wrote in comp.lang.perl.misc:
>> I continue my order for the site of sale of paintings for my friend
>> I already posted several questions about the cgi one has to bring
>> aide.i to me seeks to apply the councils that one me a gives
> 
> Your postings are hard to follow.  I suppose they are babelfish
> translations from French.  That is insufficient, you can't communicate
> about technical problems that way.  I suppose that is why you postings
> hardly receive an echo.  Maybe fr.comp.lang.perl is worth a try?

Well, it is worth checking out his adventures there, if only for a chuckle.

http://groups.google.com/group/fr.comp.lang.perl/msg/dad78040e17b16c7?dmode=source

Sinan

-- 
A. Sinan Unur <1usa@llenroc.ude.invalid>
(remove .invalid and reverse each component for email address)

comp.lang.perl.misc guidelines on the WWW:
http://augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html



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

Date: Sun, 11 Mar 2007 05:10:24 +0100
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: Q on regex of LWP::Simple data
Message-Id: <et035h.1pc.1@news.isolution.nl>

gf schreef:


> [HTML]
> You can get closer to what the browser is doing by stripping all the
> line-end characters from the document, 

Better replace them by a space, or some things will run together. 
It can still do damage, like inside <pre> </pre>. 

-- 
Affijn, Ruud

"Gewoon is een tijger."


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

Date: Sat, 10 Mar 2007 16:49:55 +0100
From: "Ekki Plicht (DF4OR)" <df4or@web.de>
Subject: Re: Reading from a serial port
Message-Id: <esuk33$1as$00$1@news.t-online.com>

michal.golunski@gmail.com wrote:

> How can I read data from a serial port under Perl + Linux? I tried to
> use Device::SerialPort but constructor isn't working for me, and when
> i tried to run it as a root there was a getattr error.

Device::Serialport works nicely and is probably the easiest method to use
the serial port with Perl (and portable to Win32). I would go and find out
the problem with it instead of looking for other, probably more difficult
and less portable solutions.

Here on my box, the serial ports have the owner root:tty, so maybe your user
is not a member of the tty group and therefore cannot access /dev/ttyS* ?

Here is how I use Device::Serialport:
sub init_serial(@) {
# in: devicename, baudrate
# out: nothing
# opens serial device if possible
  my ($dev, $baud) = @_;
  my @items = split "/", $dev;
  my $lockdevice = splice (@items,-1);
  defined($lockdevice)  || die 'failed extracting serial device\n';
  $lockdevice = '/var/lock/LCK..' . $lockdevice;

  # Change: Under Gentoo creating the lockfile suddenly takes 2 seconds
  # (sleep defined in Device::Serialport)
  # Under SuSE this sleep, implemented as nanosleep in Device::Serialport, 
  # did not happen like this.
  # So I don't use device locking currently...
  #$ser = Device::SerialPort->new ($dev, 0, $lockdevice)  
  #     || die "Can\'t lock and open $dev: $!";
  $ser = Device::SerialPort->new ($dev, 0, '')  
        or die "Can\'t open $dev: $!";
  $ser->baudrate($baud) || die 'fail setting baudrate, try -b option';
  $ser->parity("none")  || die 'fail setting parity to none';
  $ser->databits(8)     || die 'fail setting databits to 8';
  $ser->stopbits(1)     || die 'fail setting stopbits to 1';
  $ser->handshake("none")  || die 'fail setting handshake to none';
  $ser->datatype('raw') || die 'fail setting datatype raw';
  $ser->write_settings  || die 'could not write settings';
  $ser->error_msg(1);   # use built-in error messages
  $ser->user_msg(1); 
  # important for nice behaviour, otherwise hogs cpu
  $ser->read_const_time(100); 
  $ser->read_char_time(100);              # dto.
};


> So are there any other methods to connect to serial port, set
> databits, parity and so on and transfer data?

open(), close(), select(), ioctl() etc.
and maybe with setserial in the shell.

Regards,
Ekki



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

Date: 10 Mar 2007 21:35:49 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: Sending an incomplete file?
Message-Id: <55gmllF23ur54U2@mid.dfncis.de>

Tad McClellan  <tadmc@augustmail.com> wrote in comp.lang.perl.misc:

> If it always happens, then it cannot also be bizarre.  :-)

Are you saying everyday life is not bizarre? :)

Anno


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

Date: Sat, 10 Mar 2007 22:50:41 GMT
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: Sending an incomplete file?
Message-Id: <g6d6v2de3d8dotskgpi5qcp2k1he0ujbrk@4ax.com>

burak@stolenradio.com wrote:

>print "Content-type: application/octet-stream\n\n";
>open (FILE, "<foo.bar");
>binmode(FILE);
>print <FILE>;
>close (FILE);
 ...
>Let's say I have some perl code to generate a very large binary file,
>hundreds of megabytes or so.

Uh oh... Do you know that your code tries to fully load the file in
memory (some people have even claimed "several times") before sending it
out to the browser?

Don't do that. Try sending it in chunks instead: read a block of bytes
of a reasonable size, and send it out, and then read the next block...
in a loop.

You can reorganize your code so it uses read or sysread, or you can use
a trick: set $/ to a reference to an integer value, and <> will read in
blocks of that size instead of trying to load an "entire line", whatever
that may mean (the latter could, again, be the entire file)

	local $/ = \10240 ;  # 10 k blocks
	while(<FILE>) {
	    print;
	}

Of course, you still have to take care of the nitty gritty, opening the
file and using binmode (don't forget to binmode STDOUT too). But for the
rest, that's all there is to it.

-- 
	Bart.


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

Date: Sat, 10 Mar 2007 20:00:45 -0700
From: "Dave Slayton" <evad.notyals@liamg.moc>
Subject: why doesn't this argument list need a comma after the 1st argument?
Message-Id: <jcadnRsbutBH7W7YnZ2dnUVZ_qKqnZ2d@comcast.com>

Sorry, another newbie question:

I'm reading this very interesting book on Perl (Effective Perl Programming 
by Joseph N. Hall with Randal L. Schwartz), and here on page 110 there's an 
example of a
call to a (prototyped) subroutine that requires 3 arguments:  a coderef, a 
scalar, and an array, and here's the call:

   for_n {print "$_[0], $_[1]\n"} 2, @a;

I understand the parentheses around the list of arguments are optional, and 
that the anonymous subroutine does not require the "sub" keyword, but what I 
don't understand is how the call gets away with not having a comma after the 
closing curly brace and before the 2.  Can anyone shed some light on this 
for me? 




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

Date: Sun, 11 Mar 2007 03:25:09 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: why doesn't this argument list need a comma after the 1st argument?
Message-Id: <ld9cc4-bmb.ln1@osiris.mauzo.dyndns.org>


Quoth "Dave Slayton" <evad.notyals@liamg.moc>:
> Sorry, another newbie question:
> 
> I'm reading this very interesting book on Perl (Effective Perl Programming 
> by Joseph N. Hall with Randal L. Schwartz), and here on page 110 there's an 
> example of a
> call to a (prototyped) subroutine that requires 3 arguments:  a coderef, a 
> scalar, and an array, and here's the call:
> 
>    for_n {print "$_[0], $_[1]\n"} 2, @a;
> 
> I understand the parentheses around the list of arguments are optional, and 
> that the anonymous subroutine does not require the "sub" keyword, but what I 
> don't understand is how the call gets away with not having a comma after the 
> closing curly brace and before the 2.  Can anyone shed some light on this 
> for me? 

It's a special case. Prototypes were introduced to allow you to write
subs that parse like Perl builtins; so, to allow a map-like sub to be
written, a sub with its first argument prototyped '&' will accept a bare
block (without a comma) like this, and treat it as an anon sub.

Actually, this is the only case where the sub keyword is optional: a sub
prototyped as ($&$) would still need to be called like

    foo 1, sub {...}, 2;

See perldoc perlsub for all the details.

Ben

-- 
BEGIN{*(=sub{$,=*)=sub{print@_};local($#,$;,$/)=@_;for(keys%{ #ben@morrow.me.uk
$#}){/m/&&next;**=${$#}{$_};/(\w):/&&(&(($#.$_,$;.$+,$/),next);$/==\$*&&&)($;.$
_)}};*_=sub{for(@_){$|=(!$|||$_||&)(q) )));&((q:\:\::,q,,,\$_);$_&&&)("\n")}}}_
$J::u::s::t, $a::n::o::t::h::e::r, $P::e::r::l, $h::a::c::k::e::r, $,


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

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 214
**************************************


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