[30304] in Perl-Users-Digest
Perl-Users Digest, Issue: 1547 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri May 16 03:09:43 2008
Date: Fri, 16 May 2008 00:09:06 -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 Fri, 16 May 2008 Volume: 11 Number: 1547
Today's topics:
Re: arrow key bindings in perl debugger mode <mjcarman@mchsi.com>
Re: Need ideas on how to make this code faster than a s <getly@bentsys-INVALID.com>
Re: Need ideas on how to make this code faster than a s <1usa@llenroc.ude.invalid>
Re: Need ideas on how to make this code faster than a s chadda@lonemerchant.com
Re: Need ideas on how to make this code faster than a s <1usa@llenroc.ude.invalid>
Re: Need ideas on how to make this code faster than a s chadda@lonemerchant.com
Re: Need ideas on how to make this code faster than a s <1usa@llenroc.ude.invalid>
Re: Need ideas on how to make this code faster than a s <jurgenex@hotmail.com>
Re: Need ideas on how to make this code faster than a s <jurgenex@hotmail.com>
Re: Need ideas on how to make this code faster than a s <uri@stemsystems.com>
new CPAN modules on Fri May 16 2008 (Randal Schwartz)
Permissions on a file kronecker@yahoo.co.uk
Re: Permissions on a file <1usa@llenroc.ude.invalid>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: regular expression question <jurgenex@hotmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 15 May 2008 23:32:33 GMT
From: Michael Carman <mjcarman@mchsi.com>
Subject: Re: arrow key bindings in perl debugger mode
Message-Id: <lK3Xj.165531$yE1.143307@attbi_s21>
andrew wrote:
> Hmm, these two modules are installed, but it's not exactly clear to me
> how to use them to customize key bindings.
Something else must be wrong, then. The default bindings for those keys
matches the functionality you wanted.
-mjc
------------------------------
Date: Thu, 15 May 2008 15:16:06 -0700
From: "Gordon Etly" <getly@bentsys-INVALID.com>
Subject: Re: Need ideas on how to make this code faster than a speeding turtle
Message-Id: <693r18F2vs0ciU1@mid.individual.net>
chadda@lonemerchant.com wrote:
> On May 15, 1:37 pm, Uri Guttman <u...@stemsystems.com> wrote:
> chadda <cha...@lonemerchant.com> writes:
> > i have to know if you could write this mess any slower? you are
> > doing
> > everything possible to slow you down.
> I know I shouldn't critize free help, but you seem to have some anger
> management issues.
He seems to constantly come across this way. I really wish he could see
things from other points of view.
...
As a simple answer, take a look at LWP:UserAgent
(http://search.cpan.org/~gaas/libwww-perl-5.812/lib/LWP/UserAgent.pm),
as a good start in the right direction.
--
G.Etly
------------------------------
Date: Thu, 15 May 2008 22:26:45 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Need ideas on how to make this code faster than a speeding turtle
Message-Id: <Xns9A9FBBA1CBD61asu1cornelledu@127.0.0.1>
"Gordon Etly" <getly@bentsys-INVALID.com> wrote in
news:693r18F2vs0ciU1@mid.individual.net:
> chadda@lonemerchant.com wrote:
>> On May 15, 1:37 pm, Uri Guttman <u...@stemsystems.com> wrote:
>> chadda <cha...@lonemerchant.com> writes:
>
>> > i have to know if you could write this mess any slower? you are
>> > doing
>> > everything possible to slow you down.
>
>> I know I shouldn't critize free help, but you seem to have some anger
>> management issues.
>
> He seems to constantly come across this way. I really wish he could
> see things from other points of view.
> ...
>
>
> As a simple answer, take a look at LWP:UserAgent
> (http://search.cpan.org/~gaas/libwww-perl-5.812/lib/LWP/UserAgent.pm),
> as a good start in the right direction.
All the OP needs is LWP::Simple and HTML::TableExtract.
In fact, I wrote a whole script that took only 0.8 seconds to download
and parse a single page (of course, with more id's in a file, the only
real limit on the speed is the network latency and transfer speed) but I
have decided not to post it as I do not know what his intentions are.
As for you, pick a posting id and stick with it.
PLONKETY PLONK!
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://www.rehabitation.com/clpmisc/
------------------------------
Date: Thu, 15 May 2008 16:06:25 -0700 (PDT)
From: chadda@lonemerchant.com
Subject: Re: Need ideas on how to make this code faster than a speeding turtle
Message-Id: <b0833433-862e-4895-8002-66c92cc53b15@w5g2000prd.googlegroups.com>
On May 15, 3:16 pm, "Gordon Etly" <ge...@bentsys-INVALID.com> wrote:
> cha...@lonemerchant.com wrote:
> > On May 15, 1:37 pm, Uri Guttman <u...@stemsystems.com> wrote:
> > chadda <cha...@lonemerchant.com> writes:
> > > i have to know if you could write this mess any slower? you are
> > > doing
> > > everything possible to slow you down.
> > I know I shouldn't critize free help, but you seem to have some anger
> > management issues.
>
> He seems to constantly come across this way. I really wish he could see
> things from other points of view.
> ...
>
> As a simple answer, take a look at LWP:UserAgent
> (http://search.cpan.org/~gaas/libwww-perl-5.812/lib/LWP/UserAgent.pm),
> as a good start in the right direction.
>
> --
> G.Etly
I just tried LWP, and now I can't get the code to work for the life of
me. Here is what I attempted
#!/usr/bin/perl -w
use LWP::UserAgent;
use HTTP::Request;
use HTTP::Cookies;
my ($read, $build, @product, @id, @sku, @upc, @weight);
my @temp;
open(IN, '<', 'input') || die "cant open: $!";
$read = <IN>;
chomp($read);
$build = 'http://www.doba.com/members/catalog/'.$read.'.html';
#@temp = `lynx -accept_all_cookies -dump $build`;
my $ua = LWP::UserAgent->new;
$ua->agent("OMEGA SPARC DESTROYER/69");
my $request = HTTP::Request->new('GET');
$request->url($build);
my $cookie_jar = HTTP::Cookies->new;
$cookie_jar->add_cookie_header($request);
my $response = $ua->request($request);
my $code = $response->code;
print $code;
@temp = $request->content;
@product = grep(/Product ID/, @temp);
@id = grep(/Item ID/, @temp);
@sku = grep(/SKU/, @temp);
@upc = grep(/UPC/, @temp);
@weight = grep(/Weight/, @temp);
print @product;
print @id;
print @sku;
print @upc;
print @weight;
% ./parse.pl
500%
------------------------------
Date: Thu, 15 May 2008 23:14:45 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Need ideas on how to make this code faster than a speeding turtle
Message-Id: <Xns9A9FC3C7ED11Casu1cornelledu@127.0.0.1>
chadda@lonemerchant.com wrote in
news:b0833433-862e-4895-8002-66c92cc53b15@w5g2000prd.googlegroups.com:
> On May 15, 3:16 pm, "Gordon Etly" <ge...@bentsys-INVALID.com> wrote:
>> cha...@lonemerchant.com wrote:
>> > On May 15, 1:37 pm, Uri Guttman <u...@stemsystems.com> wrote:
>> > chadda <cha...@lonemerchant.com> writes:
>> > > i have to know if you could write this mess any slower? you are
>> > > doing
>> > > everything possible to slow you down.
>> > I know I shouldn't critize free help, but you seem to have some
>> > anger management issues.
...
>> As a simple answer, take a look at LWP:UserAgent
>> (http://search.cpan.org/~gaas/libwww-perl-
5.812/lib/LWP/UserAgent.pm),
>> as a good start in the right direction.
...
> I just tried LWP, and now I can't get the code to work for the life of
> me. Here is what I attempted
As I mentioned elsewhere, all you need is LWP::Simple.
So, here is a fish for you:
C:\Temp> cat p.pl
#!/usr/bin/perl
use strict;
use warnings;
use HTML::TokeParser;
use LWP::Simple;
my ($input_file) = @ARGV;
die "No input file specified\n" unless defined $input_file;
open my $INPUT, '<', $input_file
or die "Cannot open '$input_file': $!";
ID:
while ( my $id = <$INPUT> ) {
chomp $id;
my $url = make_url( $id );
my $html = get $url;
unless ( defined $html ) {
warn "Error downloading from '$url'\n";
next ID;
}
my $parser = HTML::TokeParser->new( \$html );
TABLE:
while ( my $token = $parser->get_tag('table') ) {
if ( lc $token->[1]{id} eq 'product_details' ) {
my $td = $parser->get_tag('td');
last TABLE unless $td;
my $cell = $parser->get_text('/td');
my %data;
while ( $cell =~ /\s*([^:]+?):\s+(\d+)\s+/g ) {
$data{$1} = $2;
}
use Data::Dumper;
print Dumper \%data;
}
}
}
sub make_url {
return
sprintf q{http://www.doba.com/members/catalog/%s.html}, $_[0];
}
__END__
C:\Temp> timethis p list
$VAR1 = {
'Product ID' => '3308191',
'UPC' => '896207999816',
'Item ID' => '3653992',
'SKU' => '8930'
};
TimeThis : Command Line : p list
TimeThis : Start Time : Thu May 15 18:19:28 2008
TimeThis : End Time : Thu May 15 18:19:29 2008
TimeThis : Elapsed Time : 00:00:01.062
Comparing this to the overhead of an empty script:
C:\Temp> cat t.pl
#!/usr/bin/perl
use strict;
use warnings;
C:\Temp> timethis t
TimeThis : Command Line : t
TimeThis : Start Time : Thu May 15 18:20:38 2008
TimeThis : End Time : Thu May 15 18:20:38 2008
TimeThis : Elapsed Time : 00:00:00.218
It took 0.844 seconds to retrieve and parse the required information. Of
course, the time cost would be better amortized if you ran a lot of
these queries.
--
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://www.rehabitation.com/clpmisc/
------------------------------
Date: Thu, 15 May 2008 17:43:46 -0700 (PDT)
From: chadda@lonemerchant.com
Subject: Re: Need ideas on how to make this code faster than a speeding turtle
Message-Id: <9db23530-74e7-4b34-bb8c-a77c7498ca72@1g2000prg.googlegroups.com>
On May 15, 4:14 pm, "A. Sinan Unur" <1...@llenroc.ude.invalid> wrote:
> cha...@lonemerchant.com wrote innews:b0833433-862e-4895-8002-66c92cc53b15@w5g2000prd.googlegroups.com:
>
> > On May 15, 3:16 pm, "Gordon Etly" <ge...@bentsys-INVALID.com> wrote:
> >> cha...@lonemerchant.com wrote:
> >> > On May 15, 1:37 pm, Uri Guttman <u...@stemsystems.com> wrote:
> >> > chadda <cha...@lonemerchant.com> writes:
> >> > > i have to know if you could write this mess any slower? you are
> >> > > doing
> >> > > everything possible to slow you down.
> >> > I know I shouldn't critize free help, but you seem to have some
> >> > anger management issues.
>
> ...
>
> >> As a simple answer, take a look at LWP:UserAgent
> >> (http://search.cpan.org/~gaas/libwww-perl-
>
> 5.812/lib/LWP/UserAgent.pm),
>
> >> as a good start in the right direction.
>
> ...
>
> > I just tried LWP, and now I can't get the code to work for the life of
> > me. Here is what I attempted
>
> As I mentioned elsewhere, all you need is LWP::Simple.
>
> So, here is a fish for you:
>
> C:\Temp> cat p.pl
> #!/usr/bin/perl
>
> use strict;
> use warnings;
>
> use HTML::TokeParser;
> use LWP::Simple;
>
> my ($input_file) = @ARGV;
> die "No input file specified\n" unless defined $input_file;
>
> open my $INPUT, '<', $input_file
> or die "Cannot open '$input_file': $!";
>
> ID:
> while ( my $id = <$INPUT> ) {
> chomp $id;
>
> my $url = make_url( $id );
> my $html = get $url;
>
> unless ( defined $html ) {
> warn "Error downloading from '$url'\n";
> next ID;
> }
>
> my $parser = HTML::TokeParser->new( \$html );
>
> TABLE:
> while ( my $token = $parser->get_tag('table') ) {
> if ( lc $token->[1]{id} eq 'product_details' ) {
> my $td = $parser->get_tag('td');
> last TABLE unless $td;
> my $cell = $parser->get_text('/td');
> my %data;
> while ( $cell =~ /\s*([^:]+?):\s+(\d+)\s+/g ) {
> $data{$1} = $2;
> }
> use Data::Dumper;
> print Dumper \%data;
> }
> }
>
> }
>
> sub make_url {
> return
> sprintf q{http://www.doba.com/members/catalog/%s.html}, $_[0];
>
> }
>
> __END__
>
> C:\Temp> timethis p list
>
> $VAR1 = {
> 'Product ID' => '3308191',
> 'UPC' => '896207999816',
> 'Item ID' => '3653992',
> 'SKU' => '8930'
> };
>
> TimeThis : Command Line : p list
> TimeThis : Start Time : Thu May 15 18:19:28 2008
> TimeThis : End Time : Thu May 15 18:19:29 2008
> TimeThis : Elapsed Time : 00:00:01.062
>
> Comparing this to the overhead of an empty script:
>
> C:\Temp> cat t.pl
> #!/usr/bin/perl
>
> use strict;
> use warnings;
>
> C:\Temp> timethis t
>
> TimeThis : Command Line : t
> TimeThis : Start Time : Thu May 15 18:20:38 2008
> TimeThis : End Time : Thu May 15 18:20:38 2008
> TimeThis : Elapsed Time : 00:00:00.218
>
> It took 0.844 seconds to retrieve and parse the required information. Of
> course, the time cost would be better amortized if you ran a lot of
> these queries.
>
> --
> A. Sinan Unur <1...@llenroc.ude.invalid>
> (remove .invalid and reverse each component for email address)
>
> comp.lang.perl.misc guidelines on the WWW:http://www.rehabitation.com/clpmisc/
When I try to run this code, I keep getting a blank url.
------------------------------
Date: Fri, 16 May 2008 00:49:03 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Need ideas on how to make this code faster than a speeding turtle
Message-Id: <Xns9A9FD3C493CB1asu1cornelledu@127.0.0.1>
chadda@lonemerchant.com wrote in
news:9db23530-74e7-4b34-bb8c-a77c7498ca72@1g2000prg.googlegroups.com:
[ Do not quote in full. Do not quote sigs. ]
> On May 15, 4:14 pm, "A. Sinan Unur" <1...@llenroc.ude.invalid> wrote:
>> So, here is a fish for you:
>>
>> C:\Temp> cat p.pl
>> #!/usr/bin/perl
>>
>> use strict;
>> use warnings;
>>
>> use HTML::TokeParser;
>> use LWP::Simple;
>>
>> my ($input_file) = @ARGV;
>> die "No input file specified\n" unless defined $input_file;
>>
>> open my $INPUT, '<', $input_file
>> or die "Cannot open '$input_file': $!";
>>
>> ID:
>> while ( my $id = <$INPUT> ) {
>> chomp $id;
>>
>> my $url = make_url( $id );
>> my $html = get $url;
>>
>> unless ( defined $html ) {
>> warn "Error downloading from '$url'\n";
>> next ID;
>> }
>>
>> my $parser = HTML::TokeParser->new( \$html );
>>
>> TABLE:
>> while ( my $token = $parser->get_tag('table') ) {
>> if ( lc $token->[1]{id} eq 'product_details' ) {
>> my $td = $parser->get_tag('td');
>> last TABLE unless $td;
>> my $cell = $parser->get_text('/td');
>> my %data;
>> while ( $cell =~ /\s*([^:]+?):\s+(\d+)\s+/g ) {
>> $data{$1} = $2;
>> }
>> use Data::Dumper;
>> print Dumper \%data;
>> }
>> }
>>
>> }
>>
>> sub make_url {
>> return
>> sprintf q{http://www.doba.com/members/catalog/%s.html}, $_[0];
>>
>> }
>>
>> __END__
...
> When I try to run this code, I keep getting a blank url.
Well, did you provide it with a file containing the id numbers? How do
you know the URL is blank? Did you modify the code? If you did, why did
you not post the relevant modifications?
I would have normally put the id number in the __DATA__ section, but
since you implied that you already had an input file with id numbers, I
followed your example.
In any case, unless you take active steps to help others help you, this
will be the sum total of the help I will provide you.
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://www.rehabitation.com/clpmisc/
------------------------------
Date: Fri, 16 May 2008 02:38:01 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Need ideas on how to make this code faster than a speeding turtle
Message-Id: <1gsp24t827vjihrast4r6ua7r23t9jnu16@4ax.com>
chadda@lonemerchant.com wrote:
>I 'll eventually have the input file filled with 350 million items.
>Right now there is only one
>
>$more input
>3308191
>
>The following program reads in the number from the file named 'input'
>and builds a url form this number. Then it builds a url from this
>number. I have lynx then dump the data into a file called 'out' and
>then just grep the entire thing for the Product Number, Product ID,
>SKU, UPC, and weight.
>
>
>m-net% more parse.pl
>#!/usr/bin/perl -w
>
>my (@shit, $read, $build, @product, @id, @sku, @upc, @weight);
>my $temp;
>
>open(IN, '<', 'input') || die "cant open: $!";
>$read = <IN>;
I suppose you want to turn that line into a while loop once you got more
than one single item to process.
However, considering network latency and response times it may very well
be worthwhile to trigger multiple HTTP requests in parallel, such that
your processing code will never have to wait for network responses.
Other issues like shelling out an expensive external process, that
expensive but useless temporary file, or trying to parse HTML code using
REs others already mentioned.
jue
------------------------------
Date: Fri, 16 May 2008 02:41:38 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: Need ideas on how to make this code faster than a speeding turtle
Message-Id: <g2tp249pv3f14mmlh1pfl8n0v6nq2asvod@4ax.com>
"Gordon Etly" <getly@bentsys-INVALID.com> wrote:
>He seems to constantly come across this way. I really wish he could see
>things from other points of view.
Are you the same moron you went into my killfile a few days ago as
Gordon Etly <get@bentsys.com>? I guess everyone had filtered you so you
had to create a new identity, right? Back you go where you came from!
>As a simple answer, take a look at LWP:UserAgent
>(http://search.cpan.org/~gaas/libwww-perl-5.812/lib/LWP/UserAgent.pm),
>as a good start in the right direction.
Yeah, it's easy enough to copy what other people had mentioned already.
jue
------------------------------
Date: Thu, 15 May 2008 23:31:17 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Need ideas on how to make this code faster than a speeding turtle
Message-Id: <x7od7787qy.fsf@mail.sysarch.com>
>>>>> "GE" == Gordon Etly <getly@bentsys-INVALID.com> writes:
GE> chadda@lonemerchant.com wrote:
>> On May 15, 1:37 pm, Uri Guttman <u...@stemsystems.com> wrote:
>> chadda <cha...@lonemerchant.com> writes:
>> > i have to know if you could write this mess any slower? you are
>> > doing
>> > everything possible to slow you down.
>> I know I shouldn't critize free help, but you seem to have some anger
>> management issues.
GE> He seems to constantly come across this way. I really wish he could see
GE> things from other points of view.
GE> ...
as usual, no help from you.
GE> As a simple answer, take a look at LWP:UserAgent
GE> (http://search.cpan.org/~gaas/libwww-perl-5.812/lib/LWP/UserAgent.pm),
GE> as a good start in the right direction.
which i already told him and we have already improved his code a good
deal. try to keep up.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Free Perl Training --- http://perlhunter.com/college.html ---------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Fri, 16 May 2008 04:42:18 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri May 16 2008
Message-Id: <K0y2EI.21sn@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
-0.01
http://search.cpan.org/~reneeb/-0.01/
----
Acme-Sub-Parms-1.00
http://search.cpan.org/~snowhare/Acme-Sub-Parms-1.00/
Provides simple, fast parsing of named subroutine parameters
----
Apache-DBI-1.07
http://search.cpan.org/~pgollucci/Apache-DBI-1.07/
Initiate a persistent database connection
----
Apache-Dir-0.06
http://search.cpan.org/~dwheeler/Apache-Dir-0.06/
Simple Perl Version of mod_dir
----
Apache-FakeTable-0.04
http://search.cpan.org/~dwheeler/Apache-FakeTable-0.04/
Pure Perl implementation of the Apache::Table interface.
----
Apache2-ASP-1.44
http://search.cpan.org/~johnd/Apache2-ASP-1.44/
Perl extension for ASP on mod_perl2.
----
BDB-Wrapper-0.07
http://search.cpan.org/~hikarine/BDB-Wrapper-0.07/
Wrapper module for BerkeleyDB
----
Class-Delegation-Simple-0.01
http://search.cpan.org/~johnd/Class-Delegation-Simple-0.01/
Simple delegation for Perl
----
Class-Delegator-0.08
http://search.cpan.org/~dwheeler/Class-Delegator-0.08/
Simple and fast object-oriented delegation
----
Class-Meta-0.61
http://search.cpan.org/~dwheeler/Class-Meta-0.61/
Class automation, introspection, and data validation
----
Coat-0.310
http://search.cpan.org/~sukria/Coat-0.310/
A light and self-dependent meta-class for Perl5
----
DBD-Ingres-0.52
http://search.cpan.org/~sreagle/DBD-Ingres-0.52/
DBI driver for Ingres database systems
----
DBD-Ingres-0.5201
http://search.cpan.org/~sreagle/DBD-Ingres-0.5201/
DBI driver for Ingres database systems
----
DBD-SQLite-Amalgamation-3.5.9
http://search.cpan.org/~audreyt/DBD-SQLite-Amalgamation-3.5.9/
Single C-file based DBD::SQLite distribution
----
Dowse-BadSSH-0.02
http://search.cpan.org/~samv/Dowse-BadSSH-0.02/
----
Dowse-BadSSH-0.03
http://search.cpan.org/~samv/Dowse-BadSSH-0.03/
----
Dowse-BadSSH-0.04
http://search.cpan.org/~samv/Dowse-BadSSH-0.04/
----
Exception-Class-DBI-0.99
http://search.cpan.org/~dwheeler/Exception-Class-DBI-0.99/
DBI Exception objects
----
FabForce-DBDesigner4-0.12
http://search.cpan.org/~reneeb/FabForce-DBDesigner4-0.12/
Parse/Analyse XML-Files created by DBDesigner 4 (FabForce)
----
FabForce-DBDesigner4-DBIC-0.06
http://search.cpan.org/~reneeb/FabForce-DBDesigner4-DBIC-0.06/
create DBIC scheme for DBDesigner4 xml file
----
GD-Graph-smoothlines-1.5
http://search.cpan.org/~andrei/GD-Graph-smoothlines-1.5/
----
Kephra-0.3.9.8
http://search.cpan.org/~lichtkind/Kephra-0.3.9.8/
crossplatform, CPAN-installable GUI-Texteditor along perllike Paradigms
----
Math-Prime-XS-0.20_01
http://search.cpan.org/~schubiger/Math-Prime-XS-0.20_01/
Calculate/detect prime numbers with deterministic tests
----
Module-Metadata-Changes-1.01
http://search.cpan.org/~rsavage/Module-Metadata-Changes-1.01/
Manage a module's machine-readable Changelog.ini file
----
Net-WhitePages-1.01
http://search.cpan.org/~darren/Net-WhitePages-1.01/
A Perl interface to the WhitePages.com API
----
Net-uFTP-0.11
http://search.cpan.org/~strzelec/Net-uFTP-0.11/
Universal interface for FTP-like modules (FTP, SFTP, SCP), in most cases Net::FTP compatible.
----
OAI-Harvester-1.13
http://search.cpan.org/~thb/OAI-Harvester-1.13/
----
ORLite-0.01
http://search.cpan.org/~adamk/ORLite-0.01/
Extremely light weight SQLite-specific ORM
----
POE-Component-Server-NNTP-1.00
http://search.cpan.org/~bingos/POE-Component-Server-NNTP-1.00/
A POE component that provides NNTP server functionality.
----
POE-Component-Server-POP3-0.06
http://search.cpan.org/~bingos/POE-Component-Server-POP3-0.06/
A POE framework for authoring POP3 servers
----
Parse-Eyapp-1.110
http://search.cpan.org/~casiano/Parse-Eyapp-1.110/
Extensions for Parse::Yapp
----
SVN-Notify-2.74
http://search.cpan.org/~dwheeler/SVN-Notify-2.74/
Subversion activity notification
----
SVN-Notify-Filter-Markdown-0.02
http://search.cpan.org/~dwheeler/SVN-Notify-Filter-Markdown-0.02/
Convert SVN::Notify log messages from Markdown to HTML
----
Socket-Class-1.20
http://search.cpan.org/~chrmue/Socket-Class-1.20/
A class to communicate with sockets
----
TAP-Harness-Remote-0.02
http://search.cpan.org/~alexmv/TAP-Harness-Remote-0.02/
Run tests on a remote server
----
Test-Environment-0.04_03
http://search.cpan.org/~jkutej/Test-Environment-0.04_03/
Base module for loading Test::Environment::Plugin::*
----
Test-POE-Server-TCP-0.04
http://search.cpan.org/~bingos/Test-POE-Server-TCP-0.04/
A POE Component providing TCP server services for test cases
----
Test-POE-Server-TCP-0.06
http://search.cpan.org/~bingos/Test-POE-Server-TCP-0.06/
A POE Component providing TCP server services for test cases
----
Test-Server-0.05_01
http://search.cpan.org/~jkutej/Test-Server-0.05_01/
what about test driven administration?
----
Test-Tagged-0.01_01
http://search.cpan.org/~sartak/Test-Tagged-0.01_01/
tag your tests so they can be run selectively
----
Vroom-0.11
http://search.cpan.org/~ingy/Vroom-0.11/
See Vroom::Vroom.
----
WebService-MusicBrainz-0.18
http://search.cpan.org/~bfaist/WebService-MusicBrainz-0.18/
----
Win32-WindowsMedia-0.22
http://search.cpan.org/~shamrock/Win32-WindowsMedia-0.22/
Base Module for Provisiong and control for Windows Media Services
----
XRI-Resolution-Lite-0.01
http://search.cpan.org/~zigorou/XRI-Resolution-Lite-0.01/
The LightWeight client module for XRI Resolution
----
YATT-0.0.2
http://search.cpan.org/~hkoba/YATT-0.0.2/
Yet Another Template Toolkit
----
Zucchini-0.0.4
http://search.cpan.org/~chisel/Zucchini-0.0.4/
turn templates into static websites
----
autobox-2.43
http://search.cpan.org/~chocolate/autobox-2.43/
call methods on native types
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
------------------------------
Date: Thu, 15 May 2008 17:38:52 -0700 (PDT)
From: kronecker@yahoo.co.uk
Subject: Permissions on a file
Message-Id: <27a86a81-91bd-4d5c-87ff-1b7db0770aeb@v26g2000prm.googlegroups.com>
I create a text file on the server remote.txt ok with the following
code (the last part of it)
$first_name = $FORM{command1};
$last_name = $FORM{command2};
open (example, ">remote.txt") || die ("Could not open file. $!");
print example "$first_name\n$last_name\n";
close (example);
print "Content-type:text/html\r\n\r\n";
This bit causes errors...... chmod
0777,'remote.txt'; ......................................
print "<html>";
print "<head>";
print "<title> Processed</title>";
print "</head>";
print "<body>";
print "<h2>Commands $first_name $last_name - Sent to text file</h2>";
print "</body>";
print "</html>";
The problem is that I need to be able to delete this file remotely
using FTP and the script generate a new version every now and then. I
need teh script to make the file deleteable. How do I do this?
I tried chmod 0777,'remote.txt' and it spews out errors.
K.
------------------------------
Date: Fri, 16 May 2008 00:57:30 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Permissions on a file
Message-Id: <Xns9A9FD5337A7C6asu1cornelledu@127.0.0.1>
kronecker@yahoo.co.uk wrote in news:27a86a81-91bd-4d5c-87ff-
1b7db0770aeb@v26g2000prm.googlegroups.com:
> I create a text file on the server remote.txt ok with the following
> code (the last part of it)
You should always, yes always,
use strict;
use warnings;
> $first_name = $FORM{command1};
> $last_name = $FORM{command2};
>
> open (example, ">remote.txt") || die ("Could not open file. $!");
We have been through this once before
my $filename = 'remote.txt';
open my $EXAMPLE, '>', $filename
or die "Cannot open '$filename': $!";
> print example "$first_name\n$last_name\n";
print $EXAMPLE "$first_name\n$last_name\n";
> close (example);
It is crucial to check for errors on close on a filehandle opened for
writing.
close $EXAMPLE or die "Error closing '$filename': $!";
> print "Content-type:text/html\r\n\r\n";
> This bit causes errors...... chmod
> 0777,'remote.txt'; ......................................
What errors does it cause?
chmod 0777, $filename
or die "Cannot chmod on '$filename': $!";
Have you read perldoc -f chmod and perldoc -f umask?
> print "<html>";
> print "<head>";
> print "<title> Processed</title>";
> print "</head>";
> print "<body>";
> print "<h2>Commands $first_name $last_name - Sent to text file</h2>";
> print "</body>";
> print "</html>";
Don't be silly!
print <<EO_HTML;
<html>
<head>
<title>Processed<title>
</head>
<body>
<h2>Commands $first_name $last_name - Sent to text file</h2>
</body>
</html>
EO_HTML
> The problem is that I need to be able to delete this file remotely
> using FTP and the script generate a new version every now and then. I
> need teh script to make the file deleteable. How do I do this?
> I tried chmod 0777,'remote.txt' and it spews out errors.
Did you try looking at the error messages?
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://www.rehabitation.com/clpmisc/
------------------------------
Date: Fri, 16 May 2008 06:11:30 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <mA9Xj.264$mh5.261@nlpi067.nbdc.sbc.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Fri, 16 May 2008 02:48:42 GMT
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: regular expression question
Message-Id: <2ctp24lf3eelrdjr4nukphsb2tlohoesh7@4ax.com>
Orson <moleskyca1@yahoo.com> wrote:
>I am trying to use grep -P (for perl regular expressions). I want to
>match lines that do not contain the chars "sync".
Do you mean contains none of the characters 'c', 'n', 's', and 'y'?
Or do you mean does not contain all of those 4 characters?
Or do you mean does not contain the substring 'sync'?
There are very different requirements and your description can be
interpreted in all three way and it is not clear to me what you expect.
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:
#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 1547
***************************************
