[27927] in Perl-Users-Digest
Perl-Users Digest, Issue: 9291 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Jun 13 06:05:54 2006
Date: Tue, 13 Jun 2006 03:05:03 -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, 13 Jun 2006 Volume: 10 Number: 9291
Today's topics:
Re: Converting XML to Perl structures FAST <sherm@Sherm-Pendleys-Computer.local>
Re: Converting XML to Perl structures FAST <john@castleamber.com>
Re: Converting XML to Perl structures FAST <ignoramus17503@NOSPAM.17503.invalid>
Re: Converting XML to Perl structures FAST <ignoramus17503@NOSPAM.17503.invalid>
Re: Converting XML to Perl structures FAST robic0
Daemon perl script <janicehwang1325@yahoo.com>
Re: Daemon perl script <bart@nijlen.com>
Re: Looking for a VERY EFFICIENT module for XML robic0
new CPAN modules on Tue Jun 13 2006 (Randal Schwartz)
OT: Anybody using Xemacs to edit Perl Code? <ro.naldfi.scher@gmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Question: Inline::C module packaging? <sisyphus1@nomail.afraid.org>
Re: read a webpage with username/password <jvs@india.ti.com>
Re: Xah Lee network abuse <efuzzyone@netscape.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 12 Jun 2006 21:19:48 -0400
From: Sherm Pendley <sherm@Sherm-Pendleys-Computer.local>
Subject: Re: Converting XML to Perl structures FAST
Message-Id: <m2lks14zt7.fsf@Sherm-Pendleys-Computer.local>
Ignoramus17503 <ignoramus17503@NOSPAM.17503.invalid> writes:
> Aside from a suggestion to look at RXParse, which I will do
Do yourself a favor first, and search Google Groups for robic0.
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: 13 Jun 2006 01:35:08 GMT
From: John Bokma <john@castleamber.com>
Subject: Re: Converting XML to Perl structures FAST
Message-Id: <Xns97E0D168383C5castleamber@130.133.1.4>
Ignoramus17503 <ignoramus17503@NOSPAM.17503.invalid> wrote:
> I installed XML::Twig, and things seem, so far, to be a lot faster and
> CPU use is way down. It is not quite as easy to use, but I can live
> with it.
Uhm, how easy do you want it? Study the manual and the examples.
> I am running my process, which repeatedly parses large XML structures,
The same structure?
--
John Bokma Freelance software developer
&
Experienced Perl programmer: http://castleamber.com/
------------------------------
Date: Tue, 13 Jun 2006 01:45:06 GMT
From: Ignoramus17503 <ignoramus17503@NOSPAM.17503.invalid>
Subject: Re: Converting XML to Perl structures FAST
Message-Id: <CMojg.28078$IQ3.16023@fe06.usenetserver.com>
On Mon, 12 Jun 2006 21:19:48 -0400, Sherm Pendley <sherm@Sherm-Pendleys-Computer.local> wrote:
> Ignoramus17503 <ignoramus17503@NOSPAM.17503.invalid> writes:
>
>> Aside from a suggestion to look at RXParse, which I will do
>
> Do yourself a favor first, and search Google Groups for robic0.
Well, yes, I think that you have a point. Anyway, I am now using
XML::Twig and it seems to be quite stable.
i
------------------------------
Date: Tue, 13 Jun 2006 01:46:46 GMT
From: Ignoramus17503 <ignoramus17503@NOSPAM.17503.invalid>
Subject: Re: Converting XML to Perl structures FAST
Message-Id: <aOojg.28079$IQ3.19915@fe06.usenetserver.com>
On 13 Jun 2006 01:35:08 GMT, John Bokma <john@castleamber.com> wrote:
> Ignoramus17503 <ignoramus17503@NOSPAM.17503.invalid> wrote:
>
>> I installed XML::Twig, and things seem, so far, to be a lot faster and
>> CPU use is way down. It is not quite as easy to use, but I can live
>> with it.
>
> Uhm, how easy do you want it? Study the manual and the examples.
Well, here's how I accessed data with XML::Simple:
my $price = $item->{SellingStatus}->{CurrentPrice}->{content};
Here's how I access it with XML::Twig:
$price = $item->first_child( 'SellingStatus' )->first_child( 'CurrentPrice' )->text;
Clearly, the former is easier.
>> I am running my process, which repeatedly parses large XML structures,
>
> The same structure?
>
Yes, exactly same structures.
i
------------------------------
Date: Mon, 12 Jun 2006 19:05:25 -0700
From: robic0
Subject: Re: Converting XML to Perl structures FAST
Message-Id: <9a7s821s2k1b379ag8kudmmlg4tovh7pnd@4ax.com>
On Mon, 12 Jun 2006 21:19:48 -0400, Sherm Pendley <sherm@Sherm-Pendleys-Computer.local> wrote:
>Ignoramus17503 <ignoramus17503@NOSPAM.17503.invalid> writes:
>
>> Aside from a suggestion to look at RXParse, which I will do
>
>Do yourself a favor first, and search Google Groups for robic0.
robic0
(god of porn)
------------------------------
Date: 12 Jun 2006 18:27:23 -0700
From: "janicehwang1325@yahoo.com" <janicehwang1325@yahoo.com>
Subject: Daemon perl script
Message-Id: <1150162042.938388.36680@f14g2000cwb.googlegroups.com>
hi expert,
I have a client program which is running as daemon and send data to the
server program on the remote site. I m in the testing phase. however,
after running the program for 3 days, suddenly the client program is
killed and no longer active in the client site. wat can be the reason
for this? Is setting scheduling priority using 'renice' can solve the
problem?
Appreciate lots if anyone try to give me some idea.
------------------------------
Date: 13 Jun 2006 02:36:15 -0700
From: "Bart Van der Donck" <bart@nijlen.com>
Subject: Re: Daemon perl script
Message-Id: <1150191375.267751.287730@i40g2000cwc.googlegroups.com>
janicehwang1325@yahoo.com wrote:
> I have a client program which is running as daemon and send data to the
> server program on the remote site. I m in the testing phase.
Traditionally, the server program would be described as the 'listening'
deamon, not the client. The client is typically a program that builds
up a connection with the deamon and quits after it's done.
> after running the program for 3 days, suddenly the client program is
> killed and no longer active in the client site. wat can be the reason
> for this?
It's unlikely that the server software is authorized to kill processes
at the client. I think you should look for a mechanism at the client
side that is responsible for the kill:
- timeout settings (OS-level, Apache/CGI level, Perl level, CPU
(re)nice-level...)
- client's internal error handling (program, socket, used modules,...)
- this may sound too trivial, but maybe there was a reboot or restart
of some software
I would counsel to investigate the logs as much as possible to see what
happened at kill time. I'm thinking an "unexpected condition" occured
which made the client software decide to quit.
> Is setting scheduling priority using 'renice' can solve the
> problem?
I would say normally not (though it wouldn't hurt to keep a friendly
CPU). But AFAIK such things don't kill processes unless you explicitly
allow them to do so under certain conditions.
Hope this helps,
--
Bart
------------------------------
Date: Mon, 12 Jun 2006 18:09:19 -0700
From: robic0
Subject: Re: Looking for a VERY EFFICIENT module for XML
Message-Id: <np3s82lqckjuo293ai29d848g973vi7j4r@4ax.com>
On Mon, 12 Jun 2006 17:41:55 -0700, robic0 wrote:
>On 13 Jun 2006 00:38:07 GMT, Glenn Jackman <glennj@ncf.ca> wrote:
>
>>At 2006-06-12 07:26PM, robic0 <> wrote:
>>> Well, your certainly not responding to me. So my reply is to the others
>>> who try to help you here. The pro's are directed to you though.
>>>
>>> First and last, your one dumb mother fucking retard asshole !!!!!!!!!
>>
>>I wonder why we're not all flocking to your module. Why could it be?
>>Surely it's not the personal and professional support.
>
>From the RXParse tech support group:
>Hey, I don't give a rats ass if you live or die!!!!!!
>
>RXParse support group
Ok, sorry Glenn, that poster used my logon and I just
fired him. That vulgarity is not, and will not be tollerated
within the RXParse group.
My apoligies.
Sincerly,
CEO/President RoParse Technoligies.
R. Cps
------------------------------
Date: Tue, 13 Jun 2006 04:42:08 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Jun 13 2006
Message-Id: <J0s7q8.1C1r@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.
Sub-Pipeline-0.001
http://search.cpan.org/~rjbs/Sub-Pipeline-0.001/
subs composed of sequential pieces
----
DBIx-SimplePerl-1.31
http://search.cpan.org/~landman/DBIx-SimplePerl-1.31/
Perlish access to DBI
----
Java-JCR-0.03
http://search.cpan.org/~hanenkamp/Java-JCR-0.03/
Use JSR 170 (JCR) repositories from Perl
----
Data-FormValidator-4.20
http://search.cpan.org/~markstos/Data-FormValidator-4.20/
Validates user input (usually from an HTML form) based on input profile.
----
XML-XPathScript-1.42
http://search.cpan.org/~yanick/XML-XPathScript-1.42/
a Perl framework for XML stylesheets
----
Geo-ReadGRIB-0.5
http://search.cpan.org/~frankcox/Geo-ReadGRIB-0.5/
Perl extension that gives read access to GRIB "GRIdded Binary" format Weather data files.
----
Task-Latemp-0.0100
http://search.cpan.org/~shlomif/Task-Latemp-0.0100/
Specifications for modules needed by the Latemp CMS.
----
Catalyst-Plugin-Session-Defaults-0.01
http://search.cpan.org/~nuffin/Catalyst-Plugin-Session-Defaults-0.01/
Default values in your session.
----
o2sms-3.13
http://search.cpan.org/~mackers/o2sms-3.13/
A module to send SMS messages using the website of O2 Ireland
----
Rose-DB-Object-0.731
http://search.cpan.org/~jsiracusa/Rose-DB-Object-0.731/
Extensible, high performance RDBMS-OO mapper.
----
Rose-DB-0.71
http://search.cpan.org/~jsiracusa/Rose-DB-0.71/
A DBI wrapper and abstraction layer.
----
Test-WWW-Selenium-1.00
http://search.cpan.org/~lukec/Test-WWW-Selenium-1.00/
Test applications using Selenium Remote Control
----
IO-Socket-SSL-0.98_1
http://search.cpan.org/~sullr/IO-Socket-SSL-0.98_1/
Nearly transparent SSL encapsulation for IO::Socket::INET.
----
Java-JCR-0.02
http://search.cpan.org/~hanenkamp/Java-JCR-0.02/
Use JSR 170 (JCR) repositories from Perl
----
Catalyst-Plugin-ConfigLoader-0.09
http://search.cpan.org/~bricas/Catalyst-Plugin-ConfigLoader-0.09/
Load config files of various types
----
Net-EPP-Frame-0.05
http://search.cpan.org/~gbrown/Net-EPP-Frame-0.05/
An EPP XML frame system built on top of XML::LibXML.
----
Net-EPP-Frame-0.04
http://search.cpan.org/~gbrown/Net-EPP-Frame-0.04/
An EPP XML frame system built on top of XML::LibXML.
----
EasyTool-TimeFunc-1.0.0.01
http://search.cpan.org/~foolfish/EasyTool-TimeFunc-1.0.0.01/
----
URPM-1.44
http://search.cpan.org/~rgarcia/URPM-1.44/
Manipulate RPM files and headers
----
Net-EPP-Proxy-0.03
http://search.cpan.org/~gbrown/Net-EPP-Proxy-0.03/
a proxy server for the EPP protocol.
----
Net-EPP-Frame-0.03
http://search.cpan.org/~gbrown/Net-EPP-Frame-0.03/
An EPP XML frame system built on top of XML::LibXML.
----
MIME-Explode-0.38
http://search.cpan.org/~hdias/MIME-Explode-0.38/
Perl extension for explode MIME messages
----
Acme-MetaSyntactic-0.78
http://search.cpan.org/~book/Acme-MetaSyntactic-0.78/
Themed metasyntactic variables names
----
Inline-C2XS-0.03
http://search.cpan.org/~sisyphus/Inline-C2XS-0.03/
create an XS file from an Inline C file.
----
CGI-FormBuilder-Mail-FormatMultiPart-1.0.0
http://search.cpan.org/~markle/CGI-FormBuilder-Mail-FormatMultiPart-1.0.0/
----
Filter-Template-1.02
http://search.cpan.org/~rcaputo/Filter-Template-1.02/
a source filter for inline code templates (macros)
----
POE-Component-Client-Ping-1.12
http://search.cpan.org/~rcaputo/POE-Component-Client-Ping-1.12/
a non-blocking ICMP ping client
----
Chart-Clicker-0.9.7
http://search.cpan.org/~gphat/Chart-Clicker-0.9.7/
Powerful, extensible charting.
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.
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: 13 Jun 2006 01:41:58 -0700
From: "Ronny" <ro.naldfi.scher@gmail.com>
Subject: OT: Anybody using Xemacs to edit Perl Code?
Message-Id: <1150188118.447908.22830@i40g2000cwc.googlegroups.com>
(This article was originally posted in comp.emacs.xemacs, as this is
the place
where it belongs to, but I didn't get any response there. Hopefully
there are
some Perl programmers using Xemacs who can help me here...)
I'm using Xemacs "right out of the box" to edit Perl code. Xemacs
correctly switches on CPerl mode automatically. However, it seems to
have
a very particular idea, how a Perl program should be laid out: Suppose
I write
a function definition like this:
sub myfunc($)
{
As soon as I type the {, Xemacs positions it exactly under the "$"
sign:
sub myfunc($)
{
(i.e. it places the brace under the $ sign, which is silly IMO).
I suspect that CPerl mode does not properly recognize this as the
start of a function definition at all...
Is this a known problem and does someone have a solution for it?
Ronald
------------------------------
Date: 13 Jun 2006 07:22:28 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <448e67b4$0$50699$ae4e5890@news.nationwide.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.5 $)
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://mail.augustmail.com/~tadmc/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
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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Tue, 13 Jun 2006 11:11:06 +1000
From: "Sisyphus" <sisyphus1@nomail.afraid.org>
Subject: Re: Question: Inline::C module packaging?
Message-Id: <448e1179$0$25133$afc38c87@news.optusnet.com.au>
"Lee" <leegee@gmail.com> wrote in message
news:1150107282.845066.263690@j55g2000cwa.googlegroups.com...
> Is there a preferred method of packaging an Inline::C module, perhaps
> one that would compile the C in the correct place during the
> installation, rather than on first run?
>
My preference is to package it as a normal (cpan-type distro) source
package.
If you run your Inline::C script with the Config option
'CLEAN_AFTER_BUILD=>0', you'll be able to go into the _Inline/build
directory and grab the XS file that it created.
Change the 'MODULE' and 'PACKAGE' entries in that XS file as appropriate,
then bundle the XS file with the other usual files (the normal '.pm',
Makefile.PL, CHANGES, README, MANIFEST, test suite) and you've got a distro
that can be built in the usual way without any dependence upon Inline at
all.
As an alternative, I've put Inline::C2XS on CPAN - which will write the XS
file for you from your Inline::C code. That module should really be doing
its stuff by plugging into the Inline::C module functionality .... but it
doesn't do it that way. Instead it's a (rather poor) wheel-reinvention that
just happens to work for me - and may also work for you if you choose to use
it.
Cheers,
Rob
------------------------------
Date: Tue, 13 Jun 2006 11:04:13 +0530
From: Jahagirdar Vijayvithal S <jvs@india.ti.com>
Subject: Re: read a webpage with username/password
Message-Id: <slrne8sjil.837.jvs@bstclindt008.india.ti.com>
* jiehuang001@hotmail.com <jiehuang001@hotmail.com> wrote:
> I am trying to use perl to extract the content of a webpage, such as an
> online newspaper. For example, I might want to have the program to send
> me any material with the word of "computer".
>
> I know that I can use Get("url") > output.txt to do that. But the
> problem is that to reach to the "url", it needs a username/password to
> login first. Of course, I know the username/password. My question is,
> how to pass the username/password from perl?
>
> Thank you very much!
>
> JH
>
try WWW:Mechanize
Quoting From http://search.cpan.org/dist/WWW-Mechanize/lib/WWW/Mechanize.pm
{QUOTE}
WWW::Mechanize, or Mech for short, helps you automate interaction with a
website. It supports performing a sequence of page fetches including
following links and submitting forms. Each fetched page is parsed and
its links and forms are extracted. A link or a form can be selected,
form fields can be filled and the next page can be fetched. Mech also
stores a history of the URLs you've visited, which can be queried and
revisited.
{/QUOTE}
Regards
Jahagirdar Vijayvithal S
--
"Tell your friend a lie. If he keeps it secret, then tell him the truth." - Portuguese Proverb
Jahagirdar .V.S 91-80-25099129(O) 91-80-28540394(R)
IC Design Engineer RGES-WLAN,
Texas Instruments (India) Ltd.
------------------------------
Date: Tue, 13 Jun 2006 12:46:49 +0530
From: Surendra Singhi <efuzzyone@netscape.net>
Subject: Re: Xah Lee network abuse
Message-Id: <irn5sexq.fsf@netscape.net>
Its not Xah Lee, who abuses the system.
But people like "Erik Max Francis" and "Philippa Cowderoy" who carry on
nonsense discussions across mailing lists.
--
Surendra Singhi
http://ssinghi.kreeti.com
,----
| WHY SHOULD WE SAVE TIGER?
| Ans: Saving the tiger means saving mankind..
|
| Help http://pudang.tripod.com/
| or https://secure.worldwildlife.org/forms/tiger_appeal_1.cfm
`----
------------------------------
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 V10 Issue 9291
***************************************
