[32082] in Perl-Users-Digest
Perl-Users Digest, Issue: 3346 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Apr 8 06:09:26 2011
Date: Fri, 8 Apr 2011 03:09:10 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 8 Apr 2011 Volume: 11 Number: 3346
Today's topics:
[cross posting] - weird Postgres commit behavior with P <nobody@nowhere.net>
cond_wait problem with Thread::Pool <davidmichaelkarr@gmail.com>
Re: cond_wait problem with Thread::Pool <davidmichaelkarr@gmail.com>
Re: FAQ 9.20 How do I send mail? <usenet05@drabble.me.uk>
Re: FAQ 9.20 How do I send mail? <hjp-usenet2@hjp.at>
Re: FAQ 9.20 How do I send mail? <brian.d.foy@gmail.com>
Re: How to queue each loop iteration into a thread pool <davidmichaelkarr@gmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Posting Guidelines for comp.lang.perl.misc ($Revisi <hjp-usenet2@hjp.at>
Re: Posting Guidelines for comp.lang.perl.misc ($Revisi <kkeller-usenet@wombat.san-francisco.ca.us>
Removing data between two HTML tags? <rdw204@gmail.com>
Re: Removing data between two HTML tags? <monkey_vegas@cox.net>
Re: Removing data between two HTML tags? <marc.girod@gmail.com>
Re: Removing data between two HTML tags? <marc.girod@gmail.com>
Re: Search script to index dynamic pages <rdw204@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 07 Apr 2011 18:53:40 +0200
From: Anselmo Canfora <nobody@nowhere.net>
Subject: [cross posting] - weird Postgres commit behavior with Perl DBI
Message-Id: <4d9dec22$0$6825$5fc30a8@news.tiscali.it>
Hi all,
I apologize in advance for cross posting and for the rather long post.
I am loading some big tables (three tables with ~580000, ~468000, and
~248000 rows) on Postgres 8.3 db with data retrieved from two different
types of network devices and from a Oracle database.
To do so in a speedy way I am using a Perl thread with its own db
connection for each device, therefore I have about 175 thread running
concurrently and 175 db connections. I just detected a weird behavior
with one of three type of threads, (I have 131 threads of this type).
In this case I load the table with data retrieved from network devices
(routers) and, as soon as done with it, in the same thread, I start to
update *same* rows just inserted with other data collected from the same
router.
Briefly the script does something like this:
...
my $insert=$pch->prepare("insert into mytable (...fields...) values
('$device', ...?...)");
while(...loop on device...){
... parsing data...
$insert->execute($1, $2, $3);
}
... FIRST PART OF THREAD STOPS HERE ...
my $traffsh=$pch->prepare("update mytable set traffic=? where id=?");
my $pvcsh=$pch->prepare("select * from mytable where device='$device'");
$pvcsh->execute;
while($r=$pvcsh->fetchrow_hashref('NAME_lc')){
... code to retrieve statistics from device ...
$traffsh->execute($1+$2, $r->{id});
}
With the first version of my script I kept autocommit enabled. With that
version only a small part (~50k over ~460k) of the table got the update,
like Postgres did not completed the insertions in spite it was returning
from ->execute (one transaction for each insertion).
Then, to speed up things and in suspicion for an issue, I disabled
autocommit and put a ->commit after the first part of thread. With only
this modification I got almost all updates leaving only 50 (unit) rows
without update. Then I introduced another small modification by putting
a ->commit; ->disconnect; and reconnect to the db after the first part
of thread. This way only 26 rows were leaved out. Note that in all of
three versions, if I run again only the update part filtering by
"traffic is null" I get all rows updated. This strange behavior get me
to think that PG and/or DBI is returning control from commits even if
the transaction is not *really* committed, or that there is a issue with
the sequence that feeds the "id" serial field (not keeping up?). Note
that the single threads are accessing a table part well identified by
"device" field, and that I am using Perl ithreads, thus there should be
no real-threads issues, nor data interaction between threads.
Anyone have any idea what's going on?
------------------------------
Date: Thu, 7 Apr 2011 09:50:44 -0700 (PDT)
From: David Karr <davidmichaelkarr@gmail.com>
Subject: cond_wait problem with Thread::Pool
Message-Id: <e9382a63-8277-4adb-9c38-e3bed2ceea20@glegroupsg2000goo.googlegroups.com>
I had a nested loop where each iteration doesn't depend on any other iterat=
ion, so I concluded I could use Thread::Pool to queue up the iterations to =
make the loop go faster. Each iteration makes an HTTP connection to a serv=
er, so it likely would be faster using a thread pool.
So, I moved the body of the iteration to a new sub, and added a sub paramet=
er for the two loop indices (which the iteration body needs). The body nee=
ds to reference other data defined earlier in the script, which I left as i=
s in the new sub.
I ended up replacing the body with the following approximate line:
$pool->enqueue(\&mynewsub, $rindex, $dindex);
The first thing I noticed were warnings like the following:
pragma "attrs" is deprecated, use "sub NAME : ATTRS" instead at /usr/lib/pe=
rl5/site_perl/5.10/Thread/Pool.pm line 98.
Fortunately, this was an easy fix. Pool.pm was using the deprecated "use a=
ttrs". so I changed it to the newer format. I also filed a bug report on T=
hread::Pool for this.
The next problem I don't have a fix for yet. When it hit the loop and star=
ted enqueuing tasks, I saw the following on the console:
Thread 343 terminated abnormally: cond_wait can only be used on shared valu=
es at /usr/lib/perl5/site_perl/5.10/Thread/Pool.pm line 100.
This is in the following method:
sub _next_job : locked : method {
my $pool =3D shift;
cond_wait($pool) while $pool->{num} <=3D $pool->{min} && !@{$pool->{job=
s}};
my $job =3D $pool->{jobs}->[0];
shift @{$pool->{jobs}} if defined $job;
return $job;
}
I don't know if this represents a bug in Thread::Pool or some problem with =
my script. If it matters, these are my first statements in the script:
use threads;
use threads::shared;
use Thread::Pool;
The other thing I'm wondering about with Thread::Pool is concerning what ha=
ppens at the end of my script? Do I have to do some sort of "join()" to en=
sure all the jobs are completed? I didn't see any way to do this in the Th=
read::Pool documentation.
------------------------------
Date: Thu, 7 Apr 2011 14:37:40 -0700 (PDT)
From: David Karr <davidmichaelkarr@gmail.com>
Subject: Re: cond_wait problem with Thread::Pool
Message-Id: <3cc2e057-1156-4f66-97d9-6d5b362c4623@glegroupsg2000goo.googlegroups.com>
Note that I tried examining the sub that is being queued and traced back to=
all of the non-local variables that sub references and added "share($var)"=
calls after their declarations, even the declaration of my "$pool" variabl=
e (which might be a different entity than the "$pool" referenced in Pool.pm=
), but it made no difference. I still get the "cond_wait" error.
------------------------------
Date: Thu, 07 Apr 2011 17:49:07 GMT
From: Graham Drabble <usenet05@drabble.me.uk>
Subject: Re: FAQ 9.20 How do I send mail?
Message-Id: <Xns9EC0B542F9646grahamdrabblelineone@ID-77355.user.dfncis.de>
On 05 Apr 2011 PerlFAQ Server <brian@theperlreview.com> wrote in
news:DhMmp.31372$tL6.12978@newsfe03.iad:
> 9.20: How do I send mail?
>
> Use the "sendmail" program directly:
<snip>
> Or you might be able use the CPAN module "Mail::Mailer":
<snip>
Is there a reason that this prefers the use of sendmail over the various
CPAN modules that allow use of SMTP directly? As someone who writes a lot
fo Perl for Windows, scritps / modules that use calls to sendmail are a
real pain, those using SMTP directly are much more portable.
--
Graham Drabble
http://www.drabble.me.uk/
------------------------------
Date: Thu, 7 Apr 2011 20:06:12 +0200
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: FAQ 9.20 How do I send mail?
Message-Id: <slrniprv8k.etc.hjp-usenet2@hrunkner.hjp.at>
On 2011-04-07 17:49, Graham Drabble <usenet05@drabble.me.uk> wrote:
> On 05 Apr 2011 PerlFAQ Server <brian@theperlreview.com> wrote in
> news:DhMmp.31372$tL6.12978@newsfe03.iad:
>> 9.20: How do I send mail?
>>
>> Use the "sendmail" program directly:
>
><snip>
>
>> Or you might be able use the CPAN module "Mail::Mailer":
><snip>
>
>
> Is there a reason that this prefers the use of sendmail over the various
> CPAN modules that allow use of SMTP directly? As someone who writes a lot
> fo Perl for Windows, scritps / modules that use calls to sendmail are a
> real pain, those using SMTP directly are much more portable.
Actually you want to use SUBMISSION (RFC 4409), not SMTP (RFC 5321). But
apart from that I agree that talking a well-defined network protocol is
more portable than and generally preferrable to invoking a program.
(Invoking /usr/sbin/sendmail is a lot simpler, though)
hp
------------------------------
Date: Fri, 08 Apr 2011 01:36:47 -0500
From: brian d foy <brian.d.foy@gmail.com>
Subject: Re: FAQ 9.20 How do I send mail?
Message-Id: <080420110136476524%brian.d.foy@gmail.com>
[[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]
In article
<Xns9EC0B542F9646grahamdrabblelineone@ID-77355.user.dfncis.de>, Graham
Drabble <usenet05@drabble.me.uk> wrote:
> On 05 Apr 2011 PerlFAQ Server <brian@theperlreview.com> wrote in
> news:DhMmp.31372$tL6.12978@newsfe03.iad:
>
>
> > 9.20: How do I send mail?
> >
> > Use the "sendmail" program directly:
>
> <snip>
>
> > Or you might be able use the CPAN module "Mail::Mailer":
> <snip>
>
>
> Is there a reason that this prefers the use of sendmail over the various
> CPAN modules that allow use of SMTP directly?
Because no one has rewritten the answer with modern modules. You could
be the one to do that. :)
------------------------------
Date: Thu, 7 Apr 2011 09:05:25 -0700 (PDT)
From: David Karr <davidmichaelkarr@gmail.com>
Subject: Re: How to queue each loop iteration into a thread pool, with a max size?
Message-Id: <7e9cc2fe-70c5-4745-8bd1-2f3a10d28bb5@glegroupsg2000goo.googlegroups.com>
Thread::Pool looks like exactly what I need, thanks.
------------------------------
Date: Fri, 08 Apr 2011 02:14:51 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <x7ydnSzDVMB2KAPQnZ2dnUVZ5sudnZ2d@giganews.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
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_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.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Thu, 7 Apr 2011 20:14:19 +0200
From: "Peter J. Holzer" <hjp-usenet2@hjp.at>
Subject: Re: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <slrniprvnr.etc.hjp-usenet2@hrunkner.hjp.at>
On 2011-04-07 00:02, sln@netherlands.com <sln@netherlands.com> wrote:
> On Tue, 05 Apr 2011 02:14:53 -0500, tadmc@seesig.invalid wrote:
>>Do not post binaries, HTML, or MIME
>
> I'm just wondering if this means all the html posted on this ng
What do you mean by "all the html"? I remember only one poster here who
used html and I haven't read him for a long time.
Right now there isn't a single HTML message in this group on my system:
% grep -h -i '^Content-Type:' * | sort | uniq -c
1 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
5 Content-Type: text/plain
1 Content-Type: text/plain;
112 Content-Type: text/plain; charset=ISO-8859-1
6 Content-Type: text/plain; charset=ISO-8859-15; format=flowed
56 Content-Type: text/plain; charset=ISO-8859-1; format=flowed
2 Content-Type: text/plain; charset=KOI8-R; format=flowed
5 Content-Type: text/plain; charset=US-ASCII
26 Content-Type: text/plain; charset=UTF-8
25 Content-Type: text/plain; charset=UTF-8; format=flowed
14 Content-Type: text/plain; charset=iso-8859-1
2 Content-Type: text/plain; charset=koi8-r
123 Content-Type: text/plain; charset=us-ascii
4 Content-Type: text/plain; charset=utf-8
2 Content-Type: text/plain; charset=windows-1252
Plus another 190 messages which don't even have a Content-Type header.
OTOH the prescription against MIME is clearly not heeded:
384 of 574 messages (67%) are MIME messages.
> is a violation of the law?
There is no law. People may consider you rude and will probably flame
and killfile you if you post HTML but the police won't come for you.
hp
------------------------------
Date: Thu, 7 Apr 2011 12:16:15 -0700
From: Keith Keller <kkeller-usenet@wombat.san-francisco.ca.us>
Subject: Re: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <v4f178xo8q.ln2@goaway.wombat.san-francisco.ca.us>
On 2011-04-07, Peter J. Holzer <hjp-usenet2@hjp.at> wrote:
>
> There is no law. People may consider you rude and will probably flame
> and killfile you if you post HTML but the police won't come for you.
Score:: -8500 % stupid content-types
Content-Type: text/html
Content-Type: multipart/alternative
Content-Type: multipart/mixed
--keith
--
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information
------------------------------
Date: Fri, 8 Apr 2011 00:41:53 -0700 (PDT)
From: Rob <rdw204@gmail.com>
Subject: Removing data between two HTML tags?
Message-Id: <969eb4b1-46d4-4ce4-b960-b1abd2563812@f30g2000yqa.googlegroups.com>
Hello,
I am trying to use perl to remove all data which comes between these
two tags:
<div class="left">......</div>
This is the code I have so far but it is not doing the job:
$description=~ s|(.*? <div \s+ class="left"> .*? <div \s+
class="left"> .*?)<div \s+ class="left"> .*? </div>(.*? <div \s+
class="left">)|$1$2|sxg;
Any help would be appreciated.
Many thanks
Rob
------------------------------
Date: Fri, 08 Apr 2011 02:12:23 -0700
From: James Wright <monkey_vegas@cox.net>
Subject: Re: Removing data between two HTML tags?
Message-Id: <inmjhq$b3q$1@dont-email.me>
On 04/08/11 00:41, Rob wrote:
> Hello,
>
> I am trying to use perl to remove all data which comes between these
> two tags:
>
> <div class="left">......</div>
>
>
> This is the code I have so far but it is not doing the job:
>
> $description=~ s|(.*?<div \s+ class="left"> .*?<div \s+
> class="left"> .*?)<div \s+ class="left"> .*?</div>(.*?<div \s+
> class="left">)|$1$2|sxg;
>
> Any help would be appreciated.
>
> Many thanks
>
> Rob
Use an HTML parser.
------------------------------
Date: Fri, 8 Apr 2011 02:12:48 -0700 (PDT)
From: Marc Girod <marc.girod@gmail.com>
Subject: Re: Removing data between two HTML tags?
Message-Id: <81704e98-1377-4dd1-9ad9-f4868fbfb585@p16g2000yqb.googlegroups.com>
On Apr 8, 8:41=A0am, Rob <rdw...@gmail.com> wrote:
> Any help would be appreciated.
<http://groups.google.com/group/comp.lang.perl.misc/browse_frm/thread/
2d4cc24fcb76efc5/23fc643b6a5af104?lnk=3Dgst&q=3DRemoving+data+between+two
+HTML+tags#23fc643b6a5af104>
i.e. http://tinyurl.com/64uvzgp
There was a thread on this withing the last couple of months, but
Google didn't find it using 'Removing data between two HTML tags'.
Marc
------------------------------
Date: Fri, 8 Apr 2011 02:16:55 -0700 (PDT)
From: Marc Girod <marc.girod@gmail.com>
Subject: Re: Removing data between two HTML tags?
Message-Id: <3a934720-f4a2-44fd-8d23-1c27ecadb512@n10g2000yqf.googlegroups.com>
On Apr 8, 10:12=A0am, Marc Girod <marc.gi...@gmail.com> wrote:
Argh. Not exactly as intended. Correction:
http://groups.google.com/group/comp.lang.perl.misc/search?group=3Dcomp.lang=
.perl.misc&q=3DRemoving+data+between+two+HTML+tags&qt_g=3DSearch+this+group
http://tinyurl.com/6kbdrh4
> There was a thread on this withing the last couple of months
within
Sorry for that.
Marc
------------------------------
Date: Fri, 8 Apr 2011 00:36:53 -0700 (PDT)
From: Rob <rdw204@gmail.com>
Subject: Re: Search script to index dynamic pages
Message-Id: <1adcd976-02b8-48f4-9ac9-d3c7e1a32e43@d28g2000yqc.googlegroups.com>
On Apr 2, 3:59=A0am, J rgen Exner <jurge...@hotmail.com> wrote:
> Great! This means your Perl problem is solved.
Thank you all for your advice and help with this. It turned out that
the real problem was the firewall on the server, I can't do any http
communication using scripts within the site. I have overcome this by
running the indexer on my own machine and uploading the idexed
database each time, which now works fine.
Rob
------------------------------
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:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#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 3346
***************************************
