[28526] in Perl-Users-Digest

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

Perl-Users Digest, Issue: 9890 Volume: 10

daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Oct 25 18:10:23 2006

Date: Wed, 25 Oct 2006 15:10:14 -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           Wed, 25 Oct 2006     Volume: 10 Number: 9890

Today's topics:
        Remove short words from a string <leifwessman@hotmail.com>
    Re: Remove short words from a string yankeeinexile@gmail.com
    Re: Remove short words from a string <mritty@gmail.com>
    Re: Remove short words from a string <wahab@chemie.uni-halle.de>
    Re: Remove short words from a string <tzz@lifelogs.com>
    Re: Remove short words from a string <tzz@lifelogs.com>
    Re: Remove short words from a string <rvtol+news@isolution.nl>
    Re: Setting permissions on remote directory using Net:: <someone@example.com>
        simple string extracting <mislam@spam.uiuc.edu>
    Re: simple string extracting <xicheng@gmail.com>
    Re: simple string extracting <mritty@gmail.com>
    Re: simple string extracting yankeeinexile@gmail.com
    Re: simple string extracting <wahab@chemie.uni-halle.de>
    Re: simple string extracting <mislam@spam.uiuc.edu>
        stop encoding of href in anchor meyerto@gmail.com
    Re: stop encoding of href in anchor <dorward@yahoo.com>
    Re: stop encoding of href in anchor <john@castleamber.com>
    Re: string substitution for a file, without replacing p <bootiack@yahoo.com>
    Re: use of variables <brian.raven@osbsl.co.uk>
    Re: use of variables <joe@inwap.com>
    Re: using File::Find with big files on Linux <rohm@cisco.com>
    Re: using File::Find with big files on Linux <bik.mido@tiscalinet.it>
    Re: Why I no longer use Perl <strenholme.usenet@gmail.com>
    Re: Why I no longer use Perl <hjp-usenet2@hjp.at>
        Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)

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

Date: 25 Oct 2006 08:03:20 -0700
From: "Leif Wessman" <leifwessman@hotmail.com>
Subject: Remove short words from a string
Message-Id: <1161788600.673733.102100@m7g2000cwm.googlegroups.com>


Hi all!

How can I remove all words that have a length that is 3 or less?

"a lot of words in this text";

should become

"words this text"

Is it possible?

Leif



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

Date: 25 Oct 2006 10:31:40 -0500
From: yankeeinexile@gmail.com
Subject: Re: Remove short words from a string
Message-Id: <871wowjtsz.fsf@gmail.com>

"Leif Wessman" <leifwessman@hotmail.com> writes:

> Hi all!
> 
> How can I remove all words that have a length that is 3 or less?
> 
> "a lot of words in this text";
> 
> should become
> 
> "words this text"
> 
> Is it possible?
> 
> Leif
> 

Here is your hint.
 grep { length > 3 } @words;

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
	Lawrence Statton - lawrenabae@abaluon.abaom s/aba/c/g
Computer  software  consists of  only  two  components: ones  and
zeros, in roughly equal proportions.   All that is required is to
sort them into the correct order.


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

Date: 25 Oct 2006 08:42:20 -0700
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: Remove short words from a string
Message-Id: <1161790940.246477.253290@e3g2000cwe.googlegroups.com>

Leif Wessman wrote:
> How can I remove all words that have a length that is 3 or less?
>
> "a lot of words in this text";
>
> should become
>
> "words this text"
>
> Is it possible?

Yes, it's possible.

There are two approaches which jump out at me.  You could use a
join/grep/split combination.  Or you could use a regexp solution being
sure to include word boundaries.

What have you tried so far?  How did it not work as you expected?

Paul Lalli



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

Date: Wed, 25 Oct 2006 18:36:26 +0200
From: Mirco Wahab <wahab@chemie.uni-halle.de>
Subject: Re: Remove short words from a string
Message-Id: <eho41u$rrh$1@mlucom4.urz.uni-halle.de>

Thus spoke Leif Wessman (on 2006-10-25 17:03):

