[30021] in Perl-Users-Digest
Perl-Users Digest, Issue: 1264 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Feb 8 06:09:37 2008
Date: Fri, 8 Feb 2008 03:09:04 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 8 Feb 2008 Volume: 11 Number: 1264
Today's topics:
Help with HTML:TableContentParser roberthuberjr@gmail.com
Re: Help with HTML:TableContentParser <glex_no-spam@qwest-spam-no.invalid>
Re: Help with HTML:TableContentParser <uri@stemsystems.com>
Re: lcd via NET::FTP <joserrahervas@gmail.com>
new CPAN modules on Fri Feb 8 2008 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: problem with '>' character <peter@makholm.net>
Re: problem with '>' character <uri@stemsystems.com>
Re: problem with '>' character <stoupa@practisoft.cz>
Re: problem with '>' character <peter@makholm.net>
Re: problem with '>' character <abigail@abigail.be>
Re: XS code <ben@morrow.me.uk>
Re: XS code <robert.henniger@googlemail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 7 Feb 2008 13:44:33 -0800 (PST)
From: roberthuberjr@gmail.com
Subject: Help with HTML:TableContentParser
Message-Id: <1b3f280a-8ae7-4c90-9361-f9a874dd8967@n20g2000hsh.googlegroups.com>
I have an html file I'm reading in from my file system (not via
get($URL) that I'm trying to parse the table from using
HTML::TableContentParser.
My script runs, but produces no results. I'm thinking I need to read
the file into an arrary to get the parser to work on it. Here's my
code (lifted from the Perl cookbook mostly) -
#!/usr/bin/perl
use HTML::TableContentParser;
use HTML::Entities;
use strict;
my $FILE = open("<netflow_data");
#??????read the file into an arrary maybe????
my $tcp = new HTML::TableContentParser;
my $tables = $tcp->parse($FILE);
my $modules = $tables->[1];
foreach my $r (@{ $modules->{rows} })
{
my ($date_time, $sip, $dip, $protocol, $sport, $dport,
$tcpflags, $tos, $num_pkts, $num_octets, $srcasn, $dstasn) =
parse_module_row($r, $FILE);
print "$date_time $sip $dip $protocol $sport $dport $tcpflags
$tos $num_pkts $num_octets $$srcasn $dstasn\n";
}
sub parse_module_row
{
my ($row, $FILE) = @_;
my ($date_time, $sip, $dip, $protocol, $sport, $dport,
$tcpflags, $tos, $num_pkts, $num_octets, $srcasn, $dstasn);
$date_time = $row->{cells}[0]{data};
$sip = $row->{cells}[1]{data};
$dip = $row->{cells}[2]{data};
$protocol = $row->{cells}[3]{data};
$sport = $row->{cells}[4]{data};
$dport = $row->{cells}[5]{data};
$tcpflags = $row->{cells}[6]{data};
$tos = $row->{cells}[7]{data};
$num_pkts = $row->{cells}[8]{data};
$num_octets = $row->{cells}[9]{data};
$srcasn = $row->{cells}[10]{data};
$dstasn = $row->{cells}[10]{data};
return ($date_time, $sip, $dip, $protocol, $sport, $dport,
$tcpflags, $tos, $num_pkts, $num_octets, $srcasn, $dstasn);
}
------------------------------
Date: Thu, 07 Feb 2008 16:04:18 -0600
From: "J. Gleixner" <glex_no-spam@qwest-spam-no.invalid>
Subject: Re: Help with HTML:TableContentParser
Message-Id: <47ab8063$0$3567$815e3792@news.qwest.net>
roberthuberjr@gmail.com wrote:
> I have an html file I'm reading in from my file system (not via
> get($URL) that I'm trying to parse the table from using
> HTML::TableContentParser.
>
> My script runs, but produces no results. I'm thinking I need to read
> the file into an arrary to get the parser to work on it. Here's my
> code (lifted from the Perl cookbook mostly) -
>
> #!/usr/bin/perl
> use HTML::TableContentParser;
> use HTML::Entities;
> use strict;
> my $FILE = open("<netflow_data");
That doesn't do what you think it does.
open( my $file, '<', 'netflow_data')
or die "Can't read netflow_data: $!";
perldoc -f open
To learn how to read in the contents of the file
perldoc perlopentut
or
perldoc File::Slurp
> #??????read the file into an arrary maybe????
> my $tcp = new HTML::TableContentParser;
> my $tables = $tcp->parse($FILE);
Never used it, but looking at the example in the documentation:
use HTML::TableContentParser;
$p = HTML::TableContentParser->new();
$html = read_html_from_somewhere();
$tables = $p->parse($html);
You need to read the information from the
file and pass that to parse(). Reading the
above perldoc(umentation) should help you figure
out how to read a file.
------------------------------
Date: Thu, 07 Feb 2008 22:17:41 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Help with HTML:TableContentParser
Message-Id: <x77ihgv2be.fsf@mail.sysarch.com>
>>>>> "r" == roberthuberjr <roberthuberjr@gmail.com> writes:
r> my $modules = $tables->[1];
r> foreach my $r (@{ $modules->{rows} })
r> {
r> my ($date_time, $sip, $dip, $protocol, $sport, $dport,
r> $tcpflags, $tos, $num_pkts, $num_octets, $srcasn, $dstasn) =
r> parse_module_row($r, $FILE);
GACK!!
use a hash or something. returning long lists of scalars is bug prone
and painful to read.
r> sub parse_module_row
r> {
r> my ($row, $FILE) = @_;
r> my ($date_time, $sip, $dip, $protocol, $sport, $dport,
r> $tcpflags, $tos, $num_pkts, $num_octets, $srcasn, $dstasn);
declare those where you need them
r> $date_time = $row->{cells}[0]{data};
my $date_time = $row->{cells}[0]{data};
r> $sip = $row->{cells}[1]{data};
r> $dip = $row->{cells}[2]{data};
r> $protocol = $row->{cells}[3]{data};
r> $sport = $row->{cells}[4]{data};
r> $dport = $row->{cells}[5]{data};
r> $tcpflags = $row->{cells}[6]{data};
r> $tos = $row->{cells}[7]{data};
r> $num_pkts = $row->{cells}[8]{data};
r> $num_octets = $row->{cells}[9]{data};
r> $srcasn = $row->{cells}[10]{data};
r> $dstasn = $row->{cells}[10]{data};
do you notice any repetition in that code? i can barely see the
differences as it is almost all repeated code.
the last two are the same data. is that a bug? another reason to not do
repeated lines where you edit each one slightly
first, factor out $row->{cells} into $cells
my $cells = $row->{cells} ;
then you can use a hash to get all the data with a simpler slice and
map:
# declare this outside the sub:
my( @fields ) = qw(
date_time sip dip protocol sport dport tcpflags tos
num_pkts num_octets srcasn dstasn
) ;
my %row ;
@row{ @fields } = map $cells->[$_]{data}, 0 .. $#fields ;
return \%row ;
look ma, no fugly repetition!!
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Architecture, Development, Training, Support, Code Review ------
----------- Search or Offer Perl Jobs ----- http://jobs.perl.org ---------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Fri, 8 Feb 2008 02:45:33 -0800 (PST)
From: Joserra <joserrahervas@gmail.com>
Subject: Re: lcd via NET::FTP
Message-Id: <8bfa7f60-e5c2-4e74-940f-1471acc6579f@c4g2000hsg.googlegroups.com>
On 6 feb, 07:24, vikram <vikramgan...@gmail.com> wrote:
> Hi Everyone,
>
> I want to view the local current directory using perl Net::FTP
> module..When i use lcd("local folder") its showing me the error.
>
> Can't locate object method "lcd" via package "Net::FTP"
>
> Thanks in advance.
You could use ls("folder") method or if you want more detail
information you could use dir("folder") method. For viewing the local
current directory, I use ls("").
Example:
...
my $ftp = Net::FTP->new($IP);
$ftp->login($USER,$PASSWORD);
my @files = $ftp->ls("");
...
------------------------------
Date: Fri, 8 Feb 2008 05:42:16 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri Feb 8 2008
Message-Id: <JvwnuG.uLt@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.
Acme-POE-Acronym-Generator-1.08
http://search.cpan.org/~bingos/Acme-POE-Acronym-Generator-1.08/
Generate random POE acronyms.
----
Apache2-DirBasedHandler-0.01
http://search.cpan.org/~aprime/Apache2-DirBasedHandler-0.01/
Directory based Location Handler helper
----
Apache2-Filter-TagAware-0.02
http://search.cpan.org/~aprime/Apache2-Filter-TagAware-0.02/
Tag Awareness for Apache2::Filter
----
CGI-JSONRPC-0.05
http://search.cpan.org/~crakrjack/CGI-JSONRPC-0.05/
CGI handler for JSONRPC
----
CGI-JSONRPC-0.06
http://search.cpan.org/~crakrjack/CGI-JSONRPC-0.06/
CGI handler for JSONRPC
----
Catalyst-Authentication-Store-DBIx-Class-0.102
http://search.cpan.org/~jayk/Catalyst-Authentication-Store-DBIx-Class-0.102/
A storage class for Catalyst Authentication using DBIx::Class
----
Config-INI-Simple-0.02
http://search.cpan.org/~kirsle/Config-INI-Simple-0.02/
Simple reading and writing from an INI file--with preserved comments, too!
----
Config-Validate-0.2.0
http://search.cpan.org/~cmo/Config-Validate-0.2.0/
Validate data structures generated from configuration files. (Or anywhere else)
----
Cvs-Simple-0.06
http://search.cpan.org/~stephenca/Cvs-Simple-0.06/
Perl interface to cvs
----
Cvs-Simple-0.6
http://search.cpan.org/~stephenca/Cvs-Simple-0.6/
Perl interface to cvs
----
DBD-SQLite-Amalgamation-3.5.6
http://search.cpan.org/~audreyt/DBD-SQLite-Amalgamation-3.5.6/
Single C-file based DBD::SQLite distribution
----
DBIx-Perlish-0.37
http://search.cpan.org/~gruber/DBIx-Perlish-0.37/
a perlish interface to SQL databases
----
Data-Formatter-Text-0.02
http://search.cpan.org/~zblair/Data-Formatter-Text-0.02/
Perl extension for formatting data stored in scalars, hashes, and arrays into strings, definition lists, and bulletted lists, etc. using plain ASCII text.
----
EekBoek-1.03.07_01
http://search.cpan.org/~jv/EekBoek-1.03.07_01/
Bookkeeping software for small and medium-size businesses
----
FProt-Client-0.09
http://search.cpan.org/~avar/FProt-Client-0.09/
Client interface to the fpscand(1) virus scanning daemon
----
Fey-Test-0.03
http://search.cpan.org/~drolsky/Fey-Test-0.03/
Test libraries for Fey distros
----
Hardware-Simulator-MIX-0.08
http://search.cpan.org/~litchie/Hardware-Simulator-MIX-0.08/
----
IPC-Locker-1.481
http://search.cpan.org/~wsnyder/IPC-Locker-1.481/
Distributed lock handler
----
Iterator-File-Line-0.00001
http://search.cpan.org/~dmaki/Iterator-File-Line-0.00001/
Iterate A File By Line
----
Keystone-Resolver-1.17
http://search.cpan.org/~mirk/Keystone-Resolver-1.17/
an OpenURL resolver
----
Language-MuldisD-0.19.1
http://search.cpan.org/~duncand/Language-MuldisD-0.19.1/
Formal spec of Muldis D relational DBMS lang
----
Language-MuldisD-0.20.0
http://search.cpan.org/~duncand/Language-MuldisD-0.20.0/
Formal spec of Muldis D relational DBMS lang
----
Log-Log4perl-Layout-PatternLayout-Elapsed-0.02
http://search.cpan.org/~potyl/Log-Log4perl-Layout-PatternLayout-Elapsed-0.02/
Logs the time elapsed between the last log event
----
Microarray-0.41
http://search.cpan.org/~cjones/Microarray-0.41/
A Perl module for creating and manipulating microarray objects
----
Microarray-0.41b
http://search.cpan.org/~cjones/Microarray-0.41b/
A Perl module for creating and manipulating microarray objects
----
MooseX-LogDispatch-1.1001
http://search.cpan.org/~ash/MooseX-LogDispatch-1.1001/
A Logging Role for Moose
----
Net-Hiveminder-0.04
http://search.cpan.org/~sartak/Net-Hiveminder-0.04/
Perl interface to hiveminder.com
----
Net-Radius-Client-0.02
http://search.cpan.org/~ilya/Net-Radius-Client-0.02/
Pure-Perl, VSA-empowered RADIUS client
----
POE-Component-IRC-5.62
http://search.cpan.org/~bingos/POE-Component-IRC-5.62/
a fully event-driven IRC client module.
----
POE-Component-IRC-Plugin-CPAN-Info-0.03
http://search.cpan.org/~zoffix/POE-Component-IRC-Plugin-CPAN-Info-0.03/
PoCo::IRC plugin for accessing information about CPAN modules, distributions and authors.
----
POE-Component-Server-RADIUS-0.04
http://search.cpan.org/~bingos/POE-Component-Server-RADIUS-0.04/
a POE based RADIUS server component
----
POEIKCdaemon-0.00_06
http://search.cpan.org/~suzuki/POEIKCdaemon-0.00_06/
POE IKC daemon
----
Rose-DBx-Object-Loader-FormMaker-0.01
http://search.cpan.org/~aprime/Rose-DBx-Object-Loader-FormMaker-0.01/
----
Sledge-Plugin-JSON-XS-0.01
http://search.cpan.org/~tokuhirom/Sledge-Plugin-JSON-XS-0.01/
JSON::XS wrapper for Sledge
----
Sys-Statistics-Linux-0.26_01
http://search.cpan.org/~bloonix/Sys-Statistics-Linux-0.26_01/
Front-end module to collect system statistics
----
Sysadm-Install-0.25
http://search.cpan.org/~mschilli/Sysadm-Install-0.25/
Typical installation tasks for system administrators
----
Term-Menus-1.32
http://search.cpan.org/~reedfish/Term-Menus-1.32/
Create Powerful Terminal, Console and CMD Enviroment Menus
----
Term-ReadLine-Gnu-1.17
http://search.cpan.org/~hayashi/Term-ReadLine-Gnu-1.17/
Perl extension for the GNU Readline/History Library
----
Term-ReadLine-Gnu-1.17a
http://search.cpan.org/~hayashi/Term-ReadLine-Gnu-1.17a/
Perl extension for the GNU Readline/History Library
----
Util-Properties-0.17
http://search.cpan.org/~alexmass/Util-Properties-0.17/
Java.util.properties like class
----
Variable-Magic-0.11
http://search.cpan.org/~vpit/Variable-Magic-0.11/
Associate user-defined magic to variables from Perl.
----
Variable-Magic-0.12
http://search.cpan.org/~vpit/Variable-Magic-0.12/
Associate user-defined magic to variables from Perl.
----
XML-OPML-SimpleGen-0.03
http://search.cpan.org/~stephenca/XML-OPML-SimpleGen-0.03/
create OPML using XML::Simple
----
XML-RPC-0.6
http://search.cpan.org/~daan/XML-RPC-0.6/
Pure Perl implementation for an XML-RPC client and server.
----
cpan_bot-0.01
http://search.cpan.org/~zoffix/cpan_bot-0.01/
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: Fri, 08 Feb 2008 08:15:21 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <tcUqj.6455$0w.1258@newssvr27.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: Thu, 07 Feb 2008 21:29:06 +0000
From: Peter Makholm <peter@makholm.net>
Subject: Re: problem with '>' character
Message-Id: <877ihgh2vx.fsf@hacking.dk>
Uri Guttman <uri@stemsystems.com> writes:
> PM> Yes, I'm quite aware of that and the documentation will surly tell you
> PM> which one.
>
> so why do you mention both and not report what the docs said there?
Because I don't need to know. I rarely use multi line regexps so I
would have to look up 'perldoc perlre' to give a more precise
answer. If my assumption had been right, the original poster would
have been able to do it just as easy.
//Makholm
------------------------------
Date: Thu, 07 Feb 2008 22:09:35 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: problem with '>' character
Message-Id: <x7bq6sv2ow.fsf@mail.sysarch.com>
>>>>> "PM" == Peter Makholm <peter@makholm.net> writes:
PM> Uri Guttman <uri@stemsystems.com> writes:
PM> Yes, I'm quite aware of that and the documentation will surly tell you
PM> which one.
>>
>> so why do you mention both and not report what the docs said there?
PM> Because I don't need to know. I rarely use multi line regexps so I
PM> would have to look up 'perldoc perlre' to give a more precise
PM> answer. If my assumption had been right, the original poster would
PM> have been able to do it just as easy.
then you shouldn't answer such questions. you made an assumption which
is useless even if correct.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Architecture, Development, Training, Support, Code Review ------
----------- Search or Offer Perl Jobs ----- http://jobs.perl.org ---------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Fri, 8 Feb 2008 03:49:28 +0100
From: "Petr Vileta" <stoupa@practisoft.cz>
Subject: Re: problem with '>' character
Message-Id: <fogg9n$13pf$2@ns.felk.cvut.cz>
JD wrote:
> On 2008-02-07, Abigail <abigail@abigail.be> wrote:
>> _
>>
>> That seems like a bug.
>>
>
> Found it: It was a a file from a MS-Windows system, with CRLF line
> ends. chomp removed the LF, but the CR was still there :(
>
>
> dos2unix solved it.
Or you can use regexp intead of chomp
s/[\r\n]//;
--
Petr Vileta, Czech republic
(My server rejects all messages from Yahoo and Hotmail. Send me your
mail from another non-spammer site please.)
Please reply to <petr AT practisoft DOT cz>
------------------------------
Date: Fri, 08 Feb 2008 06:08:37 +0000
From: Peter Makholm <peter@makholm.net>
Subject: Re: problem with '>' character
Message-Id: <873as4geu2.fsf@hacking.dk>
Uri Guttman <uri@stemsystems.com> writes:
> then you shouldn't answer such questions. you made an assumption which
> is useless even if correct.
I don't agree, but I should have refered to 'perldoc perlre' instead
of just the docs.
//Makholm
------------------------------
Date: 08 Feb 2008 09:01:29 GMT
From: Abigail <abigail@abigail.be>
Subject: Re: problem with '>' character
Message-Id: <slrnfqo6j9.ifi.abigail@alexandra.abigail.be>
_
Petr Vileta (stoupa@practisoft.cz) wrote on VCCLXXIV September MCMXCIII
in <URL:news:fogg9n$13pf$2@ns.felk.cvut.cz>:
&& JD wrote:
&& > On 2008-02-07, Abigail <abigail@abigail.be> wrote:
&& >> _
&& >>
&& >> That seems like a bug.
&& >>
&& >
&& > Found it: It was a a file from a MS-Windows system, with CRLF line
&& > ends. chomp removed the LF, but the CR was still there :(
&& >
&& >
&& > dos2unix solved it.
&& Or you can use regexp intead of chomp
&&
&& s/[\r\n]//;
That just deletes the first CR *or* NL from the string. This has the
problem that instead of leaving the CR, it leaves the NL.
If you want to use a regexp, I'd use:
s/\R//;
or, if you're working with an old perl:
s/\r?\n|\r//
Abigail
--
$" = "/"; split // => eval join "+" => 1 .. 7;
*{"@_"} = sub {foreach (sort keys %_) {print "$_ $_{$_} "}};
%_ = (Just => another => Perl => Hacker); &{%_};
------------------------------
Date: Fri, 8 Feb 2008 00:52:30 +0000
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: XS code
Message-Id: <enls75-ktm2.ln1@osiris.mauzo.dyndns.org>
Quoth Robert Henniger <robert.henniger@googlemail.com>:
>
> Today I tried to compile my script to an .NET DLL.
>
> This script uses HTML::Template::Pro. The compile process works well.
> When I try to use this dll then I get the following message:
>
> Unhandled Exception: PerlRuntime.PerlException: Can't locate auto/HTML/
> Template/Pro/query.al in @INC (@INC contains: .... .)
This means something is trying to call the function
HTML::Template::Pro::query, and HTP is attempting to load it with
AutoLoader. This is strange for two reasons: HTP doesn't define a query
function, and AFAICS doesn't use AutoLoader. It's possible that v0.61
used AutoLoader: the oldest version on CPAN is 0.65.
Did you get your program running correctly *before* you tried to build a
dll? If not, do that. My guess would be you're calling the
HTML::Template->query method, which is not supported by HTP.
> Maybe someone can help me and explain what a .al file do and why it is
> needed.
It is used by AutoLoader to load perl subs on demand. These files are
build and installed when you install a module, if the module uses
AutoLoading.
> Is there something i have to change when i use modules with xs parts?
I wouldn't have thought so; but in general you need to make sure all the
files your program needs are included in the DLL. I'm sure the tool
you're using will list the files it includes, and let you edit that list
somehow.
Ben
------------------------------
Date: Thu, 7 Feb 2008 23:16:59 -0800 (PST)
From: Robert Henniger <robert.henniger@googlemail.com>
Subject: Re: XS code
Message-Id: <809978a6-c590-4ea4-8a87-6b891dfff293@m34g2000hsf.googlegroups.com>
On 8 Feb., 01:52, Ben Morrow <b...@morrow.me.uk> wrote:
> Quoth Robert Henniger <robert.henni...@googlemail.com>:
>
>
>
> > Today I tried to compile my script to an .NET DLL.
>
> > This script uses HTML::Template::Pro. The compile process works well.
> > When I try to use this dll then I get the following message:
>
> > Unhandled Exception: PerlRuntime.PerlException: Can't locate auto/HTML/
> > Template/Pro/query.al in @INC (@INC contains: .... .)
>
> This means something is trying to call the function
> HTML::Template::Pro::query, and HTP is attempting to load it with
> AutoLoader. This is strange for two reasons: HTP doesn't define a query
> function, and AFAICS doesn't use AutoLoader. It's possible that v0.61
> used AutoLoader: the oldest version on CPAN is 0.65.
>
> Did you get your program running correctly *before* you tried to build a
> dll? If not, do that. My guess would be you're calling the
> HTML::Template->query method, which is not supported by HTP.
>
> > Maybe someone can help me and explain what a .al file do and why it is
> > needed.
>
> It is used by AutoLoader to load perl subs on demand. These files are
> build and installed when you install a module, if the module uses
> AutoLoading.
>
> > Is there something i have to change when i use modules with xs parts?
>
> I wouldn't have thought so; but in general you need to make sure all the
> files your program needs are included in the DLL. I'm sure the tool
> you're using will list the files it includes, and let you edit that list
> somehow.
>
> Ben
Hi Ben.
Thank you very very much for your feedback.
Maybe I should learn to read the documentation a bit more precisly.
I checked my code, and of course i am using the query methode. And yes
this methode is not implemented yet.
Do you know if it is possible to implement this methode in the perl
part or do i have to do that in the xs code?
I am very sorry that i wasted your time with my stupid questions.
Robert
------------------------------
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 1264
***************************************
