[22895] in Perl-Users-Digest
Perl-Users Digest, Issue: 5115 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jun 13 06:05:43 2003
Date: Fri, 13 Jun 2003 03:05:06 -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, 13 Jun 2003 Volume: 10 Number: 5115
Today's topics:
ASN1.pm example required (Torsten Drees)
Re: db file problem <ixanthi@ixanthi.remove.gr>
Re: Enqueue a hash? <nobull@mail.com>
Re: How to make write()/format behave more like Text::W <gerardlanois@netscape.net>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: print operand file name <simon.oliver@nospam.umist.ac.uk>
regex help (david)
Re: regex help (Philip Lees)
Re: Regexp Multiple Matching Problem <occitan@esperanto.org>
rookie question <dhou@removerohan.sdsu.edu>
Re: rookie question (Damian James)
Re: rookie question (Philip Lees)
script to do global search & replace <ofuuzo@ub.uit.no>
Re: script to do global search & replace <w.koenig@acm.org>
Re: Search through Array and evaluate the two <mgjv@tradingpost.com.au>
test <arc_of_descent@gmx.net>
Re: test <bernard.el-hagin@DODGE_THISlido-tech.net>
Webmin security problems and use of CGI.pm <jasonp@panix.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 13 Jun 2003 07:19:49 GMT
From: torsten.drees@t-online.de (Torsten Drees)
Subject: ASN1.pm example required
Message-Id: <3ee97ad7.776704@news.t-online.de>
Hi there,
i have some problems to use the Module ASN1.pm.
(http://search.cpan.org/author/GBARR/Convert-ASN1-0.17/lib/Convert/ASN1.pod)
The documentation is not enough to me, to understand the working of
these module(s). Perhaps anybody can send me a short example how to
convert a simple asn.1 encoded text to a script.
It would help very much
thanks in advance
torsten
------------------------------
Date: Fri, 13 Jun 2003 09:47:44 +0300
From: "Vassilis Tavoultsidis" <ixanthi@ixanthi.remove.gr>
Subject: Re: db file problem
Message-Id: <bcbs2l$1gt$1@nic.grnet.gr>
You have a point and I made a mistate stating the problem. I use file
locking with the following code
local *DBM;
my $db = tie %dbase, "DB_File", "${temp_data}/".$params{"database"}.".db",
O_CREAT | O_RDWR, 0755 or die "could not tie to db file: $!";
my $fd = $db->fd;
open DBM, "+<&=$fd" or die "Could not dub DBM for lock : $!";
flock DBM, LOCK_EX;
undef $db;
I had corruption problems with the dbmopen and dbmclose because the script i
am writing is serving a portal where news are added at the same time from
multiple users and viewers see them at the same time. I use the BerkeleyDB
but have no idea what the DB_INIT_CDB mode is. Any reference?
Thanks
"Dan Wilga" <dwilga-MUNGE@mtholyoke.edu> wrote in message
news:dwilga-MUNGE-B42A1B.16414111062003@nap.mtholyoke.edu...
> In article <bc7jeq$icq$1@nic.grnet.gr>,
> "Vassilis Tavoultsidis" <ixanthi@ixanthi.remove.gr> wrote:
>
> > I am working with the simple db files perl gives and I open and close
the
> > with the dbmopen and dbmclose files. Sometimes (i don't know the
conditions)
> > it seems that the file contains 2(!!) identical records in it. The
records
> > have the same key and the same content. If I erase one the other is gone
> > too. If i modify one the other is modified too. I have tried to figure
out
> > what may cause this but nothing.
>
> Are you doing updates to the DB in multiple instances of the same
> program at the same time, for instance in a CGI program or something
> that uses fork()?
>
> If so, that's probably your problem. The dbmXXX calls don't support any
> sort of locking. For more robust flatfile database access, use something
> like the DB_INIT_CDB mode of the BerkeleyDB module (available on CPAN).
>
> --
> Dan Wilga dwilga-MUNGE@mtholyoke.edu
> ** Remove the -MUNGE in my address to reply **
------------------------------
Date: 12 Jun 2003 13:27:52 +0100
From: Brian McCauley <nobull@mail.com>
Subject: Re: Enqueue a hash?
Message-Id: <u9he6vwkdz.fsf@wcl-l.bham.ac.uk>
Brian McCauley <nobull@mail.com> writes:
> $MyQueue->enqueue(@Targets{ sort { whatever } key %Targets});
^^^
keys!
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
Date: Fri, 13 Jun 2003 05:52:09 GMT
From: Gerard Lanois <gerardlanois@netscape.net>
Subject: Re: How to make write()/format behave more like Text::Wrap?
Message-Id: <uu1au4jek.fsf@netscape.net>
Big and Blue <No_4@dsl.pipex.com> writes:
> This works (it's got \n rather than \cM\cJ, but if you really want
> to enforce that I'm sure you can adapt it...
>
> #! /usr/bin/perl -w
> use strict;
>
> # I have some text that looks like this.
> my $text = "Xxx xxxxxxxxx xxxx xxxx xxxxxx xxxxxxx xxx xx x ".
> "xxxxxx. Xxx xxxx xx xxxxxx xxxxxxxxx xxxx xxxx xxxx x xxxxx. ".
> "Xxx xxxxxxx xxxx xxxx xxxx xxxxx xxx XXXXXXXXX_XXX_XXXX xxxxxxxxxx ".
> "xxxxxxx, xxx xxx xxxxxxxxx xxxx XXXXXXX xx.\nXxx xxxx ".
> "xxxx\nXxxxxxxx XX 1234567890, Xxxxxx XXXXX12345678";
>
>
> my $f_text;
> format =
> ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<~~
> $f_text
> .
>
> foreach $f_text (split(/\n/, $text)) {
> write;
> }
I was wondering if it was possible to do this without the split().
That's the main question I had.
-Gerard
------------------------------
Date: Fri, 13 Jun 2003 02:22:40 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <Yc-dnQI7JJhd5nSjXTWcpA@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, 13 Jun 2003 08:26:11 +0100
From: Simon Oliver <simon.oliver@nospam.umist.ac.uk>
Subject: Re: print operand file name
Message-Id: <3EE97C93.6070101@nospam.umist.ac.uk>
mhearse wrote:
> I've recently developed a script to validate simple macro commands. This
> script may be run on as many as 200 files at once (macro_valid.pl *).
> Currently it prints only the errors detected (no way to tell which errors go
> with which filename). I need a way to print the filename when an error is
> detected. Possibly some way to read the filename into input, and print it
> if an error is detected. Any suggestions?
>
>
>
From perlvar:
$ARGV
contains the name of the current file when reading from <>.
--
Simon Oliver
------------------------------
Date: 12 Jun 2003 21:27:35 -0700
From: dwlepage@yahoo.com (david)
Subject: regex help
Message-Id: <b09a22ae.0306122027.5e0d825c@posting.google.com>
Ive spent several days trying to figure this one.
what's the best way to match on the value after 'UserId='
file:
dn: UserId=AC1234-5,User
objectclass: User
Comment: administrator
Comment2: AC1234-5.USER.1
desired output:
dn: UserId=AC1234-5,User
objectclass: User
Comment: administrator
Comment2: @AC1234-5
Im having a hard time matching on UserId values that contain a -. If
the UserId=(\w+) this works fine. Here is a variation of what ive
tried:
if (/\.USER\.1/) {
s/\b(\w+)\.USER\.1/\@$1/g;
}
print OUT $_;
prints:
dn: UserId=AC1234-5.USER.1,User
objectclass: User
Comment: administrator
Comment2: AC1234-@5
I've been up and down regex chapters and I cant seem to find the
answer.
any help appreciated.
thx
d
------------------------------
Date: Fri, 13 Jun 2003 06:32:25 GMT
From: pjlees@ics.forthcomingevents.gr (Philip Lees)
Subject: Re: regex help
Message-Id: <3ee96d83.62640234@news.grnet.gr>
On 12 Jun 2003 21:27:35 -0700, dwlepage@yahoo.com (david) wrote:
>file:
>
>dn: UserId=AC1234-5,User
>objectclass: User
>Comment: administrator
>Comment2: AC1234-5.USER.1
>
>desired output:
>
>dn: UserId=AC1234-5,User
>objectclass: User
>Comment: administrator
>Comment2: @AC1234-5
>
>Im having a hard time matching on UserId values that contain a -. If
>the UserId=(\w+) this works fine. Here is a variation of what ive
>tried:
>
>if (/\.USER\.1/) {
> s/\b(\w+)\.USER\.1/\@$1/g;
>}
> print OUT $_;
>
>
>prints:
>
>dn: UserId=AC1234-5.USER.1,User
>objectclass: User
>Comment: administrator
>Comment2: AC1234-@5
You only give one example, so it's hard to know exactly what you want
to match. Also, if that's really your output there's some more code
you're not showing us.
However, both these:
s/([\w-]+)\.USER\.1/\@$1/;
s/(\S+)\.USER\.1/\@$1/;
do the right substitution for the data you provide.
The g modifier doesn't do anything unless you expect there to be more
than one match per line.
Phil
--
Ignore coming events if you wish to send me e-mail
------------------------------
Date: Fri, 13 Jun 2003 09:18:54 +0200
From: Daniel Pfeiffer <occitan@esperanto.org>
Subject: Re: Regexp Multiple Matching Problem
Message-Id: <20030613091854.50d8bc22.occitan@esperanto.org>
Eric Amick <eric-amick@comcast.net> skribis:
> >HREF=3D\"http:\/\/$serverip\/cgi-bin\/s2h.cgi?t=3D$t&nm=3D$nm&filter=3D$=
hlight\"><SPAN
> >style=3D\"background-color: #$color\">$hlight<\/SPAN><\/A>/g;
>=20
> If you change the delimiters, you can spare yourself at least some of
> the backslashes:
>=20
> s|$hlight|<A
> HREF=3D\"http://$serverip/cgi-bin/s2h.cgi?t=3D$t&nm=3D$nm&filter=3D$hligh=
t\"><SPAN
> style=3D\"background-color: #$color\">$hlight</SPAN></A>|g;
Why only some? " is not special within s|||, so this should work fine:
s|$hlight|<A HREF=3D"http://$serverip/cgi-bin/s2h.cgi?t=3D$t&nm=3D$nm&filte=
r=3D$hlight"><SPAN style=3D"background-color: #$color">$hlight</SPAN></A>|g;
coralament / best Gr=F6tens / liebe Gr=FC=DFe / best regards / elkorajn sal=
utojn
Daniel Pfeiffer
-- GPL 3: take the wind out of Palladium's sails! --
------
-- My other stuff here too, make.pl, sawfish...: --
------
-- http://dapfy.bei.t-online.de/ --
------------------------------
Date: 13 Jun 2003 04:44:54 GMT
From: hou <dhou@removerohan.sdsu.edu>
Subject: rookie question
Message-Id: <bcbks6$dra$1@gondor.sdsu.edu>
Hello, everyone
The following is my practice, but why my loop only executed once?
(I have set the counter = 5). I can't figure it out. please help...
Script started on Thu Jun 12 21:36:44 200
rohan:1:ch4[89]% cat torf.pl
#!/usr/bin/perl
use warnings;
use strict;
my $condition;
my $counter = 5;
while( $condition = <STDIN> ){
chomp($condition);
if( $condition ){
print "|$condition| means true!!\n";
}else{
print "|$condition| means false!!\n";
}
last unless (--$counter == 0);
}
rohan:1:ch4[90]% perl torf.pl
u
|u| means true!!
rohan:1:ch4[91]% exit
rohan:1:ch4[92]%
script done on Thu Jun 12 21:37:09 200
Thank you very much
Dean
------------------------------
Date: 13 Jun 2003 05:55:11 GMT
From: damian@qimr.edu.au (Damian James)
Subject: Re: rookie question
Message-Id: <slrnbeippv.742.damian@puma.qimr.edu.au>
On 13 Jun 2003 04:44:54 GMT, hou said:
>Hello, everyone
> The following is my practice, but why my loop only executed once?
>(I have set the counter = 5). I can't figure it out. please help...
> ...
> last unless (--$counter == 0);
Well, it is doing exactly what you asked it to do.
$counter = $counter - 1;
unless ( $counter == 0 ) { last }
which is equivalent to
if ( $counter != 0 ) {last}
Perhaps you meant:
last unless --$counter;
--damian
------------------------------
Date: Fri, 13 Jun 2003 06:44:14 GMT
From: pjlees@ics.forthcomingevents.gr (Philip Lees)
Subject: Re: rookie question
Message-Id: <3ee971ba.63719031@news.grnet.gr>
On 13 Jun 2003 04:44:54 GMT, hou <dhou@removerohan.sdsu.edu> wrote:
> The following is my practice, but why my loop only executed once?
>#!/usr/bin/perl
>use warnings;
>use strict;
>
>my $condition;
>my $counter = 5;
>while( $condition = <STDIN> ){
> chomp($condition);
> if( $condition ){
> print "|$condition| means true!!\n";
> }else{
> print "|$condition| means false!!\n";
> }
> last unless (--$counter == 0);
What is the value of $counter the first time this line is executed?
>}
I think you mean
last unless --$counter;
or
last if --$counter == 0;
Phil
--
Ignore coming events if you wish to send me e-mail
------------------------------
Date: Fri, 13 Jun 2003 10:55:04 +0200
From: Ofuuzo <ofuuzo@ub.uit.no>
Subject: script to do global search & replace
Message-Id: <3EE99168.4080406@ub.uit.no>
I'm looking for a good perl script to do global search & replace on unix
Solaris. I mean it needs to handle all files in a subdirectory tree. It
does recursive search/find and replaces all occurrences of for example
'Windows Bill' with 'Open Linux'.
I have tried the following:
find . | perl -pi.bak -e "s/Windows Bill/Open Linux/g" *.pl*
It works only on a single directory and not subdirectories.
Thanks in advance.
-Ofuuzo
------------------------------
Date: Fri, 13 Jun 2003 11:59:37 +0200
From: Winfried Koenig <w.koenig@acm.org>
Subject: Re: script to do global search & replace
Message-Id: <3EE9A089.80605@acm.org>
Ofuuzo wrote:
> I'm looking for a good perl script to do global search & replace on unix
> Solaris. I mean it needs to handle all files in a subdirectory tree. It
> does recursive search/find and replaces all occurrences of for example
> 'Windows Bill' with 'Open Linux'.
> I have tried the following:
>
> find . | perl -pi.bak -e "s/Windows Bill/Open Linux/g" *.pl
>
> It works only on a single directory and not subdirectories.
any Perl question?
find . -type f -name '*.pl' | \
xargs perl -pi.bak -e "s/Windows Bill/Open Linux/g"
Winfried Koenig
------------------------------
Date: 13 Jun 2003 05:20:28 GMT
From: Martien Verbruggen <mgjv@tradingpost.com.au>
Subject: Re: Search through Array and evaluate the two
Message-Id: <slrnbeinou.luq.mgjv@verbruggen.comdyn.com.au>
On 13 Jun 2003 03:54:34 GMT,
Martien Verbruggen <mgjv@tradingpost.com.au> wrote:
[snip]
> Seriously, though, what do you mean by "print out the hash"?
> Extrapolate it in a double-quoted context?
This is, of course, not possible with a hash. But the question stands.
Martien
--
|
Martien Verbruggen | Failure is not an option. It comes bundled
Trading Post Australia | with your Microsoft product.
|
------------------------------
Date: Fri, 13 Jun 2003 14:44:36 +0530
From: Rohan Romanus Almeida <arc_of_descent@gmx.net>
Subject: test
Message-Id: <20030613144436.6f5090b3.arc_of_descent@gmx.net>
HI
This is just a test
Please ignore it
It is my first post to this group.
Hello World!
--
arc_of_descent
------------------------------
Date: Fri, 13 Jun 2003 09:49:52 +0000 (UTC)
From: "Bernard El-Hagin" <bernard.el-hagin@DODGE_THISlido-tech.net>
Subject: Re: test
Message-Id: <Xns939977FB4CFB0elhber1lidotechnet@62.89.127.66>
Rohan Romanus Almeida wrote:
>
> HI
> This is just a test
> Please ignore it
> It is my first post to this group.
Let's hope it's also the last one which breaks this group's conventions.
--
Cheers,
Bernard
--
echo 42|perl -pe '$#="Just another Perl hacker,"'
------------------------------
Date: Fri, 13 Jun 2003 00:17:50 -0400
From: Jason Parker-Burlingham <jasonp@panix.com>
Subject: Webmin security problems and use of CGI.pm
Message-Id: <87u1aupq4x.fsf@freezer.burling>
I see from a recent Debian Security Advisory (DSA 319-1) that
miniserv.pl in the webmin package does not properly handle
metacharacters, such as line feeds and carriage returns, in
Base64-encoded strings used in Basic authentication. This
vulnerability allows remote attackers to spoof a session ID, and
thereby gain root privileges.
I downloaded the source to 1.060 (1.070 is listed as a fixed version
in the advisory) and did a quick check for use of CGI.pm; it shows up
only in mon/monshow.pl. Can any webmin user or developer confirm that
this software doesn't use CGI.pm?
Hm, the README seems to confirm this is the case:
Webmin consists of a simple web server, and a number of CGI
programs which directly update system files like /etc/inetd.conf
and /etc/passwd. The web server and all CGI programs are written
in Perl version 5, and use only the standard perl modules.
Would using CGI.pm have protected against this sort of attack? I'd
like to know, not to knock the webmin developers but to gather data
about the reasons to use CGI.pm as opposed to doing the various
encodings and decodings by hand for use in future discussions with
clients.
jason
--
Stay up-to-date on what I'm doing lately:
http://www.panix.com/~jasonp
------------------------------
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 5115
***************************************