> How can I remove all words that have a length that is 3 or less?
> "a lot of words in this text";
> should become
> "words this text"
> Is it possible?

Hi Leif,

this is something Perl was invented for ;-)
I'll try to give a easy example and you'll
try to explain it line by line in your reply, ok?

  use strict;
  use warnings;

  my $shortlen  = 3;
  my $fulltext  = 'a lot of words in this text';
  my $no_shorts = $fulltext;

  $no_shorts =~ s/ \b \w{1,$shortlen} \b \s+//gmx;

  print $fulltext, "\n";
  print $no_shorts, "\n";



Regards,

Mirxo


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

Date: Wed, 25 Oct 2006 17:41:45 +0100
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Remove short words from a string
Message-Id: <g69ods0uz3q.fsf@lifelogs.com>

On 25 Oct 2006, yankeeinexile@gmail.com wrote:

> "Leif Wessman" <leifwessman@hotmail.com> writes:
>
>> Hi all!
>>
>> How can I remove all words that have a length that is 3 or less?
>>
>> "a lot of words in this text";
>>
>> should become
>>
>> "words this text"
>>
>> Is it possible?
>>
>> Leif
>>
>
> Here is your hint.
> grep { length > 3 } @words;

That's not a good hint.

Ted


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

Date: Wed, 25 Oct 2006 17:50:19 +0100
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Remove short words from a string
Message-Id: <g69k62ouypg.fsf@lifelogs.com>

On 25 Oct 2006, leifwessman@hotmail.com wrote:

> How can I remove all words that have a length that is 3 or less?
>
> "a lot of words in this text";
>
> should become
>
> "words this text"

Solution below.  Note that your requirement ("remove all words...")
does not match the expected result, since you are also removing
whitespace around the words.  That's why I added the second regex.
Still, the leading space is preserved.  You can either add a third
regex to eliminate leading spaces, or you can split on ' '.

Keep in mind that if you split on ' ' you still won't have "words"
because punctuation will be included, for example.  This is why I
would recommend against a split()/grep()/join() approach for this,
unless you are absolutely sure you don't need to worry about
punctuation or preserving spaces.

Ted

#!/usr/bin/perl

use warnings;
use strict;

my $text = "a lot of words in this text";
# note \w may not work well for you, adjust accordingly
$text =~ s/(\w+)/length $1 > 3 ? $1 : ''/eg;
# if you need multiple spaces collapsed to just one
$text =~ s/\s+/ /g;
print $text;


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

Date: Wed, 25 Oct 2006 22:11:45 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: Remove short words from a string
Message-Id: <ehonfa.1ns.1@news.isolution.nl>

Mirco Wahab schreef:
> Leif:

>> How can I remove all words that have a length that is 3 or less?
>> "a lot of words in this text";
>> should become
>> "words this text"
>
> I'll try to give a easy example and you'll
> try to explain it line by line in your reply, ok?
>
>   use strict;
>   use warnings;
>
>   my $shortlen  = 3;
>   my $fulltext  = 'a lot of words in this text';
>   my $no_shorts = $fulltext;
>
>   $no_shorts =~ s/ \b \w{1,$shortlen} \b \s+//gmx;

1. Won't work well with a short last word. Maybe use "\s*" or
"(?:\s+|$)".

2. Maybe "\w" is too limited, it is just [[:alnum:]_], so doesn't
contain "-", which could lead to unwanted changes, like of
"non-essential", etc.

>   print $fulltext, "\n";
>   print $no_shorts, "\n";

-- 
Affijn, Ruud

"Gewoon is een tijger."



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

Date: Wed, 25 Oct 2006 19:45:39 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: Setting permissions on remote directory using Net::SFTP
Message-Id: <D9P%g.31518$P7.11889@edtnps90>

