[32065] in Perl-Users-Digest
Perl-Users Digest, Issue: 3329 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Mar 23 18:09:24 2011
Date: Wed, 23 Mar 2011 15:09:05 -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, 23 Mar 2011 Volume: 11 Number: 3329
Today's topics:
Re: "getting" a website <derykus@gmail.com>
Re: File::Slurp 9999.14 is released <Uno@example.invalid>
Re: File::Slurp 9999.14 is released <kkeller-usenet@wombat.san-francisco.ca.us>
Re: File::Slurp 9999.14 is released <uri@StemSystems.com>
Re: File::Slurp 9999.14 is released <cartercc@gmail.com>
Re: module for MSCRM? (hymie!)
Perl script running external command <cartercc@gmail.com>
Re: polling TCP server on Win32 (with Tk) <email@invalid.net>
Re: using File::Find (Alan Curry)
Re: using File::Find <hjp-usenet2@hjp.at>
Re: using File::Find <jurgenex@hotmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Wed, 23 Mar 2011 00:28:55 -0700 (PDT)
From: "C.DeRykus" <derykus@gmail.com>
Subject: Re: "getting" a website
Message-Id: <df94ea78-dabb-424a-b2aa-b6dc7294b8f8@z3g2000prz.googlegroups.com>
On Mar 22, 6:57=A0pm, Uno <U...@example.invalid> wrote:
> On 03/22/2011 07:17 PM, Uri Guttman wrote:
>
> >>>>>> "U" =3D=3D Uno<U...@example.invalid> =A0writes:
>
> > =A0 =A0U> =A0 =A0 =A0 =A0 =A0 =A0 "cats and dogs" =3D~ /cat|dog|bird/; =
=A0# matches "cat"
> > =A0 =A0U> =A0 =A0 =A0 =A0 =A0 =A0 "cats and dogs" =3D~ /dog|cat|bird/; =
=A0# matches "cat"
>
> > =A0 =A0U> =A0Interesting. =A0Might a person call the alternating operat=
or "idempotent?"
>
> > not interesting. you don't get the ordering. a regex scans the data and
> > then tries to match it in the regex. cat will always match first since
> > it is first in the string.
>
> So, are you saying that man perlretut is uninteresting? =A0There's so muc=
h
> about regex's that I don't know that i have to skip alot of it.
>
> I think I'm cool as cats because I just went up to it and typed
> /alternat
> and got
>
> =A0 =A0 Matching this or that
> =A0 =A0 =A0 =A0 Sometimes we would like our regexp to be able to match di=
fferent
> =A0 =A0 =A0 =A0 possible words or character strings. =A0This is accomplis=
hed by
> using the
> =A0 =A0 =A0 =A0 alternation metacharacter "|". =A0To match "dog" or "cat"=
, we form the
> =A0 =A0 =A0 =A0 regexp "dog|cat". =A0As before, Perl will try to match th=
e regexp
> at the
> =A0 =A0 =A0 =A0 earliest possible point in the string. =A0At each charact=
er position,
> =A0 =A0 =A0 =A0 Perl will first try to match the first alternative, "dog"=
. =A0If "dog"
> =A0 =A0 =A0 =A0 doesn't match, Perl will then try the next alternative, "=
cat". =A0If
> =A0 =A0 =A0 =A0 "cat" doesn't match either, then the match fails and Perl=
moves
> to the
> =A0 =A0 =A0 =A0 next position in the string. =A0Some examples:
>
> =A0 =A0 =A0 =A0 =A0 =A0 "cats and dogs" =3D~ /cat|dog|bird/; =A0# matches=
"cat"
> =A0 =A0 =A0 =A0 =A0 =A0 "cats and dogs" =3D~ /dog|cat|bird/; =A0# matches=
"cat"
>
> =A0 =A0 =A0 =A0 Even though "dog" is the first alternative in the second =
regexp,
> "cat"
> =A0 =A0 =A0 =A0 is able to match earlier in the string.
>
> , without hitting f once.
>
> What other things do you ascribe idempotence to?
That's because the regex remains anchored to
position 0 in the string 'cats and dogs' after alternative #1 'dog'
fails. So the regex then
tries the other alternatives in succession.
Perhaps you're conflating alternatives with
separate pattern matches:
$_ =3D 'cats and dogs';
print "got a dog and a cat\n"
if /dog/ and /cat/;
--
Charles DeRykus
------------------------------
Date: Tue, 22 Mar 2011 22:24:43 -0600
From: Uno <Uno@example.invalid>
Subject: Re: File::Slurp 9999.14 is released
Message-Id: <8utb0aFlmcU1@mid.individual.net>
On 03/22/2011 09:53 PM, Uri Guttman wrote:
>
> File::Slurp 9999.14 is released and on cpan. many changes and
> improvements were made. it's been way too long for an update but it is
> finally here. the next version will be out in a few months with some
> more new features (see the TODO file). the changes are below
>
> uri
>
> 9999.14 Sun Mar 20 16:26:47 EDT 2011
> - Added LICENCE (same as perl) to POD
> - Added special faster code to slurp in small text files which
> is a common case
> - Rewrote the extras/slurp_bench.pl script. It has a full
> legend, better CLI options, size is selectable, benchmark
> entries have more consistant names and it compares the new
> fast slurp for small files to the general slurp code.
> Thanks to Mark Friendlich
> - Cleaned up pod
> - Added more Synopsis examples
> - Added t/error.t to actually test error conditions. Previous
> error.t was renamed to error_mode.t which better reflects its
> tests.
> - t/error.t uses a new test driver module. this may get used by
> other tests in the future.
> - Fixed check for SEEK_SET and other constant subs being defined
> - Added support for binmode other than :raw and binmode.t test
> Thanks to Martin J. Evans, Peter Edwards, Bryce Nesbitt
> - Added support for perms option in write_file and perms.t test
> Thanks to Peter Corlett and Paul Miller
> - Added check to the rename call in atomic mode. Tested in error.t.
> Thanks to Daniel Scott Sterling
> - Added POD to state that using scalar_ref or buf_ref will be faster
> and save memory due to not making a copy
> Thanks to Peter Edwards
> - read_file in list mode keeps data tainted
> Thanks to Sébastien Aperghis-Tramoni
> - read_file checks for an overloaded object to get the file
> name.
> Thanks to Sébastien Aperghis-Tramoni
>
>
>
You keep on posting this. If you don't think this is boring then you've
never seen a bad movie.
--
Uno
------------------------------
Date: Tue, 22 Mar 2011 21:34:35 -0700
From: Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us>
Subject: Re: File::Slurp 9999.14 is released
Message-Id: <sr9o58xq56.ln2@goaway.wombat.san-francisco.ca.us>
["Followup-To:" header set to comp.lang.perl.misc.]
On 2011-03-23, Uno <Uno@example.invalid> wrote:
> On 03/22/2011 09:53 PM, Uri Guttman wrote:
>>
>> File::Slurp 9999.14 is released and on cpan.
[snip]
> You keep on posting this. If you don't think this is boring then you've
> never seen a bad movie.
Uri's post is completely appropriate for the Perl newsgroups. If you
don't like his announcements, killfile on the Subject: ; any good
newsreader should allow you to use a regex to match any future version
of File::Slurp.
FWIW, posts about how whereis works are not appropriate for Perl
newsgroups.
--keith
--
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
------------------------------
Date: Wed, 23 Mar 2011 02:03:14 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: File::Slurp 9999.14 is released
Message-Id: <87mxkmwezh.fsf@quad.sysarch.com>
>>>>> "U" == Uno <Uno@example.invalid> writes:
U> On 03/22/2011 09:53 PM, Uri Guttman wrote:
>>
>> File::Slurp 9999.14 is released and on cpan. many changes and
>> improvements were made. it's been way too long for an update but it is
>> finally here. the next version will be out in a few months with some
>> more new features (see the TODO file). the changes are below
>>
U> You keep on posting this. If you don't think this is boring then
U> you've never seen a bad movie.
as in where or when did i do this? you are proving yourself to be very
delusional. it was crossposted once tonight to clp.misc and
clp.modules.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Wed, 23 Mar 2011 13:07:49 -0700 (PDT)
From: ccc31807 <cartercc@gmail.com>
Subject: Re: File::Slurp 9999.14 is released
Message-Id: <2e6f4803-cb6d-47ee-840f-9b312f895162@17g2000prr.googlegroups.com>
On Mar 23, 12:24=A0am, Uno <U...@example.invalid> wrote:
> You keep on posting this. =A0If you don't think this is boring then you'v=
e
> never seen a bad movie.
Uno,
This isn't a personal criticism or an ugly post, so please don't take
it that way.
There are a class of people in the world who server others, who are
productive and effective, who seek the betterment of their world, and
who sacrifice for the benefit of their fellow men. The OP is an
example of this. We should encourage these people and support their
efforts.
I don't know why you posted the above, but it's not helpful. Even if
you find it boring, even if you find it inappropriate, you shouldn't
respond negatively.
Besides which, you would probably learn something by reading through
this. You might not find it useful directly, but you might pick up
some helpful idioms.
CC.
------------------------------
Date: 23 Mar 2011 14:01:37 GMT
From: hymie@lactose.homelinux.net (hymie!)
Subject: Re: module for MSCRM?
Message-Id: <4d89fd41$0$23128$882e7ee2@usenet-news.net>
Wow. I could have sworn I posted a response to this, but I can't seem
to find it on my news server.
In our last episode, the evil Dr. Lacto had captured our hero,
Justin C <justin.1102@purestblue.com>, who said:
>On 2011-03-16, hymie! <hymie@lactose.homelinux.net> wrote:
>Sorry, seriously though, I don't know. Doesn't the CRM drive SQL,
>surely there's a database underneath it somewhere? Wouldn't that be
>what you want to talk to?
Because the database is an ugly mess of poorly-named tables which I
would rather not have to deal with, and assorted other wheels I would
rather not have to reinvent. The software, on the other hand, should
know all of this information already.
For example, my "primary" table has four fields. Each field contains
a numeric value. Somewhere in the database are tables that related these
numeric values to the text values I need. Those tables have names like
AR090109. There are a few dozen tables with names like that. I don't
want to have to figure out what each table is, when I can in theory just
ask the CRM "If the GUI would have displayed a text value, what would it
have been?"
Also, my copy of freetds does not work with UTF-8, which is apparantly
what one of my fields is encoded in. freetds seems to have disappeared;
at least, I can't find it, although my google-fu is admittedly very weak.
--hymie! http://lactose.homelinux.net/~hymie hymie@lactose.homelinux.net
------------------------------
Date: Wed, 23 Mar 2011 12:52:12 -0700 (PDT)
From: ccc31807 <cartercc@gmail.com>
Subject: Perl script running external command
Message-Id: <30db2cd4-ad3d-4347-93e1-3a5111b64198@o21g2000prh.googlegroups.com>
This probably isn't a c.l.p.m. issue, but I'll ask anyway.
I have a script that's run for years, part of which runs pscp to
download and upload files to a remote server several times a day. This
functionality is part of an essential process, and my organization's
activities would come to a screeching halt if this ever failed. The
machines are Windows servers.
The call looks something like this:
sub get_app_file
{
my $success =3D system './pscp -p -pw password username@12.34.56.78/
directory/path/filename*.txt .';
if ($success =3D=3D 0) { $log .=3D "Successfully downloaded application
file.\n"; }
else { $log .=3D "PROBLEM WITH downloaded application file.\n"; }
}
The hardware guys are updating the servers, and I am in the process of
moving these scripts to a new machine. A week ago, the download
function worked, and today I can run it by hand -- BUT the script
fails with this error message:
=91Fatal: Network error: Connection timed out=92
The hardware guys claim that they have made no change whatsoever to
the system, but we have automatic updates, which have run.
Any clues as to what might cause the problem? And maybe how to
diagnose the failure? I'm not a hardware guy or a network guy, and I
don't have any idea where to begin.
Thanks, CC.
------------------------------
Date: Wed, 23 Mar 2011 14:21:51 GMT
From: QoS <email@invalid.net>
Subject: Re: polling TCP server on Win32 (with Tk)
Message-Id: <3mnip.139998$4c7.97272@newsfe06.iad>
JohnD <JohnD@nowhere.com> wrote in message-id: <4d887b62$0$9483$e4fe514c@dreader19.news.xs4all.nl>
>
> I posted this in comp.lang.perl.tk but would like to give it a try over
> here.
>
> The problem is Win32 (Unix works). I do not understand the very
> details of the differences between sockets on Unix and Windows. I just
> want working code, the socket part (server).
> If this socket part works I can get my real program working.
>
> Who can help me producing a working program on Windows?
>
> One server, one client. The client connects, sends strings (1-30 bytes)
> once every few seconds, the server processes these strings within 0.1
> seconds, and the connection remains open for an hour or so. If a fixed
> string-length would be better: fine. If UDP is much easier: please show me.
>
> My code so far (runs on Linux, freezes on Windows while processing the
> first message)
>
> #!/usr/bin/perl
> use strict;
> use warnings;
> use IO::Socket;
> use Tk;
>
> $| = 1;
> $SIG{PIPE} = 'IGNORE';
>
> my $listen = IO::Socket::INET->new(
> Proto => 'tcp',
> LocalPort => 7777,
> Listen => 1,
> Reuse => 1,
> ) or die "Can't create listen socket : $!\n";
>
> my $mw = MainWindow->new();
>
> my $text = $mw->Scrolled( 'Text', )->pack();
>
> my ($sel);
> if ( $^O eq 'MSWin32' ) {
> $mw->repeat( 50, [ \&new_connection, $listen ] );
> }
> else {
> $mw->fileevent( $listen, 'readable' => [ \&new_connection, $listen ]
> );
> }
>
> Tk::MainLoop;
>
> sub new_connection {
> my ($listen) = shift;
> my ($sel);
> my $client = $listen->accept() or warn "Can't accept connection";
> $client->autoflush(1);
> if ( $^O eq 'MSWin32' ) {
> use IO::Select;
> $sel = IO::Select->new;
> $sel->add($listen);
> $mw->repeat( 50, [ \&handle_connection, $client, $sel ] );
> }
> else {
> $mw->fileevent( $client,
> 'readable' => [ \&handle_connection, $client, $sel ] );
> }
>
> $text->insert( 'end', "Connected\t" );
> $text->see('end');
> }
>
> sub handle_connection {
> my ( $client, $sel ) = shift;
> if ( $^O eq 'MSWin32' ) {
> my (@ready) = $sel->can_read(0);
> return if $#ready == -1;
> $client = $ready[0];
> }
> my $message = <$client>;
> if ( defined $message and $message !~ /^quit/ ) {
> $message =~ s/[\r\n]+$//;
> $text->insert( 'end', "Got message [$message]\t" );
> $text->see('end');
> }
> else {
> $text->insert( 'end', "Connection Closed\n" );
> $text->see('end');
> $client->close();
> }
> }
>
>
> A client (as simple as I could maker it)
> #!/usr/bin/perl
> use IO::Socket;
>
> my $machine_addr = 'localhost';
> $sock = new IO::Socket::INET(PeerAddr=>$machine_addr,
> PeerPort=>7777,
> Proto=>'tcp',
> );
>
> die "Could not connect: $!" unless $sock;
>
> foreach my $count(1..100){
> print $sock "$count\n";
> print "$count\n";
> #select(undef,undef,undef,.1) ;
> }
>
> close ($sock);
Ok, this is an example of a threaded tk gui. Here we only print to
the console but you should be able to adapt this to suit your needs.
#!/usr/bin/perl
use strict;
use warnings;
use threads;
use threads::shared;
use Tk;
my (%shash, %threads, $mw,);
#initialize thread shared memory and gui
init();
#start gui
gui();
Tk::MainLoop();
#exit
foreach my $tId (keys %threads) {
$shash{$tId}{'die'} = 1;
sleep (1);
}
exit;
########################################################################
sub init #--------------------------------------------------------------
{
$mw = MainWindow->new();
#Example - one worker subroutine for one worker thread
foreach my $tId (1..1) {
foreach my $i qw(go1 progress die) {
share ($shash{$tId}{$i});
$shash{$tId}{$i} = 0;
}
$threads{$tId} = threads->new(\&worker1, $tId);
$threads{$tId}->detach();
warn "launched thread ($tId)\n";
}
return (1);
}
sub gui #---------------------------------------------------------------
{
my $c = 1;
foreach my $csv ('on,1', 'off,0') {
my ($label,$state) = split(/,/, $csv);
$mw->Button(
-text => $label,
-command => sub {$shash{1}{go1} = $state;}
)->pack();
}
return (1);
}
sub worker1 #-----------------------------------------------------------
{
my $tId = $_[0] || return (0);
local $| = 1;
warn "welcome to worker1 ($tId)\n";
workerLoop:
while (1) {
if ( $shash{$tId}{'die'} == 1) {
last;
};
if ( $shash{$tId}{'go1'} == 1 ) {
foreach my $num (1..10){
$shash{$tId}{'progress'} = $num;
warn "\tThread (".$tId.") says: ($tId->$num)\n";
if($shash{$tId}{'go1'} == 0) { last; }
if($shash{$tId}{'die'} == 1) { last workerLoop; };
sleep(1);
}
$shash{$tId}{'go01'} = 0;
}
else {
sleep(1);
}
}
warn "thread ($tId) is exiting worker1\n";
return (1);
}
########################################################################
hTh,
J
------------------------------
Date: Wed, 23 Mar 2011 07:18:27 +0000 (UTC)
From: pacman@kosh.dhis.org (Alan Curry)
Subject: Re: using File::Find
Message-Id: <imc6s2$15b$1@speranza.aioe.org>
In article <8ust1tFaaU1@mid.individual.net>, Uno <Uno@example.invalid> wrote:
>I just installed perldoc on my machine and wanted to go take a look at
I'm going to ignore the weird leaps of logic that allowed you to make the
journey from from "I just installed perldoc" to the attempt to write a script
to find the newest installed man page. The script itself is interesting
enough to comment on.
>
>$ perl find1.pl
>Use of uninitialized value in numeric gt (>) at find1.pl line 7.
>Use of uninitialized value in numeric gt (>) at find1.pl line 7.
>Use of uninitialized value in numeric gt (>) at find1.pl line 7.
>/usr/share/man/man1 Tue Mar 22 17:08:00 2011
>$ cat find1.pl
>#! usr/bin/perl -w
>use strict;
>use File::Find;
>@ARGV = ('/usr/share/man/man1') unless @ARGV;
>my ($age, $name);
>sub youngest {
> return if defined $age && $age > -M;
> $age = (stat(_))[9];
> $name = $File::Find::name;
>}
>find(\&youngest, @ARGV);
>print "$name " . scalar(localtime($age)) . "\n";
>$
The most interesting bug in the script is that you're comparing a value
returned by -M to a value (in $age) that came from (stat(_))[9]. Those are
both modification times, but one of them measured in seconds, counting
forward from 1970, and the other one is measured in days, counting backward
from the time the script started running. Pick one of those and use it
consistently. (I'd pick stat. -M is just too weird for anything but golfing)
The next bug is hinted at by the uninitialized value warnings. Since you've
tested $age for definedness before comparing, the only thing that can be
causing the warning is that -M is returning undef. You must have some
dangling symlinks in that directory. To make your script handle dangling
symlinks correctly, you could use (lstat)[9] or you could check for the undef
timestamp and just skip them. Depends on how you want to handle symlinks in
general. File::Find has some options related to symlink following that you
might want to enable.
>
>It seems to me that $name should be giving me the name of a file in the
>directory, not the directory itself. It also seems to me unlikely that
>this directory would be born today, and later than its contents.
Wow, the densely packed misconceptions! First of all, in File::Find, just as
in find(1), the "directory itself" is a legitimate part of the search output.
There's no reason why "/usr/share/man/man1" can't be the answer to "what is
the youngest file found under /usr/share/man/man1?"... Directories are files
too. If you want to exclude them, put "return if -d" at the top of your
filter function.
Secondly, -M and (stat)[9] are modification times, not birth times. It's
easily possible for a directory to be newer than any file inside it, since a
directory is modified whenever a file is added to the directory or removed
from it.
The time the directory was "born" would not be recorded in a traditional unix
filesystem. Recently some unix filesystems have been created which do record
"birthtime", but since they were not around when perl was invented, perl
doesn't have an easy way of accessing those timestamps. (None that I can find
anyway - looking under -X and stat in perlfunc(1) and also at File::stat(3) I
don't see any mention of birthtime)
If birthtime of the files is what you're after, you'll probably find
modification time to be a poor substitute. I have an installed man page with
a modification time of 15:51:31, December 10, 1992, several times older than
the computer I'm using. Imagine the path that file has taken to get to me! It
must have been compressed and uncompressed with algorithms no longer used,
passed around from FTP mirror to FTP mirror on OSes no longer remembered,
copied from hard drive to tape, CD, and DVD and back a few times, put into
tarballs and other containers and taken back out again, and through all that
it was never modified.
The point of that story is: mtime applies to file contents, not file
location. The mtime of an installed man page is likely to be the time that
it was last modified by the author, not the timestamp of installation on your
machine.
In cases like that, ctime can be a better substitute, as long as you don't do
a lot of chmod'ing of things after they're installed.
Oh and just use ls -ltr next time.
--
Alan Curry
------------------------------
Date: Wed, 23 Mar 2011 11:26:56 +0100
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: using File::Find
Message-Id: <slrniojing.m4h.hjp-usenet2@hrunkner.hjp.at>
On 2011-03-23 00:26, Uno <Uno@example.invalid> wrote:
> I just installed perldoc on my machine and wanted to go take a look at
> it, to see where it is and what it looks like. For example, I wrote:
>
> $ whereis perlretut
> perlretut: /usr/share/man/man1/perlretut.1.gz
> $
Whereis looks only in a few directories. You may want to use find or
locate instead.
[...]
> $ perl find1.pl
> Use of uninitialized value in numeric gt (>) at find1.pl line 7.
> Use of uninitialized value in numeric gt (>) at find1.pl line 7.
> Use of uninitialized value in numeric gt (>) at find1.pl line 7.
> /usr/share/man/man1 Tue Mar 22 17:08:00 2011
> $ cat find1.pl
> #! usr/bin/perl -w
> use strict;
> use File::Find;
> @ARGV = ('/usr/share/man/man1') unless @ARGV;
> my ($age, $name);
> sub youngest {
> return if defined $age && $age > -M;
> $age = (stat(_))[9];
This is confused: (stat(_))[9] returns a timestamp (expressed in seconds
since the epoch), not an age. -M returns the age in days. You cannot
meaningfully compare them. Since the timestamp of any file is likely to
be much greater than the age of any file of the system you will always
get the name and mtime of the first file (i.e. the directory you
specified).
> $name = $File::Find::name;
> }
> find(\&youngest, @ARGV);
> print "$name " . scalar(localtime($age)) . "\n";
> $
>
> It seems to me that $name should be giving me the name of a file in the
> directory, not the directory itself. It also seems to me unlikely that
> this directory would be born today, and later than its contents.
It wasn't "born" today, but it was last modified today. You just
installed a package, didn't you? The package presumably contained a
manpage. The last modified date of the manpage is almost certainly older
than the directory. So the output is probably correct even if the script
is not.
> So 2 questions.
> q1) How do I re-write this so that it outputs the filename?
Which filename?
> q2) I seem to get a varying number of warnings on "use of uninitialized
> value" depending on the directory it runs in. What does it mean?
Line 7 is this one:
> return if defined $age && $age > -M;
Now where could an "uninitialized value in numeric gt (>)" in this line
occur? There is only one > in this line, so it can only be $age or -M.
It can't be $age because you test whether that's defined. So it can only
be the return value of -M. Now check the docs to find out when -M can
return undef.
hp
------------------------------
Date: Wed, 23 Mar 2011 06:34:15 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: using File::Find
Message-Id: <g1tjo6prr8m0cs834d9ipgplta63sof6rg@4ax.com>
Uno <Uno@example.invalid> wrote:
>On 03/22/2011 09:09 PM, Randal L. Schwartz wrote:
>>>>>>> "Jürgen" == Jürgen Exner<jurgenex@hotmail.com> writes:
>>
>> Jürgen> Didn't you mean
>> Jürgen> perldoc File::Find
>> Jürgen> maybe?
>>
>> Oh, sorry. I have tools that make it so that "man File::Find" works.
>
>Does your perl documentation survive the latest install? Although I'm
>not a detached observer, I would say that mine did not.
???
Would you mind explaining what you are rambling about? It's the second
or third time that you are making some claim about perl documentation
and some installation of something. INSTALLATION OF WHAT?
If by chance you are talking about installation of a new Perl version
(you didn't say!!!) then it depends. If I deleted the old Perl version,
then of course the old documentation is gone, too, just as it should be.
If I didn't delete the old Perl version, then of course the old
documentation is still available, too. In either case, the new version
of Perl automatically comes with its new *matching* version of the docs
anyway. And that's the one you want to use. So what's the point in
babbling about survival of the [old] Perl documentation?
jue
------------------------------
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:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#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 3329
***************************************
