[29685] in Perl-Users-Digest
Perl-Users Digest, Issue: 929 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Oct 12 06:09:39 2007
Date: Fri, 12 Oct 2007 03:09:04 -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, 12 Oct 2007 Volume: 11 Number: 929
Today's topics:
add 1 to the captured backreference ?? <jbl02NO@SPAMhotmail.com>
Re: changing format comment char (Time Waster)
Re: https access - NET::SSL or Crypt::SSLeay ? <uctraing@ultranet.com>
LWP, Post, return data ? <wheeledBob@yahoo.com>
Re: LWP, Post, return data ? <mritty@gmail.com>
Re: LWP, Post, return data ? <wheeledBob@yahoo.com>
Re: LWP, Post, return data ? <wheeledBob@yahoo.com>
new CPAN modules on Fri Oct 12 2007 (Randal Schwartz)
Re: newbie question sln@netherlands.co
Re: newbie question <mritty@gmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: quotes difference in Perl5.6 vs 5.8 <tadmc@seesig.invalid>
Re: quotes difference in Perl5.6 vs 5.8 <mritty@gmail.com>
Re: quotes difference in Perl5.6 vs 5.8 <abigail@abigail.be>
Windows,ASSOC,FTYPE,.pl,.plx,.sh <anonymous@127.0.0.1>
Re: Windows,ASSOC,FTYPE,.pl,.plx,.sh <wheeledBob@yahoo.com>
Re: Windows,ASSOC,FTYPE,.pl,.plx,.sh <nospam-abuse@ilyaz.org>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 12 Oct 2007 04:50:30 -0500
From: jbl <jbl02NO@SPAMhotmail.com>
Subject: add 1 to the captured backreference ??
Message-Id: <qbgug3h53ua0cpqfisn1jl7713dk2g5cu8@4ax.com>
It seems like it shoukd be simple but it it driving me more crazy than
I already was.
All I want to do is add 1 to each and any number in the string.
ie... 1 becomes 2
All I am doingwith this is putting a literal '+1'
# changeNumbers.pl
# desired output
# string text 2 string text
# string text 2 string text 3 string text
# string text 2 string text 3 4 string text 5 6 string text
use warnings;
use strict;
while (<DATA>)
{
my $string = $_;
$string =~ s/(\d)/$1+1/g;
print $string;
}
__DATA__
string text 1 string text
string text 1 string text 2 string text
string text 1 string text 2 3 string text 4 5 string text
this is my actual output;
C:\>changeNumbers.pl
string text 1+1 string text
string text 1+1 string text 2+1 string text
string text 1+1 string text 2+1 3+1 string text 4+1 5+1 string text
thanks,
jbl
------------------------------
Date: Fri, 12 Oct 2007 01:23:18 GMT
From: bfc@fenway.UUCP (Time Waster)
Subject: Re: changing format comment char
Message-Id: <a0APi.4838$d2.515@trnddc08>
Nice!
Thanks everyone, i'm using the simple redirect from inline now.
In article <xrudne1W5MibWJPanZ2dnUVZ8qSnnZ2d@pipex.net>,
Big and Blue <No_4@dsl.pipex.com> wrote:
>As has been pointed out, you don't want to do that anyway, but if you ever
>come across a case where you do then all you need to do is put the difficult
>line into a string and print the string:
>
>==========
><start of code>...
>
>my $str="#!/usr/bin/expect";
>
>format =
>@*
>$str
>spawn some-commnd
>expect -re "some string"
>more here of course
>.
>
>....<rest of code>
------------------------------
Date: Fri, 12 Oct 2007 02:46:11 GMT
From: - Bob - <uctraing@ultranet.com>
Subject: Re: https access - NET::SSL or Crypt::SSLeay ?
Message-Id: <usntg3tgjlu1qjss7jigtleljnjbd7582j@4ax.com>
On Thu, 11 Oct 2007 12:12:38 -0500, "J. Gleixner"
<glex_no-spam@qwest-spam-no.invalid> wrote:
>
>If you can 'pull a page' for a non-SSL URL, you can 'pull a page'
>for a SSL URL, if Crypt::SSLeay is installed. The only
>difference in the script is 'https' vs 'http'. You don't use
>Crypt::SSLeay directly, LWP::* handles that for you.
>
>To see how to 'pull a page', first try the documentation:
>
>perldoc lwpcook
>perldoc LWP::UserAgent
>
>Or you could simply use the lwp-download script that might have
>been installed as part of LWP. You could also use your favorite
>search engine and find many pages on the Internet, instead
>of waiting for someone to respond in the newsgroup.
Thanks. I hacked around with it last night and figured it out. What's
confusing is the relationship between Net::SSL and/or Crypt::SSLeay -
but as you noted, once you figure it out, you realize it doesn't
matter.
------------------------------
Date: Fri, 12 Oct 2007 02:26:50 GMT
From: still me <wheeledBob@yahoo.com>
Subject: LWP, Post, return data ?
Message-Id: <uhmtg3lhf8pr0e6ucl5aut8bfjo338o26l@4ax.com>
I am trying to write a cgi that calls (POSTs to) another cgi. The
second cgi returns a web page (HTML). I can't seem to figure out how
to get to the data that the second cgi sends back. The cgi runs, the
POST works, but i don't know how to access the return output from the
second cgi (so I can pass it back to the browser that made the initial
call).
Here's the (very trimmed) code of the first program:
#!/usr/bin/perl -w
use strict;
use CGI qw(:all);
use CGI::Carp qw(fatalsToBrowser);
use LWP;
my $browser = LWP::UserAgent->new;
my $url = 'http://www.example.com/cgi-bin/second.pl';
my $response = $browser->post( $url,
[ 'ed' => '001',
'test' => 'it worked',
]
);
# and right here I want to forward the data to the calling browser
Thanks
------------------------------
Date: Thu, 11 Oct 2007 19:38:27 -0700
From: Paul Lalli <mritty@gmail.com>
Subject: Re: LWP, Post, return data ?
Message-Id: <1192156707.725636.162380@e34g2000pro.googlegroups.com>
On Oct 11, 10:26 pm, still me <wheeled...@yahoo.com> wrote:
> I am trying to write a cgi that calls (POSTs to) another cgi. The
> second cgi returns a web page (HTML). I can't seem to figure out how
> to get to the data that the second cgi sends back. The cgi runs, the
> POST works, but i don't know how to access the return output from the
> second cgi (so I can pass it back to the browser that made the initial
> call).
>
> Here's the (very trimmed) code of the first program:
>
> #!/usr/bin/perl -w
> use strict;
> use CGI qw(:all);
> use CGI::Carp qw(fatalsToBrowser);
> use LWP;
> my $browser = LWP::UserAgent->new;
> my $url = 'http://www.example.com/cgi-bin/second.pl';
> my $response = $browser->post( $url,
> [ 'ed' => '001',
> 'test' => 'it worked',
> ]
> );
>
> # and right here I want to forward the data to the calling browser
LWP::UserAgent::post() returns an HTTP::Response object.
http://search.cpan.org/~gaas/libwww-perl-5.808/lib/HTTP/Response.pm
$response = $ua->request($request)
if ($response->is_success) {
print $response->content;
}
else {
print STDERR $response->status_line, "\n";
}
Paul Lalli
------------------------------
Date: Fri, 12 Oct 2007 03:05:20 GMT
From: still me <wheeledBob@yahoo.com>
Subject: Re: LWP, Post, return data ?
Message-Id: <u0ptg3db1v228pt81i096i3ber5asdho0p@4ax.com>
On Thu, 11 Oct 2007 19:38:27 -0700, Paul Lalli <mritty@gmail.com>
wrote:
> $response = $ua->request($request)
> if ($response->is_success) {
> print $response->content;
> }
> else {
> print STDERR $response->status_line, "\n";
> }
Thanks. I tried something like that multiple ways but it didn't work.
But, since you insisted, I went back to it one more time. Turned out
is was an error in terms of what was coming back from the called
program. It's always sumthin!
------------------------------
Date: Fri, 12 Oct 2007 04:00:27 GMT
From: still me <wheeledBob@yahoo.com>
Subject: Re: LWP, Post, return data ?
Message-Id: <r1stg319qfh33o8nre87elhqordmp89ho2@4ax.com>
On Thu, 11 Oct 2007 19:38:27 -0700, Paul Lalli <mritty@gmail.com>
wrote:
>> #!/usr/bin/perl -w
>> use strict;
>> use CGI qw(:all);
>> use CGI::Carp qw(fatalsToBrowser);
>> use LWP;
>> my $browser = LWP::UserAgent->new;
>> my $url = 'http://www.example.com/cgi-bin/second.pl';
>> my $response = $browser->post( $url,
>> [ 'ed' => '001',
>> 'test' => 'it worked',
>> ]
>> );
>>
>> # and right here I want to forward the data to the calling browser
>
>LWP::UserAgent::post() returns an HTTP::Response object.
>
>http://search.cpan.org/~gaas/libwww-perl-5.808/lib/HTTP/Response.pm
>
> $response = $ua->request($request)
> if ($response->is_success) {
> print $response->content;
> }
> else {
> print STDERR $response->status_line, "\n";
> }
>
>Paul Lalli
I need a little more help. I also need to access the return headers
that are sent back from the called cgi. I read this:
http://search.cpan.org/~gaas/libwww-perl-5.808/lib/HTTP/Headers.pm
And I think I need to access this: $h->as_string( $eol )
But I am having trouble making the logical jump as to how the code
would actually look. It's clear enough when I want to create a new
header object, but how do I get the return values from the "$response
= $ua->request($request)" to populate the header object? Some detailed
code would be very helpful.
Thanks,
------------------------------
Date: Fri, 12 Oct 2007 04:42:15 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri Oct 12 2007
Message-Id: <Jps7qF.BI2@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.
Apache-SWIT-0.29
http://search.cpan.org/~bosu/Apache-SWIT-0.29/
mod_perl based application server with integrated testing.
----
Bot-Net-0.0.3
http://search.cpan.org/~hanenkamp/Bot-Net-0.0.3/
run your very own IRC bot net
----
Bricklayer-Templater-0.9.8
http://search.cpan.org/~zaphar/Bricklayer-Templater-0.9.8/
yet another templating system. Pure perl, highly flexible with very few dependencies.
----
CGI-Pager-1.00
http://search.cpan.org/~egorsh/CGI-Pager-1.00/
generate HTML pagination linkage easily.
----
Catalyst-Model-DBIC-Schema-QueryLog-0.04
http://search.cpan.org/~fayland/Catalyst-Model-DBIC-Schema-QueryLog-0.04/
DBIx::Class::QueryLog Model Class
----
Chart-Clicker-1.2.3
http://search.cpan.org/~gphat/Chart-Clicker-1.2.3/
Powerful, extensible charting.
----
Coat-0.1_0.6
http://search.cpan.org/~sukria/Coat-0.1_0.6/
A light and self-dependent meta-class for Perl5
----
Crypt-Util-0.03
http://search.cpan.org/~nuffin/Crypt-Util-0.03/
A lightweight Crypt/Digest convenience API
----
Crypt-Util-0.04
http://search.cpan.org/~nuffin/Crypt-Util-0.04/
A lightweight Crypt/Digest convenience API
----
Crypt-Util-0.05
http://search.cpan.org/~nuffin/Crypt-Util-0.05/
A lightweight Crypt/Digest convenience API
----
DBIx-Safe-1.2.4
http://search.cpan.org/~turnstep/DBIx-Safe-1.2.4/
Safer access to your database through a DBI database handle
----
Devel-Symdump-2.08
http://search.cpan.org/~andk/Devel-Symdump-2.08/
dump symbol names or the symbol table
----
Games-Nonogram-0.01
http://search.cpan.org/~ishigaki/Games-Nonogram-0.01/
solve and analyze Nonogram
----
Games-Tournament-Swiss-0.10
http://search.cpan.org/~drbean/Games-Tournament-Swiss-0.10/
FIDE Swiss Same-Rank Contestant Pairing
----
Geo-Gpx-0.19
http://search.cpan.org/~andya/Geo-Gpx-0.19/
Create and parse GPX files.
----
Geo-Gpx-0.20
http://search.cpan.org/~andya/Geo-Gpx-0.20/
Create and parse GPX files.
----
IPC-Cmd-0.38
http://search.cpan.org/~kane/IPC-Cmd-0.38/
finding and running system commands made easy
----
Language-MuldisD-0.9.1
http://search.cpan.org/~duncand/Language-MuldisD-0.9.1/
Formal spec of Muldis D relational DBMS lang
----
Linux-USBKeyboard-0.01
http://search.cpan.org/~ewilhelm/Linux-USBKeyboard-0.01/
access devices pretending to be qwerty keyboards
----
Logfile-EPrints-1.14
http://search.cpan.org/~timbrody/Logfile-EPrints-1.14/
Process Web log files for institutional repositories
----
Net-CUPS-0.55
http://search.cpan.org/~dhageman/Net-CUPS-0.55/
Common Unix Printing System Interface
----
NetSNMP-LogParser-1.0470
http://search.cpan.org/~nito/NetSNMP-LogParser-1.0470/
An incremental logparser to be used with Net-SNMP
----
NetSNMP-MibProxy-1.0473
http://search.cpan.org/~nito/NetSNMP-MibProxy-1.0473/
Simple pass_persist script for Net-SNMP
----
POE-Loop-AnyEvent-0.01
http://search.cpan.org/~perigrin/POE-Loop-AnyEvent-0.01/
----
POE-Loop-AnyEvent-0.02
http://search.cpan.org/~perigrin/POE-Loop-AnyEvent-0.02/
a bridge that supports AnyEvent.pm from POE
----
PPI-1.199_07
http://search.cpan.org/~adamk/PPI-1.199_07/
Parse, Analyze and Manipulate Perl (without perl)
----
Params-Validate-Micro-0.032
http://search.cpan.org/~hdp/Params-Validate-Micro-0.032/
Validate parameters concisely
----
Pod-Snippets-0.11
http://search.cpan.org/~domq/Pod-Snippets-0.11/
Extract and reformat snippets of POD so as to use them in a unit test (or other Perl code)
----
Pod-Snippets-0.12
http://search.cpan.org/~domq/Pod-Snippets-0.12/
Extract and reformat snippets of POD so as to use them in a unit test (or other Perl code)
----
Rose-DBx-TestDB-0.01
http://search.cpan.org/~karman/Rose-DBx-TestDB-0.01/
test Rose::DB::Object modules
----
Rose-DBx-TestDB-0.02
http://search.cpan.org/~karman/Rose-DBx-TestDB-0.02/
test Rose::DB::Object modules
----
SNMP-Effective-1.05
http://search.cpan.org/~eidolon/SNMP-Effective-1.05/
An effective SNMP-information-gathering module
----
SVN-Access-0.03
http://search.cpan.org/~mgregoro/SVN-Access-0.03/
Perl extension to manipulate SVN Access files
----
Socket-Class-1.12
http://search.cpan.org/~chrmue/Socket-Class-1.12/
A class to communicate with sockets
----
Test-Dynamic-1.3.2
http://search.cpan.org/~turnstep/Test-Dynamic-1.3.2/
Automatic test counting for Test::More
----
Test-Harness-2.99_04
http://search.cpan.org/~andya/Test-Harness-2.99_04/
Run Perl standard test scripts with statistics
----
Test-Weaken-0.000_001
http://search.cpan.org/~jkegl/Test-Weaken-0.000_001/
Test for leaks after weakening of circular references
----
Text-WikiCreole-0.05
http://search.cpan.org/~jburnett/Text-WikiCreole-0.05/
Convert Wiki Creole 1.0 markup to XHTML
----
Tk-RotatingGauge-0.24
http://search.cpan.org/~jquelin/Tk-RotatingGauge-0.24/
a rotating gauge for Tk
----
Tk-Wizard-2.117
http://search.cpan.org/~mthurn/Tk-Wizard-2.117/
GUI for step-by-step interactive logical process
----
Tk-XMLViewer-0.18_91
http://search.cpan.org/~srezic/Tk-XMLViewer-0.18_91/
Tk widget to display XML
----
WWW-Myspace-0.72
http://search.cpan.org/~grantg/WWW-Myspace-0.72/
Access MySpace.com profile information from Perl
----
WebService-Google-Suggest-0.03
http://search.cpan.org/~miyagawa/WebService-Google-Suggest-0.03/
Google Suggest as an API
----
YATG-1.0302
http://search.cpan.org/~oliver/YATG-1.0302/
Fast SNMP data poller daemon, with storage and graphing
----
kurila-1.4_0
http://search.cpan.org/~tty/kurila-1.4_0/
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/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: Thu, 11 Oct 2007 18:14:20 -0700
From: sln@netherlands.co
Subject: Re: newbie question
Message-Id: <67itg3dk3adg39bdgm55tv49acusf4ot84@4ax.com>
On Thu, 11 Oct 2007 17:48:25 -0700, andrew_nuss@yahoo.com wrote:
>Hi,
>
>How do you apply a regexp directly to a stream rather than a string?
>
>Andy
But, what is a stream? All I/O is buffered to variables, otherwise
languages wouldn't exist, there would be no need, there would only be
a before and after. No middle. Quantum middleware.
An infinite loop @the_universe = /<Stream>+$regexp/g;
------------------------------
Date: Thu, 11 Oct 2007 19:41:17 -0700
From: Paul Lalli <mritty@gmail.com>
Subject: Re: newbie question
Message-Id: <1192156877.512329.19370@i38g2000prf.googlegroups.com>
On Oct 11, 8:48 pm, andrew_n...@yahoo.com wrote:
> How do you apply a regexp directly to a stream rather than a
> string?
Explain what you mean by "stream" in this case.
As a pure hunch, maybe you want the File::Stream module from CPAN,
which allows you to read from an open file handle delimited by a
regexp rather than a string.
Paul Lalli
------------------------------
Date: Fri, 12 Oct 2007 07:10:32 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <I5FPi.3286$wF3.733@nlpi061.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: Thu, 11 Oct 2007 21:09:41 -0500
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: quotes difference in Perl5.6 vs 5.8
Message-Id: <slrnfgtlr5.782.tadmc@tadmc30.sbcglobal.net>
Petr Vileta <stoupa@practisoft.cz> wrote:
> print OUT "$var\n"; # here script fail on server with SIG-PIPE signal
Please do not para-phrase error messages, post the actual
text of the message that you are getting.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Thu, 11 Oct 2007 19:32:54 -0700
From: Paul Lalli <mritty@gmail.com>
Subject: Re: quotes difference in Perl5.6 vs 5.8
Message-Id: <1192156374.007388.52600@t8g2000prg.googlegroups.com>
On Oct 11, 8:48 pm, "Petr Vileta" <sto...@practisoft.cz> wrote:
> I have script written in Perl 5.6.1 and it wotk fine. But when I run the
> same script on hosting server then this fail on trivial operation. On server
> Perl 5.8.0 is installed.
> The example to ilustrate error is this
>
> #!/usr/bin/perl
> use strict;
> use warnings;
> my $var = "abcd'efg";
> open OUT, "> log.txt";
You're not checking the return value of open. You have no idea
whether or not this file was actually opened.
open OUT, '>', 'log.txt' or die "Could not open log: $!";
> print OUT "$var\n"; # here script fail on server with SIG-PIPE signal
What does that mean? Please show the actual error message received.
If the open above didn't succeed, then you're printing to an unopened
filehandle, which absolutely *should* cause your program to fail.
Paul Lalli
------------------------------
Date: 12 Oct 2007 09:01:56 GMT
From: Abigail <abigail@abigail.be>
Subject: Re: quotes difference in Perl5.6 vs 5.8
Message-Id: <slrnfgue04.nop.abigail@alexandra.abigail.be>
_
Petr Vileta (stoupa@practisoft.cz) wrote on VCLV September MCMXCIII in
<URL:news:femg9b$10oj$1@ns.felk.cvut.cz>:
)) I have script written in Perl 5.6.1 and it wotk fine. But when I run the
)) same script on hosting server then this fail on trivial operation. On server
)) Perl 5.8.0 is installed.
)) The example to ilustrate error is this
))
)) #!/usr/bin/perl
)) use strict;
)) use warnings;
)) my $var = "abcd'efg";
)) open OUT, "> log.txt";
)) print OUT "$var\n"; # here script fail on server with SIG-PIPE signal
)) close OUT;
))
)) Is something wrong in my script or is some bug in Perl 5.8.0 ?
There's something wrong with your script. You're not checking the
return value of 'open', blindly assuming it succeeds.
Abigail
--
perl -wlne '}for($.){print' file # Count the number of lines.
------------------------------
Date: Thu, 11 Oct 2007 22:30:40 -0400
From: "Jim Carlock" <anonymous@127.0.0.1>
Subject: Windows,ASSOC,FTYPE,.pl,.plx,.sh
Message-Id: <470edc56$0$9585$4c368faf@roadrunner.com>
Keywords: Windows,assoc,ftype,.pl,.plx
In setting up Perl within a Windows OS, what's the best way to
configure Perl so that a Perl file can get run inside a cmd.exe
prompt, but without using ASSOC or FTYPE to configure things.
Once ASSOC and FTYPE are run, they configure HKLM inside the
registry which in turn makes the whole operating system realize
Perl is installed, and makes the operating system vulnerable to
various exploits.
I hope to run a Perl application/script only inside a specific
cmd.exe prompt, preferably one set up with a .cmd or .bat file,
that in turn does not anyone viewing a website to run Perl. In
other words, I seek to not allow the whole operating system to end
up with the global updates that commands, ASSOC and FTYPE, employ.
Does anyone know of a way to prevent ASSOC and FTYPE from making
a change to the registry? Or perhaps of another way other than
having to type in "Perl.exe printenv.pl"?
--
Jim Carlock
Doctors commonly tell people that there is NO known way to cure
pink-eye without using some sort of medication.
A Natural Cure For Many Forms Of Conjunctivitis
(A Natural Cure For A Variety Of Pink-eye)
http://www.associatedcontent.com/article/381336/saliva_a_natural_cure_for_conjunctivitis.html
------------------------------
Date: Fri, 12 Oct 2007 02:59:05 GMT
From: still me <wheeledBob@yahoo.com>
Subject: Re: Windows,ASSOC,FTYPE,.pl,.plx,.sh
Message-Id: <gkotg3thtde5uof96ean1c7fu31bmn9s7k@4ax.com>
On Thu, 11 Oct 2007 22:30:40 -0400, "Jim Carlock"
<anonymous@127.0.0.1> wrote:
>Does anyone know of a way to prevent ASSOC and FTYPE from making
>a change to the registry? Or perhaps of another way other than
>having to type in "Perl.exe printenv.pl"?
I'd install Active Perl normally and then just remove the association.
However, you won't be able to avoid using "Perl.exe printenv.pl" if
you do that. The only way to get windows to run a program (the Perl
interpreter) is to either set up an association or call it directly
(e.g. Perl.exe printenv.pl)
------------------------------
Date: Fri, 12 Oct 2007 09:30:10 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: Windows,ASSOC,FTYPE,.pl,.plx,.sh
Message-Id: <fener2$er$1@agate.berkeley.edu>
Keywords: Windows,assoc,ftype,.pl,.plx
[A complimentary Cc of this posting was NOT [per weedlist] sent to
Jim Carlock
<anonymous@127.0.0.1>], who wrote in article <470edc56$0$9585$4c368faf@roadrunner.com>:
> In setting up Perl within a Windows OS, what's the best way to
> configure Perl so that a Perl file can get run inside a cmd.exe
> prompt, but without using ASSOC or FTYPE to configure things.
With 4DOS/4OS2/4NT, you could do this by
alias .pl perlexe.exe
or some such. AFAIK, this is not possible with CMD. IMO, an
extremely stupid limitation... You can make CMD look for .pl files on
PATH, but it would not know how to run them; you need to have a .cmd
wrapper for each .pl file on your system.
Hope this helps,
Ilya
------------------------------
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 929
**************************************