timothy.hill@gmail.com wrote:
> 
> I am in the process of writing a script that puts files on a remote
> unix box from a windows machine (I am also using Net::SSH::W32Perl). It
> is important that these files are placed in the correct directory and
> if that directory does not exist, it must be created with the correct
> permissions (777). For this I am using the do_mkdir() function. I am
> able to create the directory fine, but I just cannot get the
> permissions to set correctly - I have put loads of different numbers
> into this, but have been able to get anything but rwxrwxrwx on the
> directory. The code I have hacked for this bit is:
> 
>          my $attrs = new Net::SFTP::Attributes();
>          $attrs->flags(15);
>          $attrs->size(4096);
>          $attrs->uid($ftp_info{$user}->{'uid'});
>          $attrs->gid($ftp_info{$user}->{'gid'});
>          $attrs->perm(16895);
>          $attrs->atime(time);
>          $attrs->mtime(time);
> 
>          $sftp->do_mkdir($remote_dir, $attrs);
> 
> The 16895 value you see is the mode value I have obtained from doing a
> stat on a directory that has the required permissions, but running this
> code only produces drwxr-xr-x premissions. This is driving me potty -
> can anyone help?

16895 is too large, you can't set the fifteenth bit.  Try it with:

          $attrs->perm( 0777 );  # octal notation

Or:

          $attrs->perm( 511 );  # decimal notation

Or:

          $attrs->perm( 0x1ff );  # hexadecimal notation




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: Wed, 25 Oct 2006 11:29:50 -0500
From: Sharif Islam <mislam@spam.uiuc.edu>
Subject: simple string extracting
Message-Id: <eho3dv$79i$1@news.ks.uiuc.edu>

I have some strings that look like this:
info:sid/SOMECHAR:abc

The part of the string I am interested in is 'SOMECHAR' (the 'info:sid/' 
will always be there). Is there a better way to extract this?

#! /usr/bin/perl
use strict;

my $out;
my $string = "info:sid/SOMECHAR:xyz";
if($string =~ m/:(.*):/) {
          ($out = $1) =~ s/sid\///;
         print $out ;
}

# perl string.pl
SOMECHAR


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

Date: 25 Oct 2006 09:37:40 -0700
From: "Xicheng Jia" <xicheng@gmail.com>
Subject: Re: simple string extracting
Message-Id: <1161794259.897377.263210@b28g2000cwb.googlegroups.com>

Sharif Islam wrote:
> I have some strings that look like this:
> info:sid/SOMECHAR:abc
>
> The part of the string I am interested in is 'SOMECHAR' (the 'info:sid/'
> will always be there). Is there a better way to extract this?
>
> #! /usr/bin/perl
> use strict;
>
> my $out;
> my $string = "info:sid/SOMECHAR:xyz";

How about:

  $out = (split '[/:]', $string)[2];

Xicheng

> if($string =~ m/:(.*):/) {
>           ($out = $1) =~ s/sid\///;
>          print $out ;
> }



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

Date: 25 Oct 2006 09:39:06 -0700
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: simple string extracting
Message-Id: <1161794346.847918.305340@k70g2000cwa.googlegroups.com>

Sharif Islam wrote:
> I have some strings that look like this:
> info:sid/SOMECHAR:abc
>
> The part of the string I am interested in is 'SOMECHAR' (the 'info:sid/'
> will always be there). Is there a better way to extract this?
>
> #! /usr/bin/perl
> use strict;
>
> my $out;
> my $string = "info:sid/SOMECHAR:xyz";
> if($string =~ m/:(.*):/) {
>           ($out = $1) =~ s/sid\///;
>          print $out ;
> }

Why are you doing two regular expressions?

if ($string =~ m{^info:sid/(.*):}) {
   print $1;
}

Paul Lalli



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

Date: 25 Oct 2006 11:38:59 -0500
From: yankeeinexile@gmail.com
Subject: Re: simple string extracting
Message-Id: <87vem8ic4c.fsf@gmail.com>

Sharif Islam <mislam@spam.uiuc.edu> writes:
> I have some strings that look like this:
> info:sid/SOMECHAR:abc
> 
> The part of the string I am interested in is 'SOMECHAR' (the
> 'info:sid/' will always be there). Is there a better way to extract
> this?
> 
> #! /usr/bin/perl
> use strict;
> 
> my $out;
> my $string = "info:sid/SOMECHAR:xyz";
> if($string =~ m/:(.*):/) {
>           ($out = $1) =~ s/sid\///;
>          print $out ;
> }

