[29596] in Perl-Users-Digest
Perl-Users Digest, Issue: 840 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Sep 11 06:09:45 2007
Date: Tue, 11 Sep 2007 03:09:07 -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 Tue, 11 Sep 2007 Volume: 11 Number: 840
Today's topics:
Re: (?{ code }) block works fine in child rule but not <m@rtij.nl.invlalid>
Re: (?{ code }) block works fine in child rule but not <clint.olsen@gmail.com>
Re: (?{ code }) block works fine in child rule but not <brian.helterline@hp.com>
Re: (?{ code }) block works fine in child rule but not <abigail@abigail.be>
Re: Array Question <stoupa@practisoft.cz>
How to get a colored subject <absmienk@hotmail.com>
Re: INDEX Function <zen13097@zen.co.uk>
new CPAN modules on Tue Sep 11 2007 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Regular Expression <fritz-bayer@web.de>
Re: Replacing every character in a string with individu <peter@makholm.net>
Running Perl script in the backend from Html satish2112@gmail.com
Re: Running Perl script in the backend from Html <noreply@gunnar.cc>
SSH on windows <gil.kovary@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 11 Sep 2007 07:37:24 +0200
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: (?{ code }) block works fine in child rule but not in parent
Message-Id: <pan.2007.09.11.05.35.36@rtij.nl.invlalid>
On Mon, 10 Sep 2007 15:30:51 -0500, Clint Olsen wrote:
> Yeah, this is an old habit. Thanks for the reminder. What'd I'd like
> to do is to be able to use combinations of $^N and $^R to be able to
> roll up lexical subexpressions in a nice way so that I don't have to
> rewrite stuff and also be able to have an entire RE that describes every
> lexical possibility ala what lex/flex would do if you were constructing
> a lexical analyzer. So, that would also mean using the minimum required
> capture buffers to extract the tokens and any state necessary.
Did you look at Parser::Decent? Seems like the perfect tool for this job.
M4
------------------------------
Date: Tue, 11 Sep 2007 01:03:22 -0500
From: Clint Olsen <clint.olsen@gmail.com>
Subject: Re: (?{ code }) block works fine in child rule but not in parent
Message-Id: <slrnfecbta.5mi.clint.olsen@belle.0lsen.net>
On 2007-09-11, Martijn Lievaart <m@rtij.nl.invlalid> wrote:
> Did you look at Parser::Decent? Seems like the perfect tool for this job.
I've had really great luck with Parse::Yapp for that. Are you speaking of
Damian Conway's Parse::RecDescent? The problem with recursive descent
parsing is that it's not as expressive as an LALR parser. So, what's left
is writing the lexer part.
Thanks,
-Clint
------------------------------
Date: Mon, 10 Sep 2007 23:25:24 -0700
From: Brian Helterlilne <brian.helterline@hp.com>
Subject: Re: (?{ code }) block works fine in child rule but not in parent
Message-Id: <fc5ccl$r1e$1@usenet01.boi.hp.com>
Martijn Lievaart wrote:
> Did you look at Parser::Decent? Seems like the perfect tool for this job.
Parse::RecDescent
--
brian
------------------------------
Date: 11 Sep 2007 08:59:23 GMT
From: Abigail <abigail@abigail.be>
Subject: Re: (?{ code }) block works fine in child rule but not in parent
Message-Id: <slrnfecm64.k0v.abigail@alexandra.abigail.be>
_
xhoster@gmail.com (xhoster@gmail.com) wrote on VCXXIII September MCMXCIII
in <URL:news:20070910165330.968$RF@newsreader.com>:
{} Clint Olsen <clint.olsen@gmail.com> wrote:
{} > On 2007-09-10, xhoster@gmail.com <xhoster@gmail.com> wrote:
{} > > Apparently the problem is that you think the answer is to start out by
{} > > reading the source code rather than the documentation.
{} > >
{} > > The behavior you describe is documented in both perldoc perlre and
{} > > perldoc re.
{} >
{} > Yes, I read that section, but I'm not relying on any runtime
{} > interpolation to get my work done (or did I misread something?).
{}
{} Ah, now I see. Now I prefer your reading of the docs to my reading of the
{} docs (or I would if it weren't for the sad fact that the worse reading
{} seems to be correct one).
{}
{} > I want
{} > to avoid using switches that are 'perilous' when it isn't required.
{}
{} Maybe I'm missing something here, but I would argue that if you are running
{} in a hostile environment, it isn't enough to refuse to use re 'eval', you
{} should also run under taint. And once you use taint appropriately, I don't
{} see why use re 'eval' would be perilous.
Well, for starters, /$tainted_variable/ doesn't trigger an exception under -T.
The problem is code that was written before (?{ .. }) existed. Before
(?{ .. }) or (??{ .. }) existed, /$got_this_from_the_environment/ couldn't
do anything more harmful than eat up resources.
So, pre 5.6 code that used /$got_this_from_the_environment/ may not
even use -T, and still be secure. Those programs would suddenly become
a security hole if the perl on the system was upgraded. Also, making
/$got_this_from_the_environment/ throw an exception under -T would have
caused programs that ran under -T already throw a fit if the perl was
updated. Even if there was no potential security issue.
Hence "use re 'eval'" was born.
The regexp engine of 5.10 will have many new features; some of the current
usages of (?{ .. }) can be replaced by the new features. I do not what the
intended usage of (?{ .. }) in the example given by the OP is, but is might
very well be that the same could have done with named capture buffers and
%+ or %- in 5.10.
Abigail
Abigail
--
A perl rose: perl -e '@}>-`-,-`-%-'
------------------------------
Date: Tue, 11 Sep 2007 06:20:46 +0200
From: "Petr Vileta" <stoupa@practisoft.cz>
Subject: Re: Array Question
Message-Id: <fc55cj$3nd$1@ns.felk.cvut.cz>
amerar@iwc.net wrote:
> Hi,
>
> I need to create an array. Each element will have 1 row and 3
> columns. So, the array would look something like this:
>
> $x[1] = 1,2,3
> $x[2] = 4,5,6
> $x[3] = 7,8,9
>
> Basically, I have 1 row and 3 columns.........how would I store the
> values, and retrieve the values???
>
At first of all - Perl arrays are numbered from 0, not from 1.
$x[0] = [1,2,3];
$x[1] = [4,5,6];
$x[2] = [7,8,9];
Variables in array will be addressed as $x[0][0], $x[0][1] ... $x[2][2]
--
Petr Vileta, Czech republic
(My server rejects all messages from Yahoo and Hotmail. Send me your mail
from another non-spammer site please.)
------------------------------
Date: Tue, 11 Sep 2007 03:06:15 -0700
From: ab <absmienk@hotmail.com>
Subject: How to get a colored subject
Message-Id: <1189505175.257140.242980@19g2000hsx.googlegroups.com>
I want to have the recipients of my Perl created e-mail to see a
colored (say: red) subject. How can I direct my mail header to do this
or should I use a trick? All our customers use Outlook.
All help is appreciated.
------------------------------
Date: 11 Sep 2007 07:52:17 GMT
From: Dave Weaver <zen13097@zen.co.uk>
Subject: Re: INDEX Function
Message-Id: <46e64931$0$13939$fa0fcedb@news.zen.co.uk>
On Mon, 10 Sep 2007 11:20:45 -0700, amerar@iwc.net <amerar@iwc.net> wrote:
> On Sep 10, 1:17 pm, "J. Gleixner" <glex_no-s...@qwest-spam-no.invalid>
> wrote:
> > One last time...
> > *Post actual code that others can run which shows your issue.*
> >
>
> Ok, I am writing this script myself, no one else will run it.
You are missing the point.
If you would like people here on clpm to help you solve your problem
you must show us a small-but-runnable piece of code AND data that
exhibits the problem you are seeing. Make sure you use strict and
warnings too.
For example:
#!/usr/bin/perl
use strict;
use warnings;
my $screen_query = <<END;
20,1115,1082,1083,1086,1088,1089,1090|select
master_table.ticker,master_table.comp_name,DIV_YIELD,NET_MARGIN,
DEBT_TO_EQUITY,PRICE_TO_BOOK,PRICE_TO_CASH,PRICE_TO_SALES
from master_table,prices,stock_data,daily_zacks_rank where
master_table.m_ticker=stock_data.m_ticker and
master_table.m_ticker=prices.m_ticker and
master_table.m_ticker=daily_zacks_rank.m_ticker AND
upper(PRICE_TO_BOOK) <= 1.2 AND upper(PRICE_TO_CASH) >= 1.5 AND
upper(PRICE_TO_SALES) <= 1.2
END
my $string = ' AND ';
my $d = index($screen_query, $string);
print "POSITION IS HERE: $d\n";
If you cut-and-paste the above program into perl you see the output:
POSITION IS HERE: 394
Now, please show us a sample of the problem you are having, in the
same way.
------------------------------
Date: Tue, 11 Sep 2007 04:42:19 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Sep 11 2007
Message-Id: <Jo6t2J.sCH@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.
Apache2-S3-0.01
http://search.cpan.org/~iwade/Apache2-S3-0.01/
mod_perl library for proxying requests to amazon S3
----
Apache2-S3-0.02
http://search.cpan.org/~iwade/Apache2-S3-0.02/
mod_perl library for proxying requests to amazon S3
----
Atompub-0.1.0
http://search.cpan.org/~takeru/Atompub-0.1.0/
Atom Publishing Protocol implementation
----
Bio-Grep-v0.10.1
http://search.cpan.org/~limaone/Bio-Grep-v0.10.1/
Perl extension for searching in DNA and Protein sequences
----
CGI-Application-Plugin-HelpMan-1.08
http://search.cpan.org/~leocharre/CGI-Application-Plugin-HelpMan-1.08/
man lookup and help doc for your cgi app
----
CGI-Application-Plugin-Menu-1.02
http://search.cpan.org/~leocharre/CGI-Application-Plugin-Menu-1.02/
manage navigation menus for cgi apps
----
CGI-Application-Plugin-Menu-1.03
http://search.cpan.org/~leocharre/CGI-Application-Plugin-Menu-1.03/
manage navigation menus for cgi apps
----
CPAN-Reporter-0.99_09
http://search.cpan.org/~dagolden/CPAN-Reporter-0.99_09/
Adds CPAN Testers reporting to CPAN.pm
----
Catalyst-Controller-Atompub-0.0.1
http://search.cpan.org/~takeru/Catalyst-Controller-Atompub-0.0.1/
A Catalyst controller for the Atom Publishing Protocol
----
Catalyst-Controller-Atompub-0.0.2
http://search.cpan.org/~takeru/Catalyst-Controller-Atompub-0.0.2/
A Catalyst controller for the Atom Publishing Protocol
----
Class-Dot-1.0.0
http://search.cpan.org/~asksh/Class-Dot-1.0.0/
Simple way of creating accessor methods.
----
Class-Dot-Model-0.1.1
http://search.cpan.org/~asksh/Class-Dot-Model-0.1.1/
Simple way of defining models for DBIx::Class.
----
Class-Method-Modifiers-0.06
http://search.cpan.org/~sartak/Class-Method-Modifiers-0.06/
provides Moose-like method modifiers
----
Class-Plugin-Util-0.007
http://search.cpan.org/~asksh/Class-Plugin-Util-0.007/
Utility functions for supporting Plug-ins.
----
Config-PlConfig-0.1_01
http://search.cpan.org/~asksh/Config-PlConfig-0.1_01/
Maintain a single place for configuration files.
----
Crypt-UnixCrypt_XS-0.08
http://search.cpan.org/~borisz/Crypt-UnixCrypt_XS-0.08/
perl xs interface for a portable traditional crypt function.
----
DBIx-Lookup-Field-1.22
http://search.cpan.org/~marcel/DBIx-Lookup-Field-1.22/
Create a lookup hash from a database table
----
Data-Alias-1.07
http://search.cpan.org/~xmath/Data-Alias-1.07/
Comprehensive set of aliasing operations
----
Date-Manip-5.46
http://search.cpan.org/~sbeck/Date-Manip-5.46/
date manipulation routines
----
DateTime-0.41
http://search.cpan.org/~drolsky/DateTime-0.41/
A date and time object
----
Devel-STDERR-Indent-0.03
http://search.cpan.org/~nuffin/Devel-STDERR-Indent-0.03/
Indents STDERR to aid in print-debugging recursive algorithms.
----
File-PathInfo-1.17
http://search.cpan.org/~leocharre/File-PathInfo-1.17/
access to path variables, stat data, misc info about a file
----
GRID-Machine-0.079
http://search.cpan.org/~casiano/GRID-Machine-0.079/
Remote Procedure Calls over a SSH link
----
Geo-GoogleEarth-Document-0.01
http://search.cpan.org/~mrdvt/Geo-GoogleEarth-Document-0.01/
Creates a GoogleEarth KML Document
----
Geo-GoogleEarth-Document-0.02
http://search.cpan.org/~mrdvt/Geo-GoogleEarth-Document-0.02/
Creates a GoogleEarth KML Document
----
Getopt-LL-0.0.6
http://search.cpan.org/~asksh/Getopt-LL-0.0.6/
Flexible argument processing.
----
Graph-Easy-0.59
http://search.cpan.org/~tels/Graph-Easy-0.59/
Render graphs as ASCII, HTML, SVG or via Graphviz
----
HTML-Template-Compiled-0.88
http://search.cpan.org/~tinita/HTML-Template-Compiled-0.88/
Template System Compiles HTML::Template files to Perl code
----
LEOCHARRE-Class-0.01
http://search.cpan.org/~leocharre/LEOCHARRE-Class-0.01/
----
LEOCHARRE-DEBUG-1.06
http://search.cpan.org/~leocharre/LEOCHARRE-DEBUG-1.06/
my default debug subroutines
----
MIME-Types-1.21
http://search.cpan.org/~markov/MIME-Types-1.21/
Definition of MIME types
----
Math-Expression-Evaluator-0.0.1
http://search.cpan.org/~moritz/Math-Expression-Evaluator-0.0.1/
parses and evaluates mathematic expressions
----
Math-Random-MT-Auto-6.04
http://search.cpan.org/~jdhedden/Math-Random-MT-Auto-6.04/
Auto-seeded Mersenne Twister PRNGs
----
Math-Random-MT-Auto-6.05
http://search.cpan.org/~jdhedden/Math-Random-MT-Auto-6.05/
Auto-seeded Mersenne Twister PRNGs
----
Math-Random-MT-Auto-6.06
http://search.cpan.org/~jdhedden/Math-Random-MT-Auto-6.06/
Auto-seeded Mersenne Twister PRNGs
----
Math-SigFigs-1.05
http://search.cpan.org/~sbeck/Math-SigFigs-1.05/
do math with correct handling of significant figures
----
Module-Build-PM_Filter-0.7
http://search.cpan.org/~vmoral/Module-Build-PM_Filter-0.7/
Add a PM_Filter feature to Module::Build
----
Module-Build-PM_Filter-0.8
http://search.cpan.org/~vmoral/Module-Build-PM_Filter-0.8/
Add a PM_Filter feature to Module::Build
----
Net-Z3950-SimpleServer-1.08
http://search.cpan.org/~mirk/Net-Z3950-SimpleServer-1.08/
Simple Perl API for building Z39.50 servers.
----
Net-Z3950-SimpleServer-1.09
http://search.cpan.org/~mirk/Net-Z3950-SimpleServer-1.09/
Simple Perl API for building Z39.50 servers.
----
POE-Component-Client-NRPE-0.05
http://search.cpan.org/~bingos/POE-Component-Client-NRPE-0.05/
a POE Component that implements check_nrpe functionality
----
POE-Component-Client-Stomp-Utils-0.01
http://search.cpan.org/~kesteb/POE-Component-Client-Stomp-Utils-0.01/
A set of utility routines for POE clients that wish to use a Message Queue server that understands the Stomp protocol.
----
POE-Component-Server-NRPE-0.05
http://search.cpan.org/~bingos/POE-Component-Server-NRPE-0.05/
A POE Component implementation of NRPE Daemon.
----
Package-Data-Inheritable-0.03
http://search.cpan.org/~gcerrai/Package-Data-Inheritable-0.03/
Inheritable and overridable package data/variables
----
Passwd-Linux-1.2
http://search.cpan.org/~eestabroo/Passwd-Linux-1.2/
Perl module for manipulating the passwd and shadow files
----
Passwd-Solaris-1.2
http://search.cpan.org/~eestabroo/Passwd-Solaris-1.2/
Perl module for manipulating the passwd and shadow files
----
SOAP-WSDL-2.00_13
http://search.cpan.org/~mkutter/SOAP-WSDL-2.00_13/
SOAP with WSDL support
----
SQL-Script-0.03
http://search.cpan.org/~adamk/SQL-Script-0.03/
An object representing a series of SQL statements, normally stored in a file
----
SQLite-Archive-0.01
http://search.cpan.org/~adamk/SQLite-Archive-0.01/
Version-agnostic storage and manipulation of SQLite databases
----
Set-Files-1.00
http://search.cpan.org/~sbeck/Set-Files-1.00/
routines to work with files, each definining a single set
----
Sort-Key-Top-0.03
http://search.cpan.org/~salva/Sort-Key-Top-0.03/
select and sort top n elements
----
Speech-eSpeak-0.22
http://search.cpan.org/~hgneng/Speech-eSpeak-0.22/
Perl extension for eSpeak text to speech
----
Template-Like-0.01
http://search.cpan.org/~askadna/Template-Like-0.01/
Lightweight Template Engine.
----
Template-Provider-FromDATA-0.07
http://search.cpan.org/~bricas/Template-Provider-FromDATA-0.07/
Load templates from your __DATA__ section
----
Term-TUI-1.20
http://search.cpan.org/~sbeck/Term-TUI-1.20/
simple tool for building text-based user interfaces
----
Text-ASCIIMathML-0.5
http://search.cpan.org/~nodine/Text-ASCIIMathML-0.5/
Perl extension for parsing ASCIIMathML text into MathML
----
Tie-RefHash-Weak-0.06
http://search.cpan.org/~nuffin/Tie-RefHash-Weak-0.06/
A Tie::RefHash subclass with weakened references in the keys.
----
Tripletail-0.33
http://search.cpan.org/~hio/Tripletail-0.33/
Tripletail, Framework for Japanese Web Application
----
URI-Query-0.06
http://search.cpan.org/~gavinc/URI-Query-0.06/
class providing URI query string manipulation
----
Unicode-Japanese-0.43
http://search.cpan.org/~hio/Unicode-Japanese-0.43/
Japanese Character Encoding Handler 1
----
VCI-0.1.1
http://search.cpan.org/~mkanat/VCI-0.1.1/
A generic interface for interacting with various version-control systems.
----
Verilog-Perl-3.012
http://search.cpan.org/~wsnyder/Verilog-Perl-3.012/
----
Win32-0.31
http://search.cpan.org/~jdb/Win32-0.31/
Interfaces to some Win32 API Functions
----
XML-Atom-Service-0.15.0
http://search.cpan.org/~takeru/XML-Atom-Service-0.15.0/
Atom Service Document object
----
XML-XML2JSON-0.03
http://search.cpan.org/~ken/XML-XML2JSON-0.03/
Convert XML into JSON (and back again) using XML::LibXML
----
smtm_1.6.9
http://search.cpan.org/~edd/smtm_1.6.9/
Display and update a configurable ticker of global stock quotes
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: Tue, 11 Sep 2007 07:10:05 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <hbrFi.1933$4J3.229@newssvr22.news.prodigy.net>
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: Tue, 11 Sep 2007 02:05:23 -0700
From: "fritz-bayer@web.de" <fritz-bayer@web.de>
Subject: Re: Regular Expression
Message-Id: <1189501523.188824.27090@o80g2000hse.googlegroups.com>
On 8 Sep., 07:50, Joe Smith <j...@inwap.com> wrote:
> fritz-ba...@web.de wrote:
> > I'm looking for a regular expression, which is plattform independet
> > and works for java, perl or net.
>
> I'd say you have an impossible task. The advanced parts of perl
> regular expressions that almost do what you want are not implemented
> the same way (if at all) on the other platforms.
>
> -Joe
What about finding all words which are not inside a href tag? So if
I'm looking for the word OUTSIDE, then it should match, if it's not
inside a href. So the following should not match
<a href='/somethin.html'>OUTSIDE</a>
but this should match twice!
OUTSIDE <a href='/somethin.html'>SOME OTHER TEXT</a> OUTSIDE
Can somebody come up with a regular expression that does the job?
------------------------------
Date: Tue, 11 Sep 2007 03:53:08 +0000
From: Peter Makholm <peter@makholm.net>
Subject: Re: Replacing every character in a string with individual <img> tags
Message-Id: <87abrtvowr.fsf@hacking.dk>
Gunnar Hjalmarsson <noreply@gunnar.cc> writes:
> usenet@DavidFilmer.com wrote:
>>
>> $string =~ s/(.)/<img src="$1.gif">/g;
>>
>> But you need to consider if double-quote is one of the "special
>> characters" that you want to allow...
>
> Special? In what sense?
In the senses that <img src="".gif"> probaly isn't parsed the intended
way by most HTML readers.
//Makholm
------------------------------
Date: Mon, 10 Sep 2007 22:17:00 -0700
From: satish2112@gmail.com
Subject: Running Perl script in the backend from Html
Message-Id: <1189487820.344869.167790@w3g2000hsg.googlegroups.com>
Following is my HTML template:
<html>
<head>
<title>Web page</title>
</head>
<body>
<form method="post" action="script.pl">
<p><textarea cols="20" rows="20" name="field"></textarea></
p>
<p><input type="submit" value="update" ></p>
</form>
</body>
</html>
And the Perl Script script.pl is:
#!/usr/bin/perl
use strict;
use warnings;
use CGI;
use DBI;
my $query = new CGI();
my $Value = $query->param('field');
my $dbh = DBI->connect('server address', 'username','password');
my $sth = $dbh->prepare("UPDATE tablename SET columnname = '$Value'
where condition;");
$sth->execute();
$sth->finish();
$dbh->disconnect;
if i click on the submit button, another webpage is opened and the
perl script is executed.
is there any way so that the perl script runs in the backend? ( so
that another webpage doesnt pop-up). how can i modify the above html
code in order to run the perl script in the backend?
------------------------------
Date: Tue, 11 Sep 2007 08:29:32 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: Running Perl script in the backend from Html
Message-Id: <5kmqupF4j3dvU1@mid.individual.net>
satish2112@gmail.com wrote:
> Following is my HTML template:
>
> <html>
> <head>
> <title>Web page</title>
> </head>
> <body>
> <form method="post" action="script.pl">
> <p><textarea cols="20" rows="20" name="field"></textarea></
> p>
> <p><input type="submit" value="update" ></p>
> </form>
> </body>
> </html>
>
> And the Perl Script script.pl is:
>
> #!/usr/bin/perl
> use strict;
> use warnings;
> use CGI;
> use DBI;
>
> my $query = new CGI();
> my $Value = $query->param('field');
>
> my $dbh = DBI->connect('server address', 'username','password');
> my $sth = $dbh->prepare("UPDATE tablename SET columnname = '$Value'
> where condition;");
> $sth->execute();
> $sth->finish();
> $dbh->disconnect;
>
>
> if i click on the submit button, another webpage is opened and the
> perl script is executed.
> is there any way so that the perl script runs in the backend? ( so
> that another webpage doesnt pop-up). how can i modify the above html
> code in order to run the perl script in the backend?
print $query->header(-status=>'204 No Content');
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Tue, 11 Sep 2007 01:48:54 -0000
From: gil <gil.kovary@gmail.com>
Subject: SSH on windows
Message-Id: <1189475334.895066.42550@w3g2000hsg.googlegroups.com>
Hi,
In the last week I'm trying to use Net::SSH unsuccessfully (Windows).
when trying to compile:
use Net::SSH;
my $ssh = new Net::SSH($host, [options]);
$ssh->login('user', 'pass');
my ($out, $err, $exit) = $ssh->cmd('ls');
I receive (after editing Perl.pm) :
Global symbol "$home" requires explicit package name at C:/usr/Perl/
site/lib/Net
/SSH/Perl.pm line 112.
Compilation failed in require at C:/usr/Perl/site/lib/Net/SFTP.pm line
11.
BEGIN failed--compilation aborted at C:/usr/Perl/site/lib/Net/SFTP.pm
line 11.
Compilation failed in require at hello.pl line 3.
BEGIN failed--compilation aborted at hello.pl line 3.
*when I change the value of $home, I receive other errors.
When using Net::SSH::W32Perl, I get some other endless line of errors.
Did some one succeed using SSH on windows???? if yes, which packages
should I use?
Thanks,
Gil
------------------------------
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 840
**************************************
