[23704] in Perl-Users-Digest

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

Perl-Users Digest, Issue: 5910 Volume: 10

daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Dec 8 06:05:40 2003

Date: Mon, 8 Dec 2003 03:05:08 -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           Mon, 8 Dec 2003     Volume: 10 Number: 5910

Today's topics:
    Re: can some one please explain this regex?! (Tad McClellan)
    Re: can some one please explain this regex?! <geoff.cox@blueyonder.co.uk>
    Re: can some one please explain this regex?! <me@privacy.net>
    Re: Do we just use different file handles when we want  <matthew.garrish@sympatico.ca>
    Re: Generating Day of Week in Pure Perl <bigiain@mightymedia.com.au>
    Re: How to open a file from the end and read the last 1 <nmihai_year_2000@yahoo.com>
    Re: How to open a file from the end and read the last 1 <bigiain@mightymedia.com.au>
    Re: How to write to drive A:\ from CGI Perl <asu1@c-o-r-n-e-l-l.edu>
    Re: How to write to drive A:\ from CGI Perl <henq _ replace 0 by o <hvtijen@h0tmail.c0m>>
    Re: How to write to drive A:\ from CGI Perl <matthew.garrish@sympatico.ca>
    Re: How to write to drive A:\ from CGI Perl (Cle)
        HTML::Lint vs. XML (Jesse Sheidlower)
    Re: HTML::Lint vs. XML <flavell@ph.gla.ac.uk>
    Re: Idiom for array index that I'm foreach'ing over? <bigiain@mightymedia.com.au>
    Re: Overloading <usenet@morrow.me.uk>
        Perl dump and undump <wjbel@pacbell.net>
    Re: Perl dump and undump <asu1@c-o-r-n-e-l-l.edu>
    Re: Perl dump and undump <asu1@c-o-r-n-e-l-l.edu>
    Re: Perl dump and undump <wjbel@pacbell.net>
    Re: Perl dump and undump <matthew.garrish@sympatico.ca>
        Perl2EXE vs. PAR vs. perlcc <ralphk@nospam_vacb.org>
    Re: Perl2EXE vs. PAR vs. perlcc <kalinaubears@iinet.net.au>
    Re: Perl2EXE vs. PAR vs. perlcc <bobx@linuxmail.org>
    Re: read file with while and then scan lines into array (Martin Foster)
        Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)

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

Date: Sun, 7 Dec 2003 17:59:08 -0600
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: can some one please explain this regex?!
Message-Id: <slrnbt7fmc.l1p.tadmc@magna.augustmail.com>

Geoff Cox <geoff.cox@blueyonder.co.uk> wrote:

> open(DATA, "$namehtml");
             ^         ^

   perldoc -q vars

       What's wrong with always quoting "$vars"?


The DATA filehandle is special, I leave it for its special uses,
choose some other name.


You should always, yes *always*, check the return value from open():

    open(NAME, $namehtml) or die "could not open '$namehtml'  $!";




[ snip 150 lines of full-quote. Please stop doing that. Soon. ]

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


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

Date: Mon, 08 Dec 2003 08:29:12 +0000
From: Geoff Cox <geoff.cox@blueyonder.co.uk>
Subject: Re: can some one please explain this regex?!
Message-Id: <dkc8tvcm8v7l0g01pe28cei29rj61b1tqb@4ax.com>

On Sun, 7 Dec 2003 17:59:08 -0600, tadmc@augustmail.com (Tad
McClellan) wrote:

>Geoff Cox <geoff.cox@blueyonder.co.uk> wrote:
>
>> open(DATA, "$namehtml");
>             ^         ^
>
>   perldoc -q vars
>
>       What's wrong with always quoting "$vars"?

Tad,  not sure what you mean above?


>The DATA filehandle is special, I leave it for its special uses,
>choose some other name.

OK will do.

>You should always, yes *always*, check the return value from open():
>
>    open(NAME, $namehtml) or die "could not open '$namehtml'  $!";

Thanks for the reminder.

>[ snip 150 lines of full-quote. Please stop doing that. Soon. ]

ditto..

Geoff



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