Why use two regexps when one is just as good?

#!/usr/bin/perl
use strict;
use warnings;

my $out;
my $string = "info:sid/SOMECHAR:xyz";
if(my ($out) = $string =~ m|info:sid/(.*):xyz| ) {
  print "$out\n";
}




-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
	Lawrence Statton - lawrenabae@abaluon.abaom s/aba/c/g
Computer  software  consists of  only  two  components: ones  and
zeros, in roughly equal proportions.   All that is required is to
sort them into the correct order.


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

Date: Wed, 25 Oct 2006 19:30:13 +0200
From: Mirco Wahab <wahab@chemie.uni-halle.de>
Subject: Re: simple string extracting
Message-Id: <eho76p$sm8$1@mlucom4.urz.uni-halle.de>

Thus spoke Sharif Islam (on 2006-10-25 18:29):

> I have some strings that look like this:
> info:sid/SOMECHAR:abc
> my $string = "info:sid/SOMECHAR:xyz";

   ...
   print +($string =~ /sid\/(.+?):/);
   ...

or
   ...
   ($out) = ($string =~ /sid\/(.+?):/);
   ...


Regards

M.




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

Date: Wed, 25 Oct 2006 14:00:53 -0500
From: Sharif Islam <mislam@spam.uiuc.edu>
Subject: Re: simple string extracting
Message-Id: <ehoc95$a56$1@news.ks.uiuc.edu>

Paul Lalli wrote:
> Sharif Islam wrote:
> 
>>I have some strings that look like this:
>>info:sid/SOMECHAR:abc
>>
>>The part of the string I am interested in is 'SOMECHAR' (the 'info:sid/'
>>will always be there). Is there a better way to extract this?
>>
>>#! /usr/bin/perl
>>use strict;
>>
>>my $out;
>>my $string = "info:sid/SOMECHAR:xyz";
>>if($string =~ m/:(.*):/) {
>>          ($out = $1) =~ s/sid\///;
>>         print $out ;
>>}
> 
> 
> Why are you doing two regular expressions?
> 
> if ($string =~ m{^info:sid/(.*):}) {
>    print $1;
> }
> 

thanks. that is better.

--sharif


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

Date: 25 Oct 2006 13:52:38 -0700
From: meyerto@gmail.com
Subject: stop encoding of href in anchor
Message-Id: <1161809558.074905.296730@k70g2000cwa.googlegroups.com>

This:

use CGI qw(:standard);
print a({href=>'cats&dogs'},pets);

produces:

<a href="cats&amp;dogs">pets</a>

How can I stop the & from being encoded to &amp; ?



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

Date: Wed, 25 Oct 2006 22:39:18 +0100
From: David Dorward <dorward@yahoo.com>
Subject: Re: stop encoding of href in anchor
Message-Id: <eholin$9sr$1$8300dec7@news.demon.co.uk>

meyerto@gmail.com wrote:

> use CGI qw(:standard);
> print a({href=>'cats&dogs'},pets);
> produces:
> <a href="cats&amp;dogs">pets</a>

> How can I stop the & from being encoded to &amp; ?

Why would you want to?

"dogs" is not a named entity in HTML, and the context suggests you want & as
in "and" not & as in "The start of a character reference", in which case it
needs to be represeted as the entity.

-- 
David Dorward       <http://blog.dorward.me.uk/>   <http://dorward.me.uk/>
                     Home is where the ~/.bashrc is


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

Date: 25 Oct 2006 21:52:51 GMT
From: John Bokma <john@castleamber.com>
Subject: Re: stop encoding of href in anchor
Message-Id: <Xns9867ABB8488BCcastleamber@130.133.1.4>

meyerto@gmail.com wrote:

