[23409] in Perl-Users-Digest
Perl-Users Digest, Issue: 5627 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Oct 7 06:06:03 2003
Date: Tue, 7 Oct 2003 03:05:07 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 7 Oct 2003 Volume: 10 Number: 5627
Today's topics:
About regura expression only for outside of html tags. <chang@naggama.co.kr>
Re: pattern matching <nospam@peng.nl>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: regex behavior <abigail@abigail.nl>
Re: require and do - absolute vs relative - let me try <wunkalunka@elvis.com>
Re: require and do - absolute vs relative - let me try <wunkalunka@elvis.com>
Re: require and do - absolute vs relative - let me try (Anno Siegel)
Re: require and do - relative vs absolute? <wunkalunka@elvis.com>
Re: two regexs <mpapec@yahoo.com>
Re: two regexs <mpapec@yahoo.com>
Re: two regexs <mpapec@yahoo.com>
Re: two regexs <mpapec@yahoo.com>
Re: Very Interesting max_size in UserAgent <kuujinbo@hotmail.com>
Re: Virus, CPU killer, Memory Eater on Sourceforge.net? <dave.nospam@ntlworld.com>
Re: <bwalton@rochester.rr.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 7 Oct 2003 18:51:53 +0900
From: "G&G" <chang@naggama.co.kr>
Subject: About regura expression only for outside of html tags.
Message-Id: <blu2f5$qnv$1@news.hananet.net>
Have any idea about regular expression ?
I tried to change any numeric letter to Zero like following;
$aaa = ereg_replace ("|0-9|", "0", $sentence);
This seems working perfect.
My question is how I can do this function only for outside of html tags.
I don't want any numeric letters to be changed inside html tags.
Thanks for further response.
Regards,
Mo
------------------------------
Date: Tue, 7 Oct 2003 09:52:16 +0100
From: "Lex" <nospam@peng.nl>
Subject: Re: pattern matching
Message-Id: <levgb.42$CT2.2175@news-reader.eresmas.com>
"Bob Walton" <invalid-email@rochester.rr.com> wrote in message
news:3F823B3F.6070602@rochester.rr.com...
> > @xref{($word, $plural, $synonym, $text)} = ($id)x4;
>
> ----------------------------------------^^^^^
> Are you sure you want to put a whole phase in as a key in %xref? The
> keys to %xref are supposed to be words according to the conventions used
> so far.
Well no, I just wanted to be able to use the (specific) meaning later on...
> > $meaning{$id}=$meaning;
>
> ---------------------^^^^^^^^
> Did you use strict; and use warnings; ? They would have pointed out
> that this variable is undef at this point because you changed it from
> $meaning to $text two lines above and didn't change it here. If it were
> still stored in %meaning, then the text could be gotten back by ID just
> by saying $meaning{$id}.
changed it back to meaning again
> If you hadn't made the mistake of changing $meaning to $text in all but
> one of the places it is used, you could have used $meaning{$id} to get
> that text -- just replace the ... with $meaning{$id}. You'd better make
> sure the text doesn't contain any ' characters, and perhaps " characters
> either. Maybe < and > also? Others? Probably best to run it through a
> Javascript quoter, and then an HTML quoter?
>
Hi Bob. First: my original question and problem is solved, it works perfect
with this code:
open (DB, "<$db_file_name") or &cgierr("error in search. unable to open
database: $db_file_name.\nReason: $!");
if ($db_use_flock) { flock(DB, 1); }
my %xref;
my %meaning;
while ( <DB> ) {
chomp;
my($id, $word, $plural, $synonym,$cat,$meaning) = split /\|/;
@xref{($word, $plural, $synonym)} = ($id)x3;
$meaning{$id}=$meaning;
}
foreach my $id(keys %meaning){
foreach my $word ( $rec{'Text'} =~ /\S+/g ) {
my $newword = "<a
href=\"$db_script_link_url&ID=$xref{$word}&mh=1&ww=1&view_records=1\">$word<
/a>";
$rec{'Text'} =~ s|\b$word\b|$newword|gs if exists $xref{$word};
}
}
close DB;
What it does: when showing the field $rec{'Text'}from one of the records of
the database it checks if words, synonyms or plurals form all records in the
database are used in this field and if so create a link to those words.
Anyway, I don't need telling you people do I? :) But just to be clear about
what I'm doning.
Now I wanted something more again (always the same...), when showing records
from another database I wanted it to happen as well. Got that working (the
links), wasn't very hard. However, I now wanted a popup screen as well
already showing the meaning of the word (taken from the meaning field). Now,
here I run into troubles and I think it's because it's still working and
trying to do things with that meaning field as well. If it would produce
just the text it works. I thought it might be ' or " as you suggested so
made sure that I got rid of them. However, that didn't do the trick and the
problem was worse than just that.
So I think $meaning{$id} in this case (underneath) has more luggage than
that what I am looking for. In this case I do not want links in this field
now, I know I want a lot and am still not capable of producing it, quite
frustrating, but hey, this is my way of learning I guess. I'll copy the code
underneath that I tried but that was giving me more than I wanted:
open (DB, "<$db_file_name_abc") or &cgierr("error in search. unable to open
database: $db_file_name_abc.\nReason: $!");
if ($db_use_flock) { flock(DB, 1); }
my %xref;
my %meaning;
while ( <DB> ) {
chomp;
my($id, $word, $plural, $synonym, $cat, $meaning) = split /\|/;
@xref{($word, $plural, $synonym, $meaning)} = ($id)x4;
$meaning{$id}=$meaning;
}
foreach my $id(keys %meaning){
foreach my $word ( $rec{'Text'} =~ /\S+/g ) {
if ($xref{$word}) {
my $newword = "<a
href=\"$db_dir_url/db.cgi?db=abc&uid=$db_uid&ID=$xref{$word}&mh=1&ww=1&view_
records=1\" class=\"abclink\"
ONMOUSEOVER=\"popup('$meaning{$id}','#ffffcc')\";
ONMOUSEOUT=\"kill()\">$word</a>";
$rec{'Text'} =~ s|\b$word\b|$newword|gs;
}
}
}
close DB;
As soon as I insert $meaning{$id} it all goes wrong, all of it, even $word
isn't what it's supposed to be anymore. As well after cutting out all html
and ' and " etc. from $meaning{$id}.
To all the people (still) reading this: thanks for your patience with me! :)
Lex
------------------------------
Date: Tue, 07 Oct 2003 02:22:11 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <V3SdnfRSePo-9B-iU-KYiA@august.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.4 $)
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.
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
"Jeopardy" (because the answer comes before the question), or
"TOFU".
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: 07 Oct 2003 07:25:55 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: regex behavior
Message-Id: <slrnbo4qk3.13v.abigail@alexandra.abigail.nl>
Michael P. Broida (michael.p.broida@boeing_oops.com) wrote on
MMMDCLXXXVIII September MCMXCIII in <URL:news:3F81D592.208F5420@boeing_oops.com>:
'' Abigail wrote:
'' >
'' > Michael P. Broida (michael.p.broida@boeing_oops.com) wrote on
'' > MMMDCLXXXIII September MCMXCIII in <URL:news:3F7B532C.7878A3BB@boeing_oops.com>:
'' > ,, Abigail wrote:
'' > ,, >
'' > ,, > Matija Papec (mpapec@yahoo.com) wrote on MMMDCLXXXIII September MCMXCIII
'' > ,, > in <URL:news:4bdmnvcb9or2nbm2ne1euvhqp1e64s84g7@4ax.com>:
'' > ,, > --
'' > ,, > -- I went through perldoc but didn't found similar regex,
'' > ,, > -- print join ',', 'a bb ccc dddd' =~ /(\w)+/g;
'' > ,, > --
'' > ,, > -- the question is, what it exactly matches and why?
'' > ,, >
'' > ,, > /(\w)+/ matches a set of consecutive word characters, capturing
'' > ,, > the *last* one. //g in list context means, do this as often as
'' > ,, > possible (without overlap), returning a list of each of the submatches.
'' > ,, >
'' > ,, > So, 'a bb ccc dddd' =~ /(\w)+/g; returns for each substring of
'' > ,, > consecutive word characters the last one, resulting in 'a', 'b', 'c' and 'd'.
'' > ,,
'' > ,, That tests out as you said, so it's MY thinking that's off. :)
'' > ,, Hopefully, you can clue me in. :)
'' > ,,
'' > ,, I expected it to result in "a,bb,ccc,dddd". Now I realize that
'' > ,, it's the positioning of the + that causes it to get a single
'' > ,, character from each group. If the + is inside the (), it
'' > ,, prints what I expected.
'' > ,,
'' > ,, But... What is causing the original /(\w)+/ to get the LAST
'' > ,, character from each group instead of the FIRST character from
'' > ,, each group?
'' >
'' > Would you expect:
'' >
'' > $x = $_ for qw /a b c d/
'' > print $x;
'' >
'' > to print 'a' as well?
''
'' It doesn't print anything without a semi-colon on the first line.
'' <grin>
''
'' At first glance, I thought it would print each letter. Then I
'' looked deeper and realized it's basically assigning and re-assigning
'' $x (via $_) during the "for" loop, but only printing it when it's all
'' done. Thus it only prints "d".
''
'' But the prior discussion was about a regex, not a "for" loop.
'' If your point is that the regex processing works similarly to
'' the "for" loop in your example, then I see what you mean.
''
'' If that's NOT what your point was, then you've lost me. <grin>
My point is, if you repeatedly assign something to a variable, do you
expect the variable to retain the first value it was set to, or the
last value? Because that's happening in both the match, and the for loop.
Abigail
--
perl -swleprint -- -_=Just\ another\ Perl\ Hacker
------------------------------
Date: Tue, 07 Oct 2003 08:28:09 GMT
From: Derf <wunkalunka@elvis.com>
Subject: Re: require and do - absolute vs relative - let me try again
Message-Id: <Xns940D239D5BBE4wunkalunkaelviscom@24.28.95.150>
jwillmore@cyberia.com (James Willmore) wrote in
news:e0160815.0310061754.2929782c@posting.google.com:
> Huh? Try again using something like "/a/b/c/file.pl" instead of what
> you used to describe the issue. Maybe after doing that, you may find
> your error and not need to post ... because, it looks as though you're
> confussed about where the files are. I know I am :-)
>
> Seriously, you _should_ be able to execute another script from another
> location using an absolute path. You may want to check your
> permissions and, as always, try the script from the command line to
> see what happens.
>
> HTH
>
> Jim
I appreciate the help. I have the same problem from command line. It
turns out it is just this script. Other scripts run fine with the
absolute path. It is only this one script that says it can't be found if
I use an absolute path, but can be found if it is in the same directory
with a relative path (any other relative path fails as well "No such file
or directory"). The reqiuired script runs fine. The required script has a
couple do commands that use relative paths though. I wonder if those do
commands might need to be absolute so the require sees them. hmmmm
------------------------------
Date: Tue, 07 Oct 2003 08:33:52 GMT
From: Derf <wunkalunka@elvis.com>
Subject: Re: require and do - absolute vs relative - let me try again
Message-Id: <Xns940D2495BA2CAwunkalunkaelviscom@24.28.95.150>
Derf <wunkalunka@elvis.com> wrote in
news:Xns940D239D5BBE4wunkalunkaelviscom@24.28.95.150:
>
The reqiuired script runs fine. The
> required script has a couple do commands that use relative paths
> though. I wonder if those do commands might need to be absolute so the
> require sees them. hmmmm
>
Yeah, that was it.
------------------------------
Date: 7 Oct 2003 09:16:19 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: require and do - absolute vs relative - let me try again
Message-Id: <blu093$hhk$1@mamenchi.zrz.TU-Berlin.DE>
Derf <wunkalunka@elvis.com> wrote in comp.lang.perl.misc:
> jwillmore@cyberia.com (James Willmore) wrote in
> news:e0160815.0310061754.2929782c@posting.google.com:
> > Huh? Try again using something like "/a/b/c/file.pl" instead of what
> > you used to describe the issue. Maybe after doing that, you may find
> > your error and not need to post ... because, it looks as though you're
> > confussed about where the files are. I know I am :-)
> >
> > Seriously, you _should_ be able to execute another script from another
> > location using an absolute path. You may want to check your
> > permissions and, as always, try the script from the command line to
> > see what happens.
> >
> > HTH
> >
> > Jim
>
> I appreciate the help. I have the same problem from command line. It
> turns out it is just this script. Other scripts run fine with the
> absolute path. It is only this one script that says it can't be found if
> I use an absolute path, but can be found if it is in the same directory
> with a relative path...
Does the mystery script do a "chroot" by any means? Not that that has
anything to do with Perl...
Anno
------------------------------
Date: Tue, 07 Oct 2003 08:21:03 GMT
From: Derf <wunkalunka@elvis.com>
Subject: Re: require and do - relative vs absolute?
Message-Id: <Xns940D226825720wunkalunkaelviscom@24.28.95.158>
Bob Walton <invalid-email@rochester.rr.com> wrote in news:3F820680.403
@rochester.rr.com:
> CGI debugging is a FAQ, and, as the FAQ mentions, is also off-topic here
> (your question and its answer would be the same if your script was
> written in C, Befunge, etc). Please see:
>
> perldoc -q 500
>
it is a Perl question to me, and I only mentioned the Web factor so folks
didn't start asking me if I was stating my path from my web root or actual
root. The CGI part is really irrelevant to the problem, it happens from
command line as well. Unfortunately, this is just confusing to describe.
Derf
------------------------------
Date: Tue, 07 Oct 2003 09:07:15 +0200
From: Matija Papec <mpapec@yahoo.com>
Subject: Re: two regexs
Message-Id: <v7p4ov4qlf24q1kuvj24foqidk88hlp0g5@4ax.com>
On Mon, 6 Oct 2003 16:24:24 -0500, tadmc@augustmail.com (Tad
McClellan) wrote:
>>>What is a "predefined form" ?
>>
>> I have forms stored in html files and need to populate them with user or db
>> input.
>
>
>That is client-side then?
No, did you have a look a the code? It is on the server side.
------------------------------
Date: Tue, 07 Oct 2003 09:14:06 +0200
From: Matija Papec <mpapec@yahoo.com>
Subject: Re: two regexs
Message-Id: <6hp4ov4ur0jftgjc4953o5rqda0ce7n5m4@4ax.com>
On Mon, 06 Oct 2003 22:21:56 GMT, Michael Budash <mbudash@sonic.net>
wrote:
>> How do I automate an HTML form submission?
>>
>> (despite the fact that the question has nothing to do with HTML...)
>>
>>
>> Or are you talking about something else?
>>
>> (maybe I still don't know what a "predefined form" is?)
>
>i think the o.p. is simply talking about html templates. HTML::Template
>or Template Toolkit sound appropriate here...
Seems like an overkill if it's not used in other aspects beside form
populating[1].
[1] like in
http://search.cpan.org/~jsm/HTML-Defaultify-1.01/Defaultify.pm
------------------------------
Date: Tue, 07 Oct 2003 09:20:33 +0200
From: Matija Papec <mpapec@yahoo.com>
Subject: Re: two regexs
Message-Id: <mvp4ov40j8918o2ajt36d66r5akreistq8@4ax.com>
On Mon, 6 Oct 2003 13:09:17 -0700, Steven Kuo <skuo@mtwhitney.nsc.com>
wrote:
>It's fine. Other alternatives are likely to be ugly. For example,
>
>my @str = (
> '="foo bar" ..',
> '=foobar ..',
>);
>
>for (@str) {
> if (/=(")?((??{ $1 ? q{.+?(?=")} : q{\\S+} }))/) {
Tnx.. I did look at this for some time! :)
------------------------------
Date: Tue, 07 Oct 2003 09:30:00 +0200
From: Matija Papec <mpapec@yahoo.com>
Subject: Re: two regexs
Message-Id: <maq4ovoc9ap0b2rr3nhd8l11cr80eqq3mb@4ax.com>
On 6 Oct 2003 17:57:14 -0700, kuujinbo@hotmail.com (ko) wrote:
>I'm not sure how you're defining bloated - maybe not loading modules
>if its not necessary? If you don't mind looking into HTML::TreeBuilder
>(you also need HTML-Parser and HTML-Tagset, maybe that's what you mean
>by bloated), the code itself isn't that bad:
Yes, maybe bloated is wrong word, overkill probably better describes
the situation. :)
>__DATA__
><form>
><input maxlength=50 name="IME" size=50 type="text" value="Default">
><input name="Q1" type="CHECKBOX" value="A1">A1
><input name="Q1" type="CHECKBOX" value="A2">A2
><input name="Q1" type="CHECKBOX" value="A3">A3
></form>
>
>====END
>
>The attr() method allows you to read/manipulate any tag's attribute.
>And it will also work for a group of checkboxes with the same name :)
Tnx, that is what I needed; I'll try some benchmarks and decide.
------------------------------
Date: Tue, 07 Oct 2003 16:35:34 +0900
From: ko <kuujinbo@hotmail.com>
Subject: Re: Very Interesting max_size in UserAgent
Message-Id: <bltqft$ot4$1@pin3.tky.plala.or.jp>
Public Interest wrote:
> #!/usr/bin/perl
> use Net::HTTP;
> use LWP::UserAgent;
>
> $ua = LWP::UserAgent->new ( );
> $ua->max_size(2000);
> $url = 'http://www.yahoo.com';
>
> my $req = HTTP::Request->new(GET => "$url");
>
> $htmlcode = $ua->request($req)->content;
> print $htmlcode;
>
> # the problem is if i change 2000 to 1950 in max_size, the $htmlcode is
> still the same. Looks to me that the server is flushing and client is using
> buffer to hold it and the server decide how much each flushing is giving,
> and if each flushing is 1024 bytes, and max_size is checked after each
> flushing. So, max size of 1025 to max size of 2047 will give the same
> result: both are 2048. Is that right? So max_size in UserAgent is really an
> estimated value.
No, it is a specific limit. From the LWP::UserAgent docs:
$ua->max_size([$bytes])
Get/set the size limit for response content. The default is undef, which
means that there is no limit. If the returned response content is only
partial, because the size limit was exceeded, then a ``Client-Aborted''
header will be added to the response.
So if you want to check if max_size has been exceeded, you have to test
for if there is a Client-Aborted header:
#!/usr/intel/bin/perl -w
use strict;
use LWP::UserAgent;
my $ua = LWP::UserAgent->new( max_size => 0);
my $url = 'http://www.yahoo.com';
print "Exceeded max_size\n" if $ua->get($url)->header('Client-Aborted');
HTH - keith
------------------------------
Date: Tue, 07 Oct 2003 10:04:02 +0100 (BST)
From: "Dave Saville" <dave.nospam@ntlworld.com>
Subject: Re: Virus, CPU killer, Memory Eater on Sourceforge.net?
Message-Id: <qnirfnivyyragyjbeyqpbz.hme4eq7.pminews@text.news.ntlworld.com>
On Mon, 06 Oct 2003 23:54:32 GMT, Public Interest wrote:
>I am not sure it is my problem or a general problem. Last week, there was a
>hack on changing your DNS record on your PC via IE. The hackers use banners
>on forturncity, a free web hosting company to do that. It seems to me
Do you have any pointers to this? I have a friend who I think has been
hit.
Thanks.
Regards
Dave Saville
NB switch saville for nospam in address
------------------------------
Date: Sat, 19 Jul 2003 01:59:56 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re:
Message-Id: <3F18A600.3040306@rochester.rr.com>
Ron wrote:
> Tried this code get a server 500 error.
>
> Anyone know what's wrong with it?
>
> if $DayName eq "Select a Day" or $RouteName eq "Select A Route") {
(---^
> dienice("Please use the back button on your browser to fill out the Day
> & Route fields.");
> }
...
> Ron
...
--
Bob Walton
------------------------------
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.
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 5627
***************************************