Date: Mon, 8 Dec 2003 22:28:36 +1300
From: "Tintin" <me@privacy.net>
Subject: Re: can some one please explain this regex?!
Message-Id: <br1g9p$26h4bv$1@ID-172104.news.uni-berlin.de>


"Geoff Cox" <geoff.cox@blueyonder.co.uk> wrote in message
news:dkc8tvcm8v7l0g01pe28cei29rj61b1tqb@4ax.com...
> On Sun, 7 Dec 2003 17:59:08 -0600, tadmc@augustmail.com (Tad
> McClellan) wrote:
>
> >Geoff Cox <geoff.cox@blueyonder.co.uk> wrote:
> >
> >> open(DATA, "$namehtml");
> >             ^         ^
> >
> >   perldoc -q vars
> >
> >       What's wrong with always quoting "$vars"?
>
> Tad,  not sure what you mean above?

Have you read what it says?  Is there something you don't understand in the
documentation?




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

Date: Mon, 8 Dec 2003 00:21:09 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Do we just use different file handles when we want to have multiple files open at the same time...?
Message-Id: <6TTAb.6796$3y1.505664@news20.bellglobal.com>


"James Willmore" <jwillmore@remove.adelphia.net> wrote in message
news:20031207121845.1c9a4183.jwillmore@remove.adelphia.net...
> On Sun, 07 Dec 2003 17:15:32 GMT
> "Guy" <someone@somewhere.nb.ca> wrote:
>
> > To have many files open at the same time, do I just use a different
> > file handle like this:
> >
> > open(FILEA,"$stopfil");
> > open(FILEB,"$startfil");
> >
> > # some extra code goes here
> >
> > close(FILEA);
> > close(FILEB);
> >
> > Or are there other things that have to be done also.
>
> That will work.  However, I'd check to see if you actually opened the
> file.
>
> open(FILEA,"$stopfil") or die "Open failed for $stopfil: $!\n";
> open(FILEB,"$startfil") or die "Open failed for $starfil: $!\n";
>

I'd also drop the useless quotes:

open(FILEA, $stopfil) or die "Open failed for $stopfil: $!\n";
open(FILEB, $startfil) or die "Open failed for $starfil: $!\n";

Matt




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

Date: Mon, 08 Dec 2003 16:22:17 +1100
From: Iain Chalmers <bigiain@mightymedia.com.au>
Subject: Re: Generating Day of Week in Pure Perl
Message-Id: <bigiain-60EF2B.16221708122003@news.fu-berlin.de>

In article <9prtsvk8n3s9o0h8dj8vs8gajk119ii1bh@4ax.com>,
 Bart Lateur <bart.lateur@pandora.be> wrote:

> Iain Truskett wrote:
> 
> >* rev <rev@TheWaterCooler.com>:
> >
> >> I cannot use the POSIX package.
> >
> >Why?
> 
> For the same reason he can't use any other module. The ISP probably
> deleted it and isn't willing to install it again.

Or because the homework assignment specifically said he can't...

;-)

big

-- 
'When I first met Katho, she had a meat cleaver in one hand and
half a sheep in the other. "Come in", she says, "Hammo's not here.
I hope you like meat.' Sharkey in aus.moto


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

Date: Mon, 08 Dec 2003 00:02:39 GMT
From: "Mihai N." <nmihai_year_2000@yahoo.com>
Subject: Re: How to open a file from the end and read the last 100 lines
Message-Id: <Xns944AA3472FE47MihaiN@63.240.76.16>

> Problem is ... you have been *told* which module will work :-)  So,
> evaluation of a module that *works* doesn't appear to be something you
> *need* to do.
> 
> It would be a different story if you *didn't* know which module would
> work - but the author (no less) of a working module has told you it
> works and why you should use it.
"I" was not told. I am not the original poster.

> So, what's the problem with using it?  Have you even *looked* at it? 
> If you "evaluated" the module and found it doesn't work for you, have
> you let the author know this?

There is no problem using it. I am pretty sure it does it's work pretty well.
And I was not talking about this special case.

If you need the script to work without installing other 20 modules
from CPAN, this will do.

I was talking about the principle of checking CPAN for trivial problems.
Don't get me wrong, this may not be a trivial problem if you have to run
this script on GB or TB of data, several times a minute/second.
But if you run it once a day/week on some MB, should be ok.