> This:
> 
> use CGI qw(:standard);
> print a({href=>'cats&dogs'},pets);
> 
> produces:
> 
> <a href="cats&amp;dogs">pets</a>
> 
> How can I stop the & from being encoded to &amp; ?

Can you give any /good/ reason why this shouldn't happen?

-- 
John                Experienced Perl programmer: http://castleamber.com/

          Perl help, tutorials, and examples: http://johnbokma.com/perl/


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

Date: 25 Oct 2006 13:19:57 -0700
From: "gavino" <bootiack@yahoo.com>
Subject: Re: string substitution for a file, without replacing partial string?
Message-Id: <1161807597.059741.167400@k70g2000cwa.googlegroups.com>

I am sorry for whatever i have done to create your disliek for me.
The script provided by X- above does work.



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

Date: Wed, 25 Oct 2006 21:46:37 +0100
From: Brian Raven <brian.raven@osbsl.co.uk>
Subject: Re: use of variables
Message-Id: <ejswt976.fsf@osbsl.co.uk>

Michael Perle <michael_perle@yahoo.com> writes:

> news2003@wanadoo.es wrote:
>> $a = 10;
>> $b = 5;
>> print "trail ". $a + $b . "\n";  # why this???
>> $perl sample3.pl
>> 5
>
> The precedence of the plus might be lower than
> the one of the string concatenation? I don't know,
> but if so then the first statement would be like
>
> print ("trail " . $a) + ($b . "\n");
>
> where ($b + "\n") results in "5\n".
>
>> If I change the last statement to
>> print "trail ". ($a + $b) . "\n";  # why this???
>
> Yes, that seems to confirm that I am right with the above.

If you had checked 'perldoc perlop' you would have seen that those
operators have the same precedence.

HTH

-- 
Brian Raven


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

Date: Wed, 25 Oct 2006 14:48:21 -0700
From: Joe Smith <joe@inwap.com>
Subject: Re: use of variables
Message-Id: <F7ednYm53eJ1RqLYnZ2dnUVZ_tGdnZ2d@comcast.com>

Michael Perle wrote:
> news2003@wanadoo.es wrote:
>> $a = 10;
>> $b = 5;
>>
>> print "trail ". $a + $b . "\n";  # why this???
> 
> print ("trail " . $a) + ($b . "\n");

Not quite.  The "(" after "print" causes the "if it looks like a
function, it is a function" rule to be invoked.  What you've
written is parsed as:

   (print("trail " . $a)) + ($b . "\n");
=
   (print "trail 10") + ("$b\n");
=
   1 + "5\n";
=
   Useless use of addition (+) in void context at /tmp/test.pl line 4.

	-Joe


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

Date: Wed, 25 Oct 2006 11:57:44 -0700
From: Matt Rohm <rohm@cisco.com>
Subject: Re: using File::Find with big files on Linux
Message-Id: <1161802663.410398@sj-nntpcache-1.cisco.com>

Thanks for pointing this out, I think you have hit the basic
problem.  The results of the stat are compare against a number
of rules, trying to filter all files and find the old, large files.

Sorry for ignoring the posting rules, next I will include code and
everyone can point out my stupid mistake.


Michele Dondi wrote:
> On Tue, 24 Oct 2006 16:50:09 -0700, Matt Rohm <rohm@cisco.com> wrote:
> 
> 
>>routine.  When it comes across really big files,
>>say >4GB it examines (or compares) the file twice.
>>
>>Anyone seen this before?  Care to share the cause of
>>this problem, and some ideas for a solution?
> 
> 
> As others said, this sounds strange, and it would be easier to believe
> it if you gave some evidence. Wild guess: isn't it that you're doing
> multiple stat(s) perhaps in the disguised form of some -X? If so, then
> just use the _ filehandle, if possible of course. However this should
> affect *all* files independently of their size, but perhaps you were
> concerned about "really big files" and only noticed the thing in
> connection with them...
> 
> 
> Michele


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

Date: 26 Oct 2006 00:02:12 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: using File::Find with big files on Linux
Message-Id: <kbnvj2he09di13dcp4446vq0sjd0kf5a2q@4ax.com>

