[25443] in Perl-Users-Digest
Perl-Users Digest, Issue: 7688 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Jan 25 06:05:38 2005
Date: Tue, 25 Jan 2005 03:05:10 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 25 Jan 2005 Volume: 10 Number: 7688
Today's topics:
Re: "Can't modify non-lvalue subroutine call" furrows m bik.mido@gmail.com
(C++) Class Member Function (Vittal)
ASP Perlscript/VBScript Order of execution <janschiffman@hotmail.com>
Avoid long timeout on DNS lookup of nonexistent host? <invalid@earthlink.net.invalid>
Re: Avoid long timeout on DNS lookup of nonexistent hos <noreply@gunnar.cc>
Re: Avoid long timeout on DNS lookup of nonexistent hos <invalid@earthlink.net.invalid>
Re: Avoid long timeout on DNS lookup of nonexistent hos <vetler@gmail.com>
Re: Avoid long timeout on DNS lookup of nonexistent hos <invalid@earthlink.net.invalid>
Re: File::Find gives me current dir (.)? <tadmc@augustmail.com>
Re: File::Find gives me current dir (.)? <tadmc@augustmail.com>
Re: Perl on Windows <tadmc@augustmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Printing After A While Loop <blabla@hotmail.com>
Re: Printing After A While Loop <tadmc@augustmail.com>
Re: Printing After A While Loop (Jay Tilton)
Re: Printing After A While Loop <tadmc@augustmail.com>
Re: Regex problem <zen13097@zen.co.uk>
Re: switching to extended character set using curses & someone92@hotmail.com
Re: switching to extended character set using curses & someone92@hotmail.com
Re: trying to "use Sys::Syslog" but I get nothing ... <terrylr@blauedonau.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 25 Jan 2005 02:26:06 -0800
From: bik.mido@gmail.com
Subject: Re: "Can't modify non-lvalue subroutine call" furrows my brow
Message-Id: <1106648766.568447.9280@f14g2000cwb.googlegroups.com>
Anno Siegel wrote:
> rickcasey <rick@rickcasey.net> wrote in comp.lang.perl.misc:
>
> > You are right; something else was going on.
>
> Please give an attribution and quote some context when replying.
This
> way nobody knows what you are talking about.
The problem is with Google: once one could hit "reply" and get a decent
quoting as with a "regular" news client. Now they're changing to the
new inferface (which has some interesting features/advantages but
overall is IMHO less clear and functional) and it doesn't work any
more.
To reply properly one has to (i) switch to Google Groups Beta, (ii) do
(_not_ hit "reply" directly) but select "show options" and then select
"reply" there.
PS: it may be worth to spread the word around people posting from
google who _seem_ to ignore this...
HTH,
Michele (back for a while!)
------------------------------
Date: 24 Jan 2005 22:56:25 -0800
From: vsnadagouda@yahoo.com (Vittal)
Subject: (C++) Class Member Function
Message-Id: <f9dcc290.0501242256.2bbf8249@posting.google.com>
Hello All,
I am looking for a small Perl script, which can help in finding all
the member functions given the class definition.
Is any such Perl script available, by any chance???
Thanks
-Vittal
------------------------------
Date: 24 Jan 2005 22:11:16 -0800
From: "LinnAxis" <janschiffman@hotmail.com>
Subject: ASP Perlscript/VBScript Order of execution
Message-Id: <1106633476.250200.106810@c13g2000cwb.googlegroups.com>
Anyone have any idea why in the excerpt from one of my ASP pages, the
Perlscript code always executes BEFORE the VBScript code?
Even if the VBScript is in an included file
(<!--#include file="../Include/Rep01Code.asp" -->), the Perlscript gets
executed first.
Unfortuantely my Perlscript needs to read Session variables assigned by
my VBScript code.
VBScript is the default lang as well.
Regards,
Jan
<%
Session("FundID")= SetSessionFundID(myFundID)
Session("ReportDate") = SetSessionReportDate(myReportDate)
Response.Write("VBSCRIPT IS EXECUTED NOW")
Response.Write("VBScript ReportDate: " & Session("ReportDate"))
Response.Write("VBScript FundID" & Session("FundID"))
%>
<SCRIPT RUNAT=SERVER LANGUAGE=PERLSCRIPT>
use lib qq(d:\\Site);
use SAMFundV02::SAMFundLib;
my $Fund = $Session->{"FundID"};
my $ReportDate = $Session->{"ReportDate"};
$Response->Write("PERLSCRIPT IS EXECUTED NOW");
$Response->Write("Perlscript FundID:". $Session->{"FundID"}. " ");
$Response->Write("Perlscript ReportDate:" . $Session->{"ReportDate"}
. " ");
SetRoundingFundAndDate($Fund,$ReportDate);
$Session->{"CurrentNAVBefore"} = FormatNumber(Round('NAV',
GetCurrentNAV($Fund, $ReportDate ,'BEFORE')));
$Session->{"CurrentNAVAfter"} = FormatNumber(Round('NAV',
GetCurrentNAV($Fund, $ReportDate ,'AFTER')));
$Session->{"PrevWeekNAVBefore"} = FormatNumber(Round('NAV',
GetPrevWeekNAV($Fund, $ReportDate ,'BEFORE')));
$Session->{"PrevWeekNAVAfter"} = FormatNumber(Round('NAV',
GetPrevWeekNAV($Fund, $ReportDate ,'AFTER')));
$Session->{"PrevMonthNAVBefore"} = FormatNumber(Round('NAV',
GetPrevMonthEndNAV($Fund, $ReportDate ,'BEFORE')));
$Session->{"PrevMonthNAVAfter"} = FormatNumber(Round('NAV',
GetPrevMonthEndNAV($Fund, $ReportDate ,'AFTER')));
</SCRIPT>
------------------------------
Date: Tue, 25 Jan 2005 09:31:47 GMT
From: Someone Else <invalid@earthlink.net.invalid>
Subject: Avoid long timeout on DNS lookup of nonexistent host?
Message-Id: <7moJd.6449$cZ1.3645@newsread2.news.atl.earthlink.net>
I'm sure this question has been addressed here before. I think I
even recall reading it, and answers, but for the life of me I
cannot come up with the correct Google incantation to resurrect
the thread(s).
The issue has to do with how to avoid the long (~18 sec)
time-out on a DNS lookup of a nonexistent host (at least it's
long with Active Perl running under Windows).
I'm trying to collect some statistics on the spam at a couple of
accounts. (At the moment this is not about spam filtering. I
just want to get some statistics.) It was easy enough to write a
Perl script to look up an IP address at [insert favorite list]:
========<begin script>=========
use Socket;
$h = gethostbyname shift;
if (!$h) {
$a = "<not listed>";
} else {
$a = inet_ntoa($h);
}
print "$a\n";
========<end script>=========
E.g.:
perl -w xxx.pl aaa.bbb.ccc.ddd.dnsbl.sorbs.net
returns the SROBS opinion of ddd.ccc.bbb.aaa. Make that a
subroutine, and call it from a main that parses your mailbox,
and you're all set.
The problem is that, while it rips through positive responses,
it hangs for about 18 sec on each negative response. I'm looking
through about 50,000 IP addresses, with about 20% not listed, so
that becomes a problem.
I know that it is possible to detect a negative response much
faster. E.g., CyberKit's NSLookUp returns a negative response
almost instantly.
FWIW, I'm using Windows ME and Active Perl v5.8.0.
Any ideas?
-- David
To make invalid valid, reverse the letters
------------------------------
Date: Tue, 25 Jan 2005 11:01:46 +0100
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: Avoid long timeout on DNS lookup of nonexistent host?
Message-Id: <35mk4kF4l6hepU1@individual.net>
Someone Else wrote:
> The problem is that, while it rips through positive responses, it hangs
> for about 18 sec on each negative response. I'm looking through about
> 50,000 IP addresses, with about 20% not listed, so that becomes a problem.
>
> I know that it is possible to detect a negative response much faster.
I don't know how you do that, but it sounds as if it would be possible
to speed up the execution time by forking multiple processes. You may
want to check out the CPAN module Parallel::ForkManager for a convenient
way to do so.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Tue, 25 Jan 2005 10:14:10 GMT
From: Someone Else <invalid@earthlink.net.invalid>
Subject: Re: Avoid long timeout on DNS lookup of nonexistent host?
Message-Id: <SZoJd.9441$rp1.362@newsread3.news.atl.earthlink.net>
Gunnar Hjalmarsson wrote:
> Someone Else wrote:
>
>> The problem is that, while it rips through positive responses, it
>> hangs for about 18 sec on each negative response. I'm looking through
>> about 50,000 IP addresses, with about 20% not listed, so that becomes
>> a problem.
>>
>> I know that it is possible to detect a negative response much faster.
>
>
> I don't know how you do that, but it sounds as if it would be possible
> to speed up the execution time by forking multiple processes. You may
> want to check out the CPAN module Parallel::ForkManager for a convenient
> way to do so.
>
Thanks. Yes, I thought of that, but was then thinking to the
future. That may be the solution to the near-term problem.
Thanks again.
-- David
To make invalid valid, reverse the letters
------------------------------
Date: Tue, 25 Jan 2005 11:18:39 +0100
From: "Vetle Roeim" <vetler@gmail.com>
Subject: Re: Avoid long timeout on DNS lookup of nonexistent host?
Message-Id: <opsk5lldegx7nu7z@quickfix.opera.com>
On Tue, 25 Jan 2005 09:31:47 GMT, Someone Else
<invalid@earthlink.net.invalid> wrote:
[...]
> I know that it is possible to detect a negative response much faster.
> E.g., CyberKit's NSLookUp returns a negative response almost instantly.
>
> FWIW, I'm using Windows ME and Active Perl v5.8.0.
>
> Any ideas?
Use the Net::DNS module instead. It allows you to do multiple concurrent
lookups and to set timeout values.
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
------------------------------
Date: Tue, 25 Jan 2005 10:28:33 GMT
From: Someone Else <invalid@earthlink.net.invalid>
Subject: Re: Avoid long timeout on DNS lookup of nonexistent host?
Message-Id: <lbpJd.6485$cZ1.3147@newsread2.news.atl.earthlink.net>
Vetle Roeim wrote:
> On Tue, 25 Jan 2005 09:31:47 GMT, Someone Else
> <invalid@earthlink.net.invalid> wrote:
>
> [...]
>
>> I know that it is possible to detect a negative response much faster.
>> E.g., CyberKit's NSLookUp returns a negative response almost instantly.
>>
>> FWIW, I'm using Windows ME and Active Perl v5.8.0.
>>
>> Any ideas?
>
>
> Use the Net::DNS module instead. It allows you to do multiple
> concurrent lookups and to set timeout values.
Thanks. I'll have to dig that up (it's not part of the
ActivePerl I have, but it's probably time for an upgrade anyway).
-- David
To make invalid valid, reverse the letters
------------------------------
Date: Mon, 24 Jan 2005 20:12:08 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: File::Find gives me current dir (.)?
Message-Id: <slrncvbano.2g4.tadmc@magna.augustmail.com>
ben.rogers@gmail.com <ben.rogers@gmail.com> wrote:
> #!C:\\Perl -w
> use File::Find;
You need a
use strict;
there.
And
use warnings;
is better than -w.
> if ($File::Find::name =~ /(.fm)$/i && -f){
Since it is anchored to the end anyway, you don't need the
other parts of the path, you can just use $_.
You shouldn't capture when you're not going to use the captured chars.
That will match a file named "foofm" you know...
Fixing all of that, we end up with:
if ( /\.fm$/i and -f ) {
> chdir "C:/Adobe/mifaliscious/b4";
You should check the return value to see if you got what you asked for:
chdir "C:/Adobe/mifaliscious/b4" or
die "could not cd to 'C:/Adobe/mifaliscious/b4' $!";
> foreach (@files) {print STDOUT "FOUND: $_\n";}
You can eliminate some punctuation:
print STDOUT "FOUND: $_\n" foreach @files;
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Mon, 24 Jan 2005 20:14:23 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: File::Find gives me current dir (.)?
Message-Id: <slrncvbarv.2g4.tadmc@magna.augustmail.com>
ben.rogers@gmail.com <ben.rogers@gmail.com> wrote:
> I made a mistake in my original post and Tad managed to get through the
> garbage to figure it out. Yes, I am writing a program-writing program.
> The code example was originally in a HERE block
A here document is not a "block", it is a "string".
If you single-quote the here-doc token, then you wouldn't have
to do all that backslashing of dollar signs and whatnot.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Mon, 24 Jan 2005 20:18:03 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Perl on Windows
Message-Id: <slrncvbb2r.2g4.tadmc@magna.augustmail.com>
[ Newsgroups trimmed ]
Matt Garrish <matthew.garrish@sympatico.ca> wrote:
>
> "JRBTech" <jrbtech-at@gmail.com> wrote in message
> news:W-WdnUkXep_KyG_cRVn-pQ@adelphia.com...
>>
>> Active Perl isnt free.
>>
>
> Really? Care to elaborate?
It is held hostage in a doped-silicon environment!
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 25 Jan 2005 08:22:08 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <41f601b0$0$8279$8b463f8a@news.nationwide.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://mail.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Mon, 24 Jan 2005 21:45:11 -0500
From: Bla <blabla@hotmail.com>
Subject: Re: Printing After A While Loop
Message-Id: <tkcbv01jdh0iqscslp44e4kk8u4i0nfbpq@4ax.com>
On Mon, 24 Jan 2005 17:35:34 -0700, Eric Schwartz <emschwar@pobox.com>
wrote:
>Bla <blabla@hotmail.com> writes:
>> Trying to print to a file after a while loop.....
>>
>>
>> while {
>> test
>> }
>>
>> do this
>>
>> can I put an else in here if the above is not true????
>
>I quoted you fully only because I cannot for the life of me figure out
>what, in fact, you are trying to do. A while loop doesn't look like
>that, it looks like this:
>
>while (some_test()) {
> do_something();
>}
>
>Can you please try this question again, with actual Perl?
>
>-=Eric
#!/usr/bin/perl -w
#
open (SNMPLOG, ">snmp.log") or die "could not open 'snmp.log' $!";
$ARGV[0] = 'url.log';
my %status;
while (<>) {
/ (FAILURE|SUCCESS).+?from (.+)/ and $status{$2} = $1;
}
$status{$_} eq 'FAILURE' and print SNMPLOG " 0 " for sort keys
%status;
#else {
# print SNMPLOG " 1 " for sort keys %status;
#}
------------------------------
Date: Mon, 24 Jan 2005 22:29:53 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Printing After A While Loop
Message-Id: <slrncvbiq1.2oh.tadmc@magna.augustmail.com>
Bla <blabla@hotmail.com> wrote:
> On Mon, 24 Jan 2005 17:35:34 -0700, Eric Schwartz <emschwar@pobox.com>
> wrote:
>
>>Bla <blabla@hotmail.com> writes:
>>> Trying to print to a file after a while loop.....
>>>
>>>
>>> while {
>>> test
>>> }
>>>
>>> do this
>>>
>>> can I put an else in here if the above is not true????
>>
>>I quoted you fully only because I cannot for the life of me figure out
>>what, in fact, you are trying to do. A while loop doesn't look like
>>that, it looks like this:
>>
>>while (some_test()) {
>> do_something();
>>}
>>
>>Can you please try this question again, with actual Perl?
>>
>>-=Eric
>
> #!/usr/bin/perl -w
> #
> open (SNMPLOG, ">snmp.log") or die "could not open 'snmp.log' $!";
> $ARGV[0] = 'url.log';
> my %status;
> while (<>) {
> / (FAILURE|SUCCESS).+?from (.+)/ and $status{$2} = $1;
> }
> $status{$_} eq 'FAILURE' and print SNMPLOG " 0 " for sort keys
> %status;
>
> #else {
> # print SNMPLOG " 1 " for sort keys %status;
> #}
print SNMPLOG $status{$_} eq 'FAILURE' ? ' 0 ' : ' 1 ' for sort keys %status;
but I don't like that much for maintenance, I wouldn't use it in my code.
I'd "unroll" it, as that seems to make it much easier to see what's going on:
for (sort keys %status) {
if ( $status{$_} eq 'FAILURE' )
{ print SNMPLOG ' 0 ' }
else
{ print SNMPLOG ' 1 ' }
}
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Tue, 25 Jan 2005 06:53:51 GMT
From: tiltonj@erols.com (Jay Tilton)
Subject: Re: Printing After A While Loop
Message-Id: <41f5e4a7.27286345@news.erols.com>
Bla <blabla@hotmail.com> wrote:
: #!/usr/bin/perl -w
: #
: open (SNMPLOG, ">snmp.log") or die "could not open 'snmp.log' $!";
: $ARGV[0] = 'url.log';
: my %status;
: while (<>) {
: / (FAILURE|SUCCESS).+?from (.+)/ and $status{$2} = $1;
: }
: $status{$_} eq 'FAILURE' and print SNMPLOG " 0 " for sort keys
: %status;
:
: #else {
: # print SNMPLOG " 1 " for sort keys %status;
: #}
This makes more sense than the original article. Other than setting up the
data structure, the while loop has nothing to do with the problem.
Since there are only two possible values of $status{$_}, each of which maps
directly to one output string, I'd rather ditch the if/else thing.
print SNMPLOG
{ FAILURE => ' 0 ', SUCCESS => ' 1 ' } -> { $status{$_} }
for sort keys %status;
------------------------------
Date: Mon, 24 Jan 2005 20:16:13 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Printing After A While Loop
Message-Id: <slrncvbavd.2g4.tadmc@magna.augustmail.com>
Bla <blabla@hotmail.com> wrote:
> while {
> test
> }
This is the Perl newsgroup. We discuss Perl here.
Did you have some _Perl_ code that you wanted to ask about?
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 25 Jan 2005 09:08:23 GMT
From: Dave Weaver <zen13097@zen.co.uk>
Subject: Re: Regex problem
Message-Id: <41f60c87$0$7767$db0fefd9@news.zen.co.uk>
Vito Corleone <vito_corleone@godfather.com> wrote:
> How can I change every:
> <photo src=111:123:456> to
> <img src=img/111/123/456>?
>
> I tried:
> $html =~ s#<photo src=($d+):($d+):($d+)>#<img src=img/$1/$2/$3>#g;
^ ^ ^
If you are trying to match digits, this is not how you do it.
This may be better:
$html =~ s#<photo src=(\d+):(\d+):(\d+)>#<img src=img/$1/$2/$3>#g;
^ ^ ^
------------------------------
Date: 24 Jan 2005 22:25:33 -0800
From: someone92@hotmail.com
Subject: Re: switching to extended character set using curses & perl
Message-Id: <1106634333.934032.162460@c13g2000cwb.googlegroups.com>
I found the solution to my problem just in case someone would need the
information some day:
Curses::attrset(&Curses::A_ALTCHARSET); #switch to ACS
$win->addstr($y,$x,$ACSchar);
------------------------------
Date: 24 Jan 2005 22:25:34 -0800
From: someone92@hotmail.com
Subject: Re: switching to extended character set using curses & perl
Message-Id: <1106634334.793962.74460@f14g2000cwb.googlegroups.com>
I found the solution to my problem just in case someone would need the
information some day:
Curses::attrset(&Curses::A_ALTCHARSET); #switch to ACS
$win->addstr($y,$x,$ACSchar);
------------------------------
Date: Tue, 25 Jan 2005 00:37:18 -0600
From: "terry l. ridder" <terrylr@blauedonau.com>
Subject: Re: trying to "use Sys::Syslog" but I get nothing ...
Message-Id: <Pine.LNX.4.61.0501250033140.28019@johann.blauedonau.com>
On Mon, 24 Jan 2005, Karen Wieprecht wrote:
> I'm trying to get some data sent into the system log after processing it
> with a perl program. the text processing works great, and if I send to
> stdout, the messages come out as they are processed. However, I'm trying
> to send the messages to the system log with "use Sys::Syslog" and I am not
> getting anything ...
>
> 1. I'm using perl 5.6
> 2. syslog.conf is configured to show *.notice
which log file are *.notice msgs logged?
> 3. I have seen examples with different flavors of quotes ( " .vs. ') in
> the setlogsock, openlog, and syslog commands. I tried both ways with no
> effect.
>
> Code snippit (not the full program):
>
> use Sys::Syslog qw(:DEFAULT setlogsock);
> setlogsock ("unix");
> openlog ("audit", "ndelay,nowait", "local5");
>
> while ( <> ) {
> chomp;
> $PRINT_STRING = $_;
> syslog ("notice", " %s\n",$PRINT_STRING) ;
> }
> closelog ();
>
works for me. msgs are logged to /var/log/messages.
Jan 25 00:29:11 johann audit: this is a test
>
>
> I never get a syntax error, but I don't get any of the messages into the
> system log either . I can't get the syslog command to DO anything. the
> syntax looks right compared to many samples of the code I've seen ... maybe
> I'm missing something?
>
best guess would be:
0. the msgs are being logged but not where you think/want them logged.
1. there is a problem with /etc/syslog.conf.
>
>
> Any ideas? Help would be most appreciated.
>
> Thanks,
>
> Karen Wieprecht
>
>
--
terry l. ridder ><>
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 7688
***************************************