The main think is productivity and what I am advocating is "balance."
Sometimes is faster/better your own, sometimes some CPAN module.
Decide when to go for one or the other is the difficult part.

-- 
Mihai
-------------------------
Replace _year_ with _ to get the real email


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

Date: Mon, 08 Dec 2003 16:11:26 +1100
From: Iain Chalmers <bigiain@mightymedia.com.au>
Subject: Re: How to open a file from the end and read the last 100 lines
Message-Id: <bigiain-8E7AB1.16112608122003@news.fu-berlin.de>

In article <x7wu9bykqj.fsf@mail.sysarch.com>,
 Uri Guttman <uri@stemsystems.com> wrote:

> >>>>> "TA" == Tore Aursand <tore@aursand.no> writes:
> 
>   TA> On Thu, 04 Dec 2003 18:05:50 +0000, Uri Guttman wrote:
>   >>> I am writing some Perl script to check some patterns errors in an
>   >>> alert log (Oracle alert log).  The file can't get quite large.
>   >>> Therefore I would like write a Perl script that runs every day via at
>   >>> and opens the file from the end to read the last 100 lines. How can I
>   >>> do this?
> 
>   >> use File::ReadBackawards ;
> 
>   TA> *bzzzt*  Should be 'File::ReadBackwards'.
> 
> bah!
> 
> it is a module that tells you who won awards in reverse order! :)

Heh, I still reckon it _should_ have been called File::sdrawkcaBdaeR

big

-- 
'When I first met Katho, she had a meat cleaver in one hand and
half a sheep in the other. "Come in", she says, "Hammo's not here.
I hope you like meat.' Sharkey in aus.moto


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

Date: 7 Dec 2003 23:30:21 GMT
From: "A. Sinan Unur" <asu1@c-o-r-n-e-l-l.edu>
Subject: Re: How to write to drive A:\ from CGI Perl
Message-Id: <Xns944ABC418569Basu1cornelledu@132.236.56.8>

canle@lecan.com (Cle) wrote in 
news:8a21e493.0312071321.4d5de54e@posting.google.com:

> I will look forward to buy your best. I will introduce my best Perl
> script, which is better than the one that I am posting in my website,
> then you may loose at least a customer and may more online buyers like
> me, because you write Perl better than many others, and you will
> nerver know that someday, one person out there can do it,

May I politely suggest you return to whereever you came from? You are not 
making any sense at all. What customers are we going to lose?

> as replied by:
> 
> Sinan: Easy! !  : #! C:/Perl/bin/perl.exe ....

I said no such thing. Here is an idea: If you do not have anything 
meaningful to say, please do not hesitate not to say it. 

This would actually be funny if you did not have:

"with experiences in HTML, CGI, and PERL"