On Wed, 25 Oct 2006 11:57:44 -0700, Matt Rohm <rohm@cisco.com> wrote:

>Thanks for pointing this out, I think you have hit the basic
>problem.  The results of the stat are compare against a number
>of rules, trying to filter all files and find the old, large files.

If you use the *results*, and I think you mean the return value, of a
stat(), then you should not have problems. If you call, say, -f, -s
and so on on the same filehandle, then you may, since they call stat()
again each time. Thus you can use the _ filehandle, as hinted in the
other post, as that will use cached values from the last stat()
instead.

>Sorry for ignoring the posting rules, next I will include code and
>everyone can point out my stupid mistake.

Well, there's no guarantee either. We're not perfect of course. But
indeed if you paste some minimal but complete example exhibiting the
problem you're having, then it will be easier to help you.

BTW: *please* do not top-post. It's annoying, and makes editing and
replying harder for mostly everybody here. (See below!)

>Michele Dondi wrote:
>> On Tue, 24 Oct 2006 16:50:09 -0700, Matt Rohm <rohm@cisco.com> wrote:
[snip full quoted context]


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: 25 Oct 2006 09:57:58 -0700
From: "strenholme.usenet@gmail.com" <strenholme.usenet@gmail.com>
Subject: Re: Why I no longer use Perl
Message-Id: <1161795478.268012.229690@m73g2000cwd.googlegroups.com>

First of all, I would like to thank Peter for taking time to help with
this issue.  The open(A,'<:utf8','unicode.char'); line fixed the issue
for Perl 5.8.0 and Perl 5.8.8.

In reply for Peter's request for more information:

$ env | grep LANG
LANG=en_US.UTF-8

I wish I had more time to study the dark mysteries of how Perl
determines the encoding for the script, the input Perl receives, and
the output Perl prints.  I assumed "use utf8" told Perl "the script and
all input and output will be in UTF8"; I was wrong.  Unfortunatly, I am
no longer a computer professional (the dot-com bubble exploding hit me
hard) and am a full-time ESL English teacher these days who programs
open-source projects as a hobby.

I have the highest of respect for the Perl language and the Perl
community.  I have had the pleasure of meeting Larry Wall at a SVLUG
meeting during my days as a dot-com worker and am still very impressed
with how nice and charming Larry is.

The reason why I have to put up with !@#$ Perl 5.8.0 bugs is because
some actively maintained Linux distributions (Such as RedHat Enterprise
Linux 3 and derivatives) still distribute this fossil.

Again, I thank everyone for their responses and their help.

- Sam



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

Date: Wed, 25 Oct 2006 21:47:55 +0200
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: Why I no longer use Perl
Message-Id: <slrnejvfrb.5u8.hjp-usenet2@yoyo.hjp.at>

On 2006-10-25 16:57, strenholme.usenet@gmail.com <strenholme.usenet@gmail.com> wrote:
> I wish I had more time to study the dark mysteries of how Perl
> determines the encoding for the script, the input Perl receives, and
> the output Perl prints.  I assumed "use utf8" told Perl "the script and
> all input and output will be in UTF8"; I was wrong.

You can use the PERL_UNICODE environment variable or the -C option for
that. But there are still some areas where explicit conversion is
necessary.

> The reason why I have to put up with !@#$ Perl 5.8.0 bugs is because
> some actively maintained Linux distributions (Such as RedHat Enterprise
> Linux 3 and derivatives) still distribute this fossil.

Yep. Most of our RHEL servers are running RHEL 3, too. Fortunately I can
simply install a newer perl if I run into problems. (There's an
advantage if the sysadmin and the perl programmer are the same person
:-).

	hp


-- 
   _  | Peter J. Holzer    | > Wieso sollte man etwas erfinden was nicht
|_|_) | Sysadmin WSR       | > ist?
| |   | hjp@hjp.at         | Was sonst wäre der Sinn des Erfindens?
__/   | http://www.hjp.at/ |	-- P. Einstein u. V. Gringmuth in desd


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

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


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