[23082] in Perl-Users-Digest
Perl-Users Digest, Issue: 5303 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Aug 1 06:05:48 2003
Date: Fri, 1 Aug 2003 03:05:08 -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, 1 Aug 2003 Volume: 10 Number: 5303
Today's topics:
Re: <input type='image'> ... IE fails to pass value w <krahnj@acm.org>
Re: Command or script to get a list of email addresses <carsten.nospam@furtherspam.welcomes-you.com>
how to construct a variable, variable name ? (Alex Johnson)
Re: how to know the week of today? <ggkuo@yahoo.com>
Re: how to know the week of today? <abigail@abigail.nl>
Re: mod_perl: my $var=1 if ... (Jay Tilton)
Re: mod_perl: my $var=1 if ... <kjetilskotheim@yahoo.com>
Re: mod_perl: my $var=1 if ... <kkeller-spammmm@wombat.san-francisco.ca.us>
Re: pattern matching <kjetilskotheim@yahoo.com>
PERL: ISO-Latin and UTF8 (Philip M. Gollucci)
Re: PERL: ISO-Latin and UTF8 <abigail@abigail.nl>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
question from perl noob <boblehue@online.no>
Re: question from perl noob <g4rry_sh0rt@zw4llet.com>
Re: question from perl noob <boblehue@online.no>
Re: question from perl noob <jvandervloet@hotmail.com>
Re: question from perl noob <boblehue@online.no>
Re: Substitution Question <krahnj@acm.org>
Re: using post method (hash)
Re: using post method <bernard.el-hagin@DODGE_THISlido-tech.net>
Re: Web development and Perl 6 <tassilo.parseval@rwth-aachen.de>
Re: Web development and Perl 6 <abigail@abigail.nl>
Re: Web development and Perl 6 <bigiain@mightymedia.com.au>
Re: Wide character in print <NOSPAM@bigpond.com>
Re: <bwalton@rochester.rr.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 01 Aug 2003 06:26:33 GMT
From: "John W. Krahn" <krahnj@acm.org>
Subject: Re: <input type='image'> ... IE fails to pass value while Mozilla and Netsacpe works
Message-Id: <3F2A085A.75B610D7@acm.org>
Tad McClellan wrote:
>
> "... looking for another place to put the garbage. We didn't
> find one. Until we came to a side road, and off the side of
> the side road there was another fifteen foot cliff and at
> the bottom of the cliff there was another pile of garbage.
> And we decided that one big pile is better than two little
> piles, and rather than bring that one up we decided to
> throw our's down." [2]
>
> [2] "Alice's Restaurant", Arlo Guthrie
I don't want a pickle
Just want to ride on my motorsickle
And I don't want a tickle
'Cause I'd rather ride on my motorsickle
And I don't want to die
I just want to ride on my motorcy...cle
-- "The Motorcycle Song", Arlo Guthrie
John
--
use Perl;
program
fulfillment
------------------------------
Date: Fri, 01 Aug 2003 07:48:17 +0200
From: Carsten Aulbert <carsten.nospam@furtherspam.welcomes-you.com>
Subject: Re: Command or script to get a list of email addresses
Message-Id: <bgcuv4$nhkoq$1@uni-berlin.de>
Deboo wrote:
> I tried using grep but then there are some duplicates too and finding
> and removing them would be a big hassle.
If you are just worried about duplicates, try
Your_Grep|sort|uniq
or
Your_Grep|sort -u (not 100% sure this will work all the time)
Of course, you can do similar things in perl...
Carsten
------------------------------
Date: 1 Aug 2003 02:34:51 -0700
From: alex2100k@yahoo.com (Alex Johnson)
Subject: how to construct a variable, variable name ?
Message-Id: <5c6fa981.0308010134.37021b96@posting.google.com>
hi, i'm trying to call a variable where the variables name is
constructed using text and the value of another variable, the kind of
code that i'm trying to write would be something like this:
#!/usr/bin/perl -w
my $var1 = "three";
my $total = 1;
$var2 = '$var' . $total;
print "$var2";
but rather than printing literally '$var1' i want it to print the
contents of the variable $var1, so it should print 'three', i couldn't
find the answer in the perl books, probably because don't know the
keyword to look for, or else just one of those things that's so simple
it's assumed you know already, so any advice would be gratefully
received.
thanks in advance,
Alex.
------------------------------
Date: Fri, 01 Aug 2003 05:49:51 GMT
From: "C&J" <ggkuo@yahoo.com>
Subject: Re: how to know the week of today?
Message-Id: <3cnWa.11732$k06.5245@newssvr22.news.prodigy.com>
Hi, all
Thanks all of your help.
"C&J" <ggkuo@yahoo.com> wrote in message
news:OWlVa.662$Qb7.504188001@newssvr12.news.prodigy.com...
> Hi,
> Is there any way to know what is the current week?
> January 1 is the first week.
> Thanks
> Chris
>
>
------------------------------
Date: 01 Aug 2003 08:59:07 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: how to know the week of today?
Message-Id: <slrnbikauq.rj8.abigail@alexandra.abigail.nl>
cp (cpryce@pryce.nospam.net) wrote on MMMDCXXI September MCMXCIII in
<URL:news:310720031317510686%cpryce@pryce.nospam.net>:
{} In article <etor846a9fv.fsf@wormtongue.emschwar>, Eric Schwartz
{} <emschwar@ldl.fc.hp.com> wrote:
{}
{} > $weeknum = int((localtime)[7] / 7);
{}
{} Isn't that inaccurate?
{} int( 365 / 7 ) = 52
{}
{} The 365th day of the year ( and on leap years, the 366th also) are in
{} the 53rd week..
{}
{} The OP might want to check CPAN for any number of Date manipulation
{} modules. 'The Perl Cookbook'[1] suggests Date::Calc.
{}
{} [bash:~]user% perl -e 'use Date::Calc qw(Week_Number);\
{} print Week_Number('2003', 12, 31), "\n";'
{}
{} outputs: 53
The methods aren't equivalent, even when you change 'int' to 'ceil'.
Take for instance Jan 6, 2003.
ceil (6 / 7) == 1.
but
Week_Number (2003, 1, 6) == 2.
The latter corresponds with the ISO standard on weeks: weeks start on
Mondays, and week 1 is the week with the first Thursday of the year in
it. This could mean some days of January are in week 52 or 53, and
some days of December could be in week 1.
The former method isn't any standard I know off - it would mean that
weeks start on different days in different years.
Americans, as usual, don't follow international standards. Week 1 in
the US is the week January 1 falls in. Which may, or may not be the
same as the POSIX standard, depending on the year.
Abigail
--
perl -e '* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
/ / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / / /
% % % % % % % % % % % % % % % % % % % % % % % % % % % % % % % %;
BEGIN {% % = ($ _ = " " => print "Just Another Perl Hacker\n")}'
------------------------------
Date: Fri, 01 Aug 2003 04:14:27 GMT
From: tiltonj@erols.com (Jay Tilton)
Subject: Re: mod_perl: my $var=1 if ...
Message-Id: <3f29e70b.85808163@news.erols.com>
Kjetil Skotheim <kjetilskotheim@yahoo.com> wrote:
: I'm having trouble understanding something in mod_perl. The sub handler is:
:
: sub handler
: {
: ...stuff deleted...
: my $var=1 if ...condition_A...;
: $var=2 if ...condition_B...; if($var){
: ...someting....
: }
: }
:
: The IF-block are entered sometimes when both condition_A and B
: are false! How can that be?
From the "Private Variables via my()" section of perlsub:
NOTE: The behaviour of a my statement modified with a
statement modifier conditional or loop construct (e.g. my $x
if ...) is undefined. The value of the my variable may be
undef, any previously assigned value, or possibly anything
else. Don't rely on it. Future versions of perl might do
something different from the version of perl you try it out
on. Here be dragons.
: I suspect that $var is preserved from the previous apache-request
: on the same process.
You nailed it.
------------------------------
Date: Fri, 01 Aug 2003 06:34:03 +0200
From: Kjetil Skotheim <kjetilskotheim@yahoo.com>
Subject: Re: mod_perl: my $var=1 if ...
Message-Id: <oprs7lm1w785yxzq@nntp.uio.no>
On Fri, 01 Aug 2003 04:14:27 GMT, Jay Tilton <tiltonj@erols.com> wrote:
> Kjetil Skotheim <kjetilskotheim@yahoo.com> wrote:
>
> : I'm having trouble understanding something in mod_perl.
> : The sub handler is:
> :
> : sub handler
> : {
> : ...stuff deleted...
> : my $var=1 if ...condition_A...;
> : $var=2 if ...condition_B...; if($var){
> : ...someting....
> : }
> : }
> : The IF-block are entered sometimes when both condition_A and B
> : are false! How can that be?
>
> From the "Private Variables via my()" section of perlsub:
>
> NOTE: The behaviour of a my statement modified with a statement modifier
> conditional or loop construct (e.g. my $x if ...) is undefined. The value
> of the my variable may be undef, any previously assigned value, or
> possibly anything else. Don't rely on it. Future versions of perl might
> do something different from the version of perl you try it out on. Here
> be dragons.
(ok, should have RTFM)
>
> : I suspect that $var is preserved from the previous apache-request
> : on the same process.
>
> You nailed it.
But it works in "normal perl" outside mod_perl, and its the
same perl-version as compiled into apache. Oh well...I'l just
have to exterminate all those my-if's everywhere.
--
Kjetil Skotheim
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
------------------------------
Date: Thu, 31 Jul 2003 21:48:35 -0700
From: Keith Keller <kkeller-spammmm@wombat.san-francisco.ca.us>
Subject: Re: mod_perl: my $var=1 if ...
Message-Id: <3frcgb.hle.ln@goaway.wombat.san-francisco.ca.us>
-----BEGIN xxx SIGNED MESSAGE-----
Hash: SHA1
In article <oprs7if8d985yxzq@nntp.uio.no>, Kjetil Skotheim wrote:
> I'm having trouble understanding something in mod_perl. The sub handler is:
>
> sub handler
> {
>
> ...stuff deleted...
>
> my $var=1 if ...condition_A...;
> $var=2 if ...condition_B...; if($var){
> ...someting....
> }
>
> }
>
> The IF-block are entered sometimes when both condition_A and B
> are false! How can that be? If I do the following instead then
> everyting works ok:
>
> my $var; #lexical declaration without if
> $var=1 if ...condition_A...;
> $var=2 if ...condition_B...;
>
> I suspect that $var is preserved from the previous apache-request
> on the same process. Can anyone confirm this?
I'm not sure that's what's going on. It would help to know what
condition_A and condition_B were--there are probably variables
surviving in the httpd process that are influencing the conditions
in ways you aren't expecting, thus causing $var to be set. Since
we don't know what your conditions are, though, it's tough to tell.
It would certainly help to post a test case with real code instead
of condition_[AB], and perhaps to check your error_log. If you
find a real problem, I'd also recommend the mod_perl mailing list
(findable from perl.apache.org).
> Should "my $var=... if ..." be totally avoided in mod_perl?
I personally don't think it's such a great style, but I don't
know if it's something definitely to be avoided.
- --keith
- --
kkeller-mmmspam@wombat.san-francisco.ca.us
(try just my userid to email me)
alt.os.linux.slackware FAQ: http://wombat.san-francisco.ca.us/cgi-bin/fom
-----BEGIN xxx SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAj8p8RsACgkQhVcNCxZ5ID8WxACeJMM5HxMH+V1GkMeSO0Lql33v
hSAAn3WjaMjs1sgXDXRl+IEKIqCFd6zI
=5phS
-----END PGP SIGNATURE-----
------------------------------
Date: Fri, 01 Aug 2003 06:29:49 +0200
From: Kjetil Skotheim <kjetilskotheim@yahoo.com>
Subject: Re: pattern matching
Message-Id: <oprs7lfzdx85yxzq@nntp.uio.no>
Have you looked at the HTML::TableExtract module?
Or you might parse one-dimentional <table>'s just like this:
Or I sometimes use the following sub to extract html-<table>'s
and copy the non-html-content inside <td>-tags into
a list of lists. (Two-dim-perl-array).
my $html=<<"END";
<html>
...
The table:
<table>
<tr><td><b>Now:</b></td> <td>234</td> <td>11</td></tr>
<tr><td><b>Then:</b></td> <td><a href="asdf">ABC</a></td></tr>
<tr><td>After:</td><td>1</td><td>2</td><td>3<td>4<td>5</tr>
</table>
</html>
END
my @table = ht2t($html); #Or ht2t($html,'table:'); #string before right
<table>
for (@table){ print map "($_) ",@$_; print "\n" }
sub ht2t { # = html-table-to-table
my($f,$s)=@_;
$f=~s,.*?($s).*?(<table.*?)</table.*,$2,si;
my $e=0;$e++ while index($f,$s=chr($e))>=$[;
$f=~s/<t(d|r|h).*?>/$1$s/gsi;
$f=~s/\s*<.*?>\s*//gsi;
my @t=split("r$s",$f);shift @t;
for (@t){my @r=split(/[dh]$s/,$_);shift @r;$_=[@r]}
@t;
}
__END__
This prints, as expected:
(Now:) (234) (11) (Then:) (ABC)
(After:) (1) (2) (3) (4) (5)
On 31 Jul 2003 16:02:51 -0700, brian liu <xliu75@yahoo.com> wrote:
> i got pop0.htm file, I want to get value between <TD> and </TD>
> and put into one array.
> like a[0]=a1 a[1]=b a[2]=a2 a[3]=a3
>
> pop0.htm
>
> <HTML>
> <HEAD>
> </HEAD>
> <BODY bgColor=#ffffff>
> <TABLE border=1>
> <TR>
> <TD>a1</TD>
> <TD>b</TD> <TD>a2</TD>
> <TD>a3</TD>
> </TR>
> <TABLE>
> </BODY>
> </HTML>
>
>
> I use perl code pop0.pl below:
> $defaultDir='d:\haha';
> $inputFile='pop\d+\.htm';
>
> #Output files
> $tempOutput = $defaultDir.'\tempOutput.txt';
>
> #Clear files
> unlink $tempOutput;
>
> main($defaultDir);
>
>
> sub main()
> {
> #$err= opendir THISDIR,$_[0];
> if( ! opendir THISDIR,$_[0] ) {
> print "Faild to open $_[0]\n";
> die;
> }
>
>
> my @dataFiles = grep /$inputFile/ , readdir THISDIR; # Get all
> data.* files
> closedir THISDIR;
> openFiles();
>
> sort @dataFiles;
> foreach $file (@dataFiles){
> processFile($file);
> }
>
> closeFiles();
> print "Done.\n";
>
> }#main
>
>
> sub processFile()
> {
>
> local $path=$defaultDir;
> local $dataF = $_[0];
> print "Processing $_[0] ...\n";
>
> $count=1;
> open DF,$path.'/'.$dataF or print "Error opening file $dataF, at
> $path \n Error: $!\n";
> while(<DF>){
>
> if(/^$/){next;}
> if ($count<5){
> if(/<TD>(a\d+)<\/TD>/|/<TD>(b)<\/TD>/){
> @a[$count]=$1; if ($2!=null){
> } print "$count @a[$count] \t";
> $count++;
> }
> }
>
> }
> }
>
>
>
> # --- DB access methods --------
>
>
> sub openFiles()
> {
> open S,'>>'.$tempOutput or print "Error opening file $tempOutput \n
> Error: $!\n";
> }
>
> sub closeFiles()
> {
> close S;
> }
>
>
> and get print out is like a[0]=a1 a[1]=b a[2]=a3 done;
> it seems like after match first <TD></TD> then didn't match the rest
> of this line, just go to next line
>
> How can I match first pattern in one line and then match again using
> same pattern or other pattern in the same line , in perl?
>
> Thanks a lot
>
> Brian
>
--
Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
------------------------------
Date: 31 Jul 2003 22:21:12 -0700
From: pgollucci@ejpress.com (Philip M. Gollucci)
Subject: PERL: ISO-Latin and UTF8
Message-Id: <75e6245d.0307312121.68a2f7b3@posting.google.com>
If I retreived a stored value from a database (MSSQL/Oralce),
Is there any way in PERL to determine if it was encoded using UTF8 or ISO-LATIN.
If so, how ?
---------------------------------------------------------------------------------
eJournalPress
DBA / Software Engineer / System Administrator
E-Mail: pgollucci@ejournalpress.com
URL : http://www.ejournalpress.com
Phone : 301.530.6375
------------------------------
Date: 01 Aug 2003 09:04:13 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: PERL: ISO-Latin and UTF8
Message-Id: <slrnbikb8d.rj8.abigail@alexandra.abigail.nl>
Philip M. Gollucci (pgollucci@ejpress.com) wrote on MMMDCXXII September
MCMXCIII in <URL:news:75e6245d.0307312121.68a2f7b3@posting.google.com>:
-: If I retreived a stored value from a database (MSSQL/Oralce),
-: Is there any way in PERL to determine if it was encoded using UTF8 or ISO-LATIN.
-: If so, how ?
Other than heuristics? No. But that has to do with UTF-8 encoding
itself, and not much with Perl. Problem is that valid UTF-8 could also be
valid ISO-LATIN, and the other way around. Now, sometimes what is valid
ISO-LATIN can't be valid UTF-8, and some UTF-8 strings might contain
octets in the range 0x80 - 0x9F which some might consider to be invalid
ISO-LATIN. So, you might be lucky and have a string that's only valid
in one encoding. But in general, you can't determine it.
Not in Perl, not in any other language.
Abigail
--
$" = "/"; split // => eval join "+" => 1 .. 7;
*{"@_"} = sub {foreach (sort keys %_) {print "$_ $_{$_} "}};
%_ = (Just => another => Perl => Hacker); &{%_};
------------------------------
Date: Fri, 01 Aug 2003 02:23:08 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <bpadnauIfrnBiLeiXTWJkw@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: Fri, 1 Aug 2003 10:06:09 +0200
From: "boblehue" <boblehue@online.no>
Subject: question from perl noob
Message-Id: <NdpWa.17188$Hb.287897@news4.e.nsc.no>
Hi
I'm tryng to learn a little perl and have a problems with decimal's.
This asignment is to rewrite this code to not print more the two decimals
with the use of INT operator, multiplication, and division.
print "Monthly deposit amount? ";
$pmt=<STDIN>;
chomp $pmt;
print "Annual Interest rate? (ex. 7% is .07) ";
$interest=<STDIN>;
chomp $interest;
print "Number of months to deposit? ";
$mons=<STDIN>;
chomp $mons;
# Formula requires a monthly interest
$interest/=12;
$total=$pmt * ( ( (1 + $interest) ** $mons ) -1 )/ $interest;
print "After $mons months, at $interest monthly you\n";
print "Will have $total,\n";
Regards
Boblehue
------------------------------
Date: Fri, 01 Aug 2003 09:24:25 +0000
From: Garry Short <g4rry_sh0rt@zw4llet.com>
Subject: Re: question from perl noob
Message-Id: <bgd89m$3lv$1$8302bc10@news.demon.co.uk>
boblehue wrote:
<SNIP>
> $total=$pmt * ( ( (1 + $interest) ** $mons ) -1 )/ $interest;
>
<SNIP>
>
> Regards
> Boblehue
Not 100% sure, but I'm almost certain that's in the FAQ!
However, modifying your code *very* slightly ...
$total= sprintf "%2f", ($pmt * ( ( (1 + $interest) ** $mons ) -1 )/
$interest);
HTH,
Garry
------------------------------
Date: Fri, 1 Aug 2003 10:57:29 +0200
From: "boblehue" <boblehue@online.no>
Subject: Re: question from perl noob
Message-Id: <YZpWa.17199$Hb.287974@news4.e.nsc.no>
Hi and tnx Garry!
I tryed your code but it did not give me the result i wanted.
With your code : 29498.282425,
With origninal code : 29498.2824251624
Result i'm looking for : 29498.28
I get closer with your code but not quite!
And i'm suposed to use the INT operator, multiplication, and division.
Regards
Boblehue
"Garry Short" <g4rry_sh0rt@zw4llet.com> wrote in message
news:bgd89m$3lv$1$8302bc10@news.demon.co.uk...
> boblehue wrote:
>
> <SNIP>
> > $total=$pmt * ( ( (1 + $interest) ** $mons ) -1 )/ $interest;
> >
> <SNIP>
> >
> > Regards
> > Boblehue
>
> Not 100% sure, but I'm almost certain that's in the FAQ!
>
> However, modifying your code *very* slightly ...
>
> $total= sprintf "%2f", ($pmt * ( ( (1 + $interest) ** $mons ) -1 )/
> $interest);
>
> HTH,
>
> Garry
>
>
------------------------------
Date: Fri, 01 Aug 2003 09:46:06 GMT
From: "joeri" <jvandervloet@hotmail.com>
Subject: Re: question from perl noob
Message-Id: <yFqWa.44047$F92.4818@afrodite.telenet-ops.be>
"boblehue" <boblehue@online.no> wrote in message
news:YZpWa.17199$Hb.287974@news4.e.nsc.no...
> Hi and tnx Garry!
>
> I tryed your code but it did not give me the result i wanted.
>
> With your code : 29498.282425,
>
> With origninal code : 29498.2824251624
>
> Result i'm looking for : 29498.28
>
> I get closer with your code but not quite!
>
> And i'm suposed to use the INT operator, multiplication, and division.
>
> Regards
>
> Boblehue
>
>
>
>
>
> "Garry Short" <g4rry_sh0rt@zw4llet.com> wrote in message
> news:bgd89m$3lv$1$8302bc10@news.demon.co.uk...
> > boblehue wrote:
> >
> > <SNIP>
> > > $total=$pmt * ( ( (1 + $interest) ** $mons ) -1 )/ $interest;
> > >
> > <SNIP>
> > >
> > > Regards
> > > Boblehue
> >
> > Not 100% sure, but I'm almost certain that's in the FAQ!
> >
> > However, modifying your code *very* slightly ...
> >
> > $total= sprintf "%2f", ($pmt * ( ( (1 + $interest) ** $mons ) -1 )/
> > $interest);
> >
> > HTH,
> >
> > Garry
> >
> >
>
>
You're right, it should be" %0.2f"
Greets,
J
------------------------------
Date: Fri, 1 Aug 2003 12:02:44 +0200
From: "boblehue" <boblehue@online.no>
Subject: Re: question from perl noob
Message-Id: <4XqWa.17213$Hb.288239@news4.e.nsc.no>
Or u can use the grey ones and do some math:
$total=$pmt * ( ( ( 1 + $interest) ** $mons ) -1 )/ $interest;
$total=$total * 100;
$total=int($total);
$total=$total/100;
print "After $mons months, at $interest monthly you\n";
print "Will have $total.\n";
I found the solution on my one :-)
One step closer to understand perl...
Regards
Kenneth
"boblehue" <boblehue@online.no> wrote in message
news:YZpWa.17199$Hb.287974@news4.e.nsc.no...
> Hi and tnx Garry!
>
> I tryed your code but it did not give me the result i wanted.
>
> With your code : 29498.282425,
>
> With origninal code : 29498.2824251624
>
> Result i'm looking for : 29498.28
>
> I get closer with your code but not quite!
>
> And i'm suposed to use the INT operator, multiplication, and division.
>
> Regards
>
> Boblehue
>
>
>
>
>
> "Garry Short" <g4rry_sh0rt@zw4llet.com> wrote in message
> news:bgd89m$3lv$1$8302bc10@news.demon.co.uk...
> > boblehue wrote:
> >
> > <SNIP>
> > > $total=$pmt * ( ( (1 + $interest) ** $mons ) -1 )/ $interest;
> > >
> > <SNIP>
> > >
> > > Regards
> > > Boblehue
> >
> > Not 100% sure, but I'm almost certain that's in the FAQ!
> >
> > However, modifying your code *very* slightly ...
> >
> > $total= sprintf "%2f", ($pmt * ( ( (1 + $interest) ** $mons ) -1 )/
> > $interest);
> >
> > HTH,
> >
> > Garry
> >
> >
>
>
------------------------------
Date: Fri, 01 Aug 2003 06:31:58 GMT
From: "John W. Krahn" <krahnj@acm.org>
Subject: Re: Substitution Question
Message-Id: <3F2A099F.F019330@acm.org>
Janek Schleicher wrote:
>
> Mike Flannigan wrote at Thu, 31 Jul 2003 21:15:39 +0000:
> >
> > I simply want to convert Adkins to Adki01
> >
> > This code is close, but has a space between
> > Adki and 01
> >
> > $temp =~ s/^(.{0,4})..$/$1 01/;
>
> If you want substitute characters defined in their absolute positions, the
> substr function might be your friend:
>
> substr($temp,4,2) = "01";
You can leave out the length argument if you want to substitute the rest
of the string at position 4.
substr( $temp, 4 ) = '01';
John
--
use Perl;
program
fulfillment
------------------------------
Date: 31 Jul 2003 23:57:43 -0700
From: hash_q@yahoo.com (hash)
Subject: Re: using post method
Message-Id: <634c3c13.0307312257.4d558bac@posting.google.com>
Eric Schwartz <emschwar@ldl.fc.hp.com> wrote in message news:<etod6fq8f64.fsf@wormtongue.emschwar>...
> "Dave Millen" <postmaster@[127.0.0.1]> writes:
> > The form handler will be checking the HTTP_REFERER value and rejecting
> > anything that doesn't come from the expected page.
>
> s/come from/claim to $&/
what does the above line mean?
>
> -=Eric
------------------------------
Date: Fri, 1 Aug 2003 07:49:10 +0000 (UTC)
From: "Bernard El-Hagin" <bernard.el-hagin@DODGE_THISlido-tech.net>
Subject: Re: using post method
Message-Id: <Xns93CA635F7EEEelhber1lidotechnet@62.89.127.66>
hash wrote:
> Eric Schwartz <emschwar@ldl.fc.hp.com> wrote in message
> news:<etod6fq8f64.fsf@wormtongue.emschwar>...
>> "Dave Millen" <postmaster@[127.0.0.1]> writes:
>> > The form handler will be checking the HTTP_REFERER value and
>> > rejecting anything that doesn't come from the expected page.
>>
>> s/come from/claim to $&/
>
> what does the above line mean?
It changes "come from" to "claim to come from".
--
Cheers,
Bernard
--
echo 42|perl -pe '$#="Just another Perl hacker,"'
------------------------------
Date: 1 Aug 2003 06:58:00 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: Web development and Perl 6
Message-Id: <bgd31o$qg3$1@nets3.rz.RWTH-Aachen.DE>
Also sprach Uri Guttman:
>>>>>> "GH" == Gunnar Hjalmarsson <noreply@gunnar.cc> writes:
>
> GH> The point I was trying to make is:
> GH> - Some people in this group seem to believe it is good for Perl if
> GH> "newbies" opt for PHP before Perl/CGI for web scripting.
> GH> - I expressed my doubts about that view.
>
> more like it doesn't matter to perl what they choose for web stuff since
> web stuff is a fraction of the entire perl world. just wait until the
> newbies do something real and try to use php for genomics or parsing.
>
> the point is not to fret over what people use for web apps. it is
> nothing compared to the large picture.
Yet, the web is a good entrance point for a programming language. When I
started with Perl it was because I wanted to do some CGI stuff. The
interesting thing is that I soon started to use Perl for all other
things _but_ CGI (not because Perl would be unsuitable for that but
because I got bored by CGI-thingies).
For me the question remains what my primary language would be right now
hadn't Perl had the reputation to be a web-language. Perhaps I'd be
programming PHP or Java now (and be less happy).
In essence, the assumption that a person starting his life as CGI
script-kiddie will remain one till the end of his days is wrong. He
might soon switch to more interesting domains and even become a
CPAN-author or perl5/6-porter or whatever. Or become a knowledgeable
regular in clpm. Go figure.
The point of the OP was - as far as I understand it - not to alter Perl
in order to attract the kiddies. It was to provide a homogeneous Perl
environment so that webhosts are encouraged to offer a solid mod_perl
system. Would that be hard? No, not so:
perl (standard distribution or perhaps stripped down)
mod_perl
DBI
DBD::mysql
libnet
libwww
some HTML/XML modules
CGI
EmbPerl (to make it 'appear' more PHPish)
Bundle that up, provide an installation script and some documentation.
And give it a flashy name so that people start to recognize it by that
(like PerlWDK or so).
Even from a selfish point of view, that wouldn't be so bad. I might some
day be in the situation where I have use for a good webhoster. I am sure
I'll get very sick if all I have is some mod_php crap.
So all that remains to be done is take those things that already exist
and bring them together in a fairly standardized way and seamless way.
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: 01 Aug 2003 08:30:29 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: Web development and Perl 6
Message-Id: <slrnbik995.rj8.abigail@alexandra.abigail.nl>
Gunnar Hjalmarsson (noreply@gunnar.cc) wrote on MMMDCXXII September
MCMXCIII in <URL:news:bgce21$nk32u$1@ID-184292.news.uni-berlin.de>:
==
== Personally I believe that any program needs a big user base,
I disagree. Quality matters, quantity doesn't. I don't think Windows
is a better OS because more people use it. I don't think trucks aren't
important and don't play an important role because there are more 'normal'
cars. I don't think major league baseball players play worse baseball
than little league players, just because the latter league as a bigger
player base.
== Sometimes I feel that
== regulars in this group deliberately and actively discourage Perl and
== CGI from being used for trivial web scripting, and _that_ amazes _me_.
== I smell snobbery.
That might also have to do with the quality and attitude of many of the
so-called "web programmers". They are to Perl as what AOL used to be to
Usenet.
== Isn't CGI scripts on the web _one_ important application field for
== Perl? You don't need to have a "web-centric view" to acknowledge that,
== do you?
It's important. It's not vital.
Abigail
--
perl -Mstrict -we '$_ = "goto O.print chop;\n=rekcaH lreP rehtona tsuJ";O1:eval'
------------------------------
Date: Fri, 01 Aug 2003 19:12:05 +1000
From: Iain Chalmers <bigiain@mightymedia.com.au>
Subject: Re: Web development and Perl 6
Message-Id: <bigiain-547818.19120501082003@nasal.pacific.net.au>
In article <bgd31o$qg3$1@nets3.rz.RWTH-Aachen.DE>,
"Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de> wrote:
> The point of the OP was - as far as I understand it - not to alter Perl
> in order to attract the kiddies. It was to provide a homogeneous Perl
> environment so that webhosts are encouraged to offer a solid mod_perl
> system. Would that be hard? No, not so:
>
> perl (standard distribution or perhaps stripped down)
> mod_perl
> DBI
> DBD::mysql
> libnet
> libwww
> some HTML/XML modules
> CGI
> EmbPerl (to make it 'appear' more PHPish)
>
> Bundle that up, provide an installation script and some documentation.
> And give it a flashy name so that people start to recognize it by that
> (like PerlWDK or so).
Seems to me that could almost all be done as a CPAN bundle...
big
--
"Two-strokes develop torque in Nm's, but not in reality. Real
torque is what you're supposed to get when you open the throttle.
___________ this is a torque curve, /\ this is not." Theo in aus.moto
------------------------------
Date: Fri, 1 Aug 2003 18:01:32 +1000
From: "Gregory Toomey" <NOSPAM@bigpond.com>
Subject: Re: Wide character in print
Message-Id: <bgd6oa$mt819$1@ID-202028.news.uni-berlin.de>
"Yuri Shtil" <shtil@comcast.net> wrote in message
news:a3eWa.21387$cF.8823@rwcrnsc53...
> Hi all
>
> I am getting this when I try to print certain strings. Is it harmless ?
>
> If not, how do I get rid of it ?
>
> Yuri.
Upgrade! Fixed on Eniac 2.
gtoomey
------------------------------
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 5303
***************************************