in your resume. 
(http://www.lecan.com/cgi-bin/cgiwrap/canle/message5.cgi)

-- 
A. Sinan Unur
asu1@c-o-r-n-e-l-l.edu
Remove dashes for address
Spam bait: mailto:uce@ftc.gov


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

Date: Mon, 8 Dec 2003 00:52:57 +0100
From: "henq" <henq _ replace 0 by o <hvtijen@h0tmail.c0m>>
Subject: Re: How to write to drive A:\ from CGI Perl
Message-Id: <3fd3bd59$0$416$1b62eedf@news.wanadoo.nl>


"A. Sinan Unur" <asu1@c-o-r-n-e-l-l.edu> wrote in
news:Xns944ABC418569Basu1cornelledu@132.236.56.8...
> canle@lecan.com (Cle) wrote in
> news:8a21e493.0312071321.4d5de54e@posting.google.com:
>
> This would actually be funny if you did not have:
>
> "with experiences in HTML, CGI, and PERL"
>
> in your resume.
> (http://www.lecan.com/cgi-bin/cgiwrap/canle/message5.cgi)


Perhaps you want to trade Cle some perl advice in exchange for one of his 5
copyrights?:

 "Holding 5 copyrights : Variable Pi formula, Multiplication & Division
 Integrations, PVT Gas Process with 2 new rules in thermodynamics, Labor
 Expansion in economics, Word Processor with Math & Graphics.




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

Date: Sun, 7 Dec 2003 21:45:27 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: How to write to drive A:\ from CGI Perl
Message-Id: <bBRAb.5703$3y1.440449@news20.bellglobal.com>


"A. Sinan Unur" <asu1@c-o-r-n-e-l-l.edu> wrote in message
news:Xns944ABC418569Basu1cornelledu@132.236.56.8...
>
> I said no such thing. Here is an idea: If you do not have anything
> meaningful to say, please do not hesitate not to say it.
>
> This would actually be funny if you did not have:
>
> "with experiences in HTML, CGI, and PERL"
>
> in your resume.


Wouldn't this qualify as an experience in Perl?

Matt




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

Date: 8 Dec 2003 02:37:40 -0800
From: canle@lecan.com (Cle)
Subject: Re: How to write to drive A:\ from CGI Perl
Message-Id: <8a21e493.0312080237.47885c85@posting.google.com>

Sinan:

Cle did not have 15 years of experinces in Perl, even he had bought 5
books and online readings in Perl, with books in Linux, such
experience can recommand a book for newbie, not yet for CGI Perl:

Paul Haffman, author of Netscape 4 and Perl for Dummies, page 175:
 open(IN, "D:\ORDERS\DATA\JAN97.DAT"); 

Cle thank you all!

Sinan in first reply for this topic, article #4:

>Easy:

>#! C:/Perl/bin/perl.exe -T
>
>use strict;
>use warnings;
>
>my $fn = 'output.txt';
>open(AFILE, ">", $fn) or die "Cannot open $fn: $!\n";
>print AFILE 'Output';
>close(AFILE) or die "Cannot close $fn: $!\n";
>__END__
>
>This will create the file output.txt on the server's A: drive
provided
>you remembered to put a floppy in there.
----------------------------

"A. Sinan Unur" <asu1@c-o-r-n-e-l-l.edu> wrote in message
news:Xns944ABC418569Basu1cornelledu@132.236.56.8...
>
> I said no such thing. Here is an idea: If you do not have anything
> meaningful to say, please do not hesitate not to say it.
>
> This would actually be funny if you did not have:
>
> "with experiences in HTML, CGI, and PERL"
>
> in your resume.


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

Date: 7 Dec 2003 19:40:18 -0500
From: jester@panix.com (Jesse Sheidlower)
Subject: HTML::Lint vs. XML
Message-Id: <br0h9i$eok$1@panix2.panix.com>


I've just started doing some real testing on my scripts,
and I've run into a problem already. I am trying to test
a generated Web page using WWW::Mechanize and Test::HTML::Lint,
following some posted suggestions from Andy Lester. But I'm
getting an error that doesn't seem to be described in the
Lint docs.

I generate my page using standard CGI.pm functions (via
Template Toolkit), starting with CGI::header and 
CGI::start_html, which generates text beginning:

---
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html
	  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
	   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>...
---

I then point at this the following test script:

---
#!/usr/bin/perl -w
use Test::More qw(no_plan);
use Test::HTML::Lint;
use WWW::Mechanize;

my $mech = WWW::Mechanize->new();
isa_ok( $mech, "WWW::Mechanize" ) or die;
$mech->get( "http://127.0.0.1/cgi-bin/test/search.cgi" );
is ($mech->status, 200, "Fetched OK" );
html_ok( $mech->content, "Login page HTML" );
---

which produces the following test results:

---
ok 1 - The object isa WWW::Mechanize
ok 2 - Fetched OK
not ok 3 - Login page HTML
#     Failed test (02libloading.t at line 10)
# Errors: Login page HTML
#  (7:1) Unknown attribute "xmlns" for tag <html>
#  (7:1) Unknown attribute "xml:lang" for tag <html>
1..3
# Looks like you failed 1 tests of 3.
---

What do I need to do to get Lint to accept this as valid HTML?

Thanks.

Jesse Sheidlower


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

Date: Mon, 8 Dec 2003 01:22:36 +0000
From: "Alan J. Flavell" <flavell@ph.gla.ac.uk>
Subject: Re: HTML::Lint vs. XML
Message-Id: <Pine.LNX.4.53.0312080109290.19459@ppepc56.ph.gla.ac.uk>

On Mon, 7 Dec 2003, Jesse Sheidlower wrote:

> <?xml version="1.0" encoding="iso-8859-1"?>
> <!DOCTYPE html
> 	  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> 	   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
[..]
> What do I need to do to get Lint to accept this as valid HTML?

I can't answer the specific question, sorry, but you're surely aware
that it is _not_ "valid HTML"?

Appendix C of XHTML/1.0 describes a kludge whereby XHTML can be
force-fed to tag-soup slurpers on the pretext of it being HTML;  but
it wouldn't fool a formal validator.[1]

Apologies if you already knew that and it was just a slip of
the keyboard.  But the documentation for Lint doesn't seem to mention
XHTML, and the stuff it's complaining about, doesn't happen in HTML
/per se/.

Hope this is vaguely useful.


[1] and is rated by many to have been a distinctly bad idea.  But
that's even more OT here.


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

Date: Mon, 08 Dec 2003 15:50:13 +1100
From: Iain Chalmers <bigiain@mightymedia.com.au>
Subject: Re: Idiom for array index that I'm foreach'ing over?
Message-Id: <bigiain-AA9A43.15501308122003@news.fu-berlin.de>

In article <bqqot6$m39$1@mamenchi.zrz.TU-Berlin.DE>,
 anno4000@lublin.zrz.tu-berlin.de (Anno Siegel) wrote:

> I think only a purist would complain about the use of $i and %i here.

But remember, you're helping out a _Fortran_ guy here... $i as an array 
index, sure - but as a *hash* name???

:-)

big

-- 
'When I first met Katho, she had a meat cleaver in one hand and
half a sheep in the other. "Come in", she says, "Hammo's not here.
I hope you like meat.' Sharkey in aus.moto


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

Date: Mon, 8 Dec 2003 00:13:19 +0000 (UTC)
From: Ben Morrow <usenet@morrow.me.uk>
Subject: Re: Overloading
Message-Id: <br0fmv$k5l$1@wisteria.csv.warwick.ac.uk>


"Jim Keenan" <no_spam_for_jkeen@verizon.net> wrote:
> Okay ... so then I went back to your original posting and copied-and-pasted
> your code exactly as you typed it.  When I ran it, I was unable to reproduce
> the first of the two problems you cited:

They're not exactly 'problems', more things I am curious to know the
reason for..

> >    1. Why is 'numify' called twice for int($i)?
> 
> >   numify
> >   Argument "*" isn't numeric in addition (+) at ./op line 15.
> >   numify
> >   Argument "*" isn't numeric in addition (+) at ./op line 15.
> >   0
> 
> I did not get the first 2 lines -- only the last 3.

Interesting. Which version of perl is this? I'm using 5.8.2.

Ben

-- 
It will be seen that the Erwhonians are a meek and long-suffering people,
easily led by the nose, and quick to offer up common sense at the shrine of
logic, when a philosopher convinces them that their institutions are not based 
on the strictest morality.  [Samuel Butler, paraphrased]       ben@morrow.me.uk


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

Date: Mon, 08 Dec 2003 03:11:02 GMT
From: wjbell <wjbel@pacbell.net>
Subject: Perl dump and undump
Message-Id: <aZRAb.66989$5m1.61914@newssvr25.news.prodigy.com>

I've seen messages where you can use perl to dump a script to a core 
file and use undump to create an executable from it.

Where can I find undump?  I'm running redhat 7.1 and perl 5.8.2.


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

Date: 8 Dec 2003 03:41:08 GMT
From: "A. Sinan Unur" <asu1@c-o-r-n-e-l-l.edu>
Subject: Re: Perl dump and undump
Message-Id: <Xns944AE6C66C60Dasu1cornelledu@132.236.56.8>

wjbell <wjbel@pacbell.net> wrote in news:aZRAb.66989$5m1.61914
@newssvr25.news.prodigy.com:

> I've seen messages where you can use perl to dump a script to a core 
> file and use undump to create an executable from it.

I am not sure what you mean by 'core file', but if you are looking for 
usage examples on Data::Dumper; you can find them at:

http://search.cpan.org/dist/Data-Dumper/Dumper.pm#EXAMPLES
 
> Where can I find undump?  I'm running redhat 7.1 and perl 5.8.2.

Or maybe you are thinking of eval?

C:\Home> cat ttt
print "tttt\n"; 

C:\Home> cat ttt.pl
use strict;
use warnings;

open TTT, "<", 'ttt' or die "Cannot open ttt: $!\n";
my $script;
{
        local $/;
        $script = <TTT>;
}
close TTT or die "Cannot close ttt: $!\n";

eval $script;
die $@ if $@;
__END__

C:\Home> ttt.pl
tttt
-- 
A. Sinan Unur
asu1@c-o-r-n-e-l-l.edu
Remove dashes for address
Spam bait: mailto:uce@ftc.gov


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

Date: 8 Dec 2003 03:47:14 GMT
From: "A. Sinan Unur" <asu1@c-o-r-n-e-l-l.edu>
Subject: Re: Perl dump and undump
Message-Id: <Xns944AE7CE98C05asu1cornelledu@132.236.56.8>

"A. Sinan Unur" <asu1@c-o-r-n-e-l-l.edu> wrote in 
news:Xns944AE6C66C60Dasu1cornelledu@132.236.56.8:

> wjbell <wjbel@pacbell.net> wrote in news:aZRAb.66989$5m1.61914
> @newssvr25.news.prodigy.com:

>> Where can I find undump?  I'm running redhat 7.1 and perl 5.8.2.

Note to self: Check the FAQ before replying! Sorry about my previous post.

See http://www.perldoc.com/perl5.8.0/pod/perlfaq3.html#How-can-I-make-my-
Perl-program-run-faster-

The undump program was an old attempt to speed up your Perl program by 
storing the already-compiled form to disk. This is no longer a viable 
option, as it only worked on a few architectures, and wasn't a good 
solution anyway. 

-- 
A. Sinan Unur
asu1@c-o-r-n-e-l-l.edu
Remove dashes for address
Spam bait: mailto:uce@ftc.gov


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

Date: Mon, 08 Dec 2003 03:53:57 GMT
From: wjbell <wjbel@pacbell.net>
Subject: Re: Perl dump and undump
Message-Id: <pBSAb.34642$L%5.6909@newssvr29.news.prodigy.com>

A. Sinan Unur wrote:

> Note to self: Check the FAQ before replying! Sorry about my previous post.
> 
> See http://www.perldoc.com/perl5.8.0/pod/perlfaq3.html#How-can-I-make-my-
> Perl-program-run-faster-
> 
> The undump program was an old attempt to speed up your Perl program by 
> storing the already-compiled form to disk. This is no longer a viable 
> option, as it only worked on a few architectures, and wasn't a good 
> solution anyway. 
> 

Ok, thanks for the reply.


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

Date: Sun, 7 Dec 2003 22:23:39 -0500
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Perl dump and undump
Message-Id: <_8SAb.5743$3y1.456827@news20.bellglobal.com>


"wjbell" <wjbel@pacbell.net> wrote in message
news:aZRAb.66989$5m1.61914@newssvr25.news.prodigy.com...
> I've seen messages where you can use perl to dump a script to a core
> file and use undump to create an executable from it.
>
> Where can I find undump?  I'm running redhat 7.1 and perl 5.8.2.

Start with the faqs:

http://www.perl.com/doc/manual/html/pod/perlfaq3.html#What_is_undump_

You're going to be disappointed, though.

Matt




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

Date: Sun, 07 Dec 2003 18:26:48 -0500
From: Ralph K <ralphk@nospam_vacb.org>
Subject: Perl2EXE vs. PAR vs. perlcc
Message-Id: <OGOAb.461$eg3.34795@news.uswest.net>

Before committing the time and effort to try one of these methods of 
producing compiled perl programs, I'd welcome the observations, 
experiences and warnings from those who have gone before.



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

Date: Mon, 08 Dec 2003 11:12:15 +1100
From: Sisyphus <kalinaubears@iinet.net.au>
Subject: Re: Perl2EXE vs. PAR vs. perlcc
Message-Id: <3fd3c2ad$0$1751$5a62ac22@freenews.iinet.net.au>

Ralph K wrote:
> Before committing the time and effort to try one of these methods of 
> producing compiled perl programs, I'd welcome the observations, 
> experiences and warnings from those who have gone before.
> 

Forget perlcc.

Try PAR first. It doesn't yet handle all situations on all operating 
systems. If it doesn't do the job you need, report the bug to the PAR 
mailing list (see http://lists.perl.org ) and try perl2exe (or Active 
State's perlapp from their PDK).

Cheers,
Rob

-- 
To reply by email u have to take out the u in kalinaubears.



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

Date: Mon, 08 Dec 2003 00:36:00 GMT
From: Robert <bobx@linuxmail.org>
Subject: Re: Perl2EXE vs. PAR vs. perlcc
Message-Id: <QHPAb.815$Zq2.722179@news2.news.adelphia.net>

Ralph K wrote:

> Before committing the time and effort to try one of these methods of 
> producing compiled perl programs, I'd welcome the observations, 
> experiences and warnings from those who have gone before.
> 
I have only recently used PAR on Windows but I found no problems with it.

PerlCC did not work at all.


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

Date: 7 Dec 2003 21:11:30 -0800
From: mdfoster44@netscape.net (Martin Foster)
Subject: Re: read file with while and then scan lines into array
Message-Id: <6a20f90a.0312072111.2dae23d5@posting.google.com>

Thanks!  I'll try this out.
 
> Here is a solution which (a) assumes that the target lines all follow a
> pattern of "unsigned integers separated by a single whitespace" and (b)
> stores the results in a hash of arrays of arrays.  I leave to you the task
> of feeding this into MySQL.
> 
> jimk
> 
> ##### START CODE BLOCK #################
> #!/usr/bin/perl
> use strict;
> use warnings;
> use Data::Dumper;
> 
> my (@chunks, %results);
> {
>     local $/ = "\n\n";    # slurp data in by 'paragraphs'
>     while (<DATA>) {
>         next unless /_iza_sc_CoordinationSequence/;    # ignore all chunks
> except ones that contain this string
>         push (@chunks, $_);
>     }
> }
> 
> for (my $i = 0; $i <= $#chunks; $i++) {
>     my (@lines, @sequences);
>     @lines = split(/\n/, $chunks[$i]);
>     foreach my $line (@lines) {
>         if ($line =~ /^(\d+\s)+\d+\s*$/) {
>             push(@sequences, [ split(/\s/, $line) ]);
>         }
>     }
>  $results{$i} = [@sequences];
> }
> 
> print Dumper(\%results);
> 
> __DATA__
> loop_
> _iza_sc_CoordinationSequence
> 1 4 9 17 28 42 60 82 111 149 191 229 262 297 336 384
> 1 4 10 19 30 44 63 89 121 155 188 221 258 302 355 415
> 1 4 9 18 32 49 68 89 114 144 179 221 267 314 364 417
> 
> loop_
> _iza_sc_VertexSymbols
> 4.6.4.6.4.6
> 4.4.6.6.6.8_{3}
> 4.4.4.6.8.12
> 
> loop_
> _iza_sc_SomethingElse
> 3 7 9 17 28 42 60 82 111 149 191 229 262 297 336 384
> 3 7 10 19 30 44 63 89 121 155 188 221 258 302 355 415
> 3 7 9 18 32 49 68 89 114 144 179 221 267 314 364 417
> 
> loop_
> _iza_sc_CoordinationSequence
> 5 8 9 17 28 42 60 82 111 149 191 229 262 297 336 384
> 5 8 10 19 30 44 63 89 121 155 188 221 258 302 355 415
> 5 8 9 18 32 49 68 89 114 144 179 221 267 314 364 417
> 
> ##### END CODE BLOCK #################
> 
> If we were playing Perl Golf and wanted to trade off readability for
> brevity, we could re-write the 'for' loop as:
> 
> for (my $i = 0; $i <= $#chunks; $i++) {
>     my (@sequences);
>     foreach (split(/\n/, $chunks[$i])) {
>         push(@sequences, [ split(/\s/) ]) if (/^(\d+\s)+\d+\s*$/);
>     }
>  $results{$i} = [@sequences];
> }


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

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.  

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


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