[23739] in Perl-Users-Digest
Perl-Users Digest, Issue: 5945 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Dec 16 14:10:45 2003
Date: Tue, 16 Dec 2003 11:10: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, 16 Dec 2003 Volume: 10 Number: 5945
Today's topics:
Login to site with random image code? <l.v.g@moskuetiez.de>
Re: Login to site with random image code? <nobull@mail.com>
Re: Login to site with random image code? <Juha.Laiho@iki.fi>
Re: LWP install MacOS X <jgibson@mail.arc.nasa.gov>
Re: Planning for maintenance (Anno Siegel)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Problem building XML::LibXML on SunOS 5.6 <iain@smokehythe.net>
Problem with Win32::Console and END block. <spikeywan@bigfoot.com.delete.this.bit>
Re: recursive closures? <nobull@mail.com>
Re: Shrinkage: regexp rookie <groups@donstefani.com>
Re: stop plus (+) symbol within scalar variable being i <bart.lateur@pandora.be>
Re: stop plus (+) symbol within scalar variable being i <useperl@fastmail.fm>
Re: ticks and FreeBSD <jwillmore@remove.adelphia.net>
Re: ticks and FreeBSD <kuujinbo@hotmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 16 Dec 2003 17:01:08 GMT
From: "Lucas Van Hieng" <l.v.g@moskuetiez.de>
Subject: Login to site with random image code?
Message-Id: <oTGDb.323$Z57.278@newssvr27.news.prodigy.com>
What I am trying to do is write a Perl script that process a certain
webpage that requires me to be logged in:
(http://www.starlance.us/MW4/)
They recently redid the site, so now it requires that you enter the
random 5 digit number shown on a png image. (Before there was no such
extra security and I was able to POST with LWP:UserAgent.)
Is there way at all around these things? I'm guessing that this would be
easier than with what MSN and Yahoo use, which is often a scrambled
mess. This site however uses uniform text (as if just typed into the
image with text tool and saved.) Is there anyway to do some sort of OCR
(char recognition) on the fly?
Thanks for any info on this.
------------------------------
Date: 16 Dec 2003 17:49:06 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: Login to site with random image code?
Message-Id: <u9zndshcvh.fsf@wcl-l.bham.ac.uk>
"Lucas Van Hieng" <l.v.g@moskuetiez.de> writes:
> What I am trying to do is write a Perl script that process a certain
> webpage that requires me to be logged in:
>
> (http://www.starlance.us/MW4/)
>
> They recently redid the site, so now it requires that you enter the
> random 5 digit number shown on a png image.
> Is there way at all around these things?
There was a rather intersting talk on this at YAPC::Europe::2003
Dunno if you can find it online.
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
Date: Tue, 16 Dec 2003 18:22:01 GMT
From: Juha Laiho <Juha.Laiho@iki.fi>
Subject: Re: Login to site with random image code?
Message-Id: <brniem$nm7$2@ichaos.ichaos-int>
"Lucas Van Hieng" <l.v.g@moskuetiez.de> said:
>What I am trying to do is write a Perl script that process a certain
>webpage that requires me to be logged in:
>
>(http://www.starlance.us/MW4/)
>
>They recently redid the site, so now it requires that you enter the
>random 5 digit number shown on a png image. (Before there was no such
>extra security and I was able to POST with LWP:UserAgent.)
>
>Is there way at all around these things?
Have you considered the social approach -- that is, describe your use
and need to the site admins, and ask whether they can provide another
method for authentication?
--
Wolf a.k.a. Juha Laiho Espoo, Finland
(GC 3.0) GIT d- s+: a C++ ULSH++++$ P++@ L+++ E- W+$@ N++ !K w !O !M V
PS(+) PE Y+ PGP(+) t- 5 !X R !tv b+ !DI D G e+ h---- r+++ y++++
"...cancel my subscription to the resurrection!" (Jim Morrison)
------------------------------
Date: Tue, 16 Dec 2003 09:52:55 -0800
From: Jim Gibson <jgibson@mail.arc.nasa.gov>
Subject: Re: LWP install MacOS X
Message-Id: <161220030952553659%jgibson@mail.arc.nasa.gov>
In article <BBFE35BB.19075%henryn@zzzspacebbs.com>, Henry
<henryn@zzzspacebbs.com> wrote:
> Folks:
>
> I need LWP. It doesn't come with Jaguar.
>
>
There are instructions for installing Perl 5.8 on Mac OS 10.2 at
http://developer.apple.com/internet/macosx/perl.html
I was able to successfully install Perl 5.8.2 under 10.2.8 on two
different Macs following these instructions (Mac OS 10.2 comes with
Perl 5.6.0 installed). I had already installed the Developer tools. It
did take awhile (1 hour?) to install Perl, after which I was happily
installing CPAN modules for the next hour. The only one I had trouble
with was Module::Build, which was required by DateTime and at least one
other module. The Module::Build installation process hung on the basic
tests the first two times I tried to install it, but worked the third
try 3 days later. Perseverance helps, as does the "force install"
command to the CPAN shell.
Over the weekend, I upgraded one of the Macs to Panther, installing the
new developer tools CD. I did a "clean" install on the operating
system, then moved /usr/local from the Previous System to the new
System folder. Perl 5.8.2 was back up and running without having to
reinstall it.
------------------------------
Date: 16 Dec 2003 08:30:39 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Planning for maintenance
Message-Id: <brmfrf$d4t$1@mamenchi.zrz.TU-Berlin.DE>
Uri Guttman <uri@stemsystems.com> wrote in comp.lang.perl.misc:
> >>>>> "AS" == Anno Siegel <anno4000@lublin.zrz.tu-berlin.de> writes:
[...]
> >> Indeed. On the other hand, if you'd had the bad-fortune to choose a
> >> function name which later turned out to clash with some other needed
> >> module...
>
> > ...all is not lost. This renames a function on import:
>
> > use Exporter::Renaming;
> > use MyModule Renaming => [ clash => 'no_clash'];
>
> i had proposed a grant project to TPF for a similar thing. this module
[...]
> i will have to investigate Renaming to see how it does this. ...
Simple and brutal -- it commandeers Exporter::import and replaces
it with a modified version of itself that understands renaming.
("no Exporter::Renaming" restores the original.) The modified
import() uses the original one to import everything into a dummy
name space, just to make sure no export restrictions are violated.
Thein the actual renaming happens in so many simple typeglob assignments
into the user's name space.
Anno
------------------------------
Date: Tue, 16 Dec 2003 02:22:08 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <EfudnUutk4YtXUOiRVn-iQ@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: Tue, 16 Dec 2003 17:42:19 +0000
From: Iain <iain@smokehythe.net>
Subject: Problem building XML::LibXML on SunOS 5.6
Message-Id: <brng5s$abu$1@new-usenet.uk.sun.com>
Hi,
I'm trying to build XML::LibXML in non-standard directories on Solaris
and I'm going insane in the process. I fail trying the non standard
directories and my normal perl directory, so I'm guessing this is a
fundamental issue that has me flummoxed.
I don't normally have issues keeping my XML::LibXML/LibXSLT APIs up to
date, but then that's usually on SuSE running straight-forward Gnu stuff.
I've tried both Gnu & Distributed make tools, here are the details of
the other tools I'm using.
* Forte Developer 7 C 5.4 2002/03/09
* GNU ld version 2.13
Supported emulations:
elf32_sparc
* Forte Developer 7 Distributed Make 7.2 2002/03/10
* GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
I have the latest zlib, libxml2, libxslt, libxml, libiconv compiled and
installed (used dmake for those) without issues; ran the checks and
everything ok there.
The dialog (from my attemp to install in site perl directory) follows.
Any help here would be immensely appreciated... cue unconsolable weeping...
Thanks,
Iain.
# perl Makefile.PL
enable native perl UTF8
running xml2-config...ok
looking for -lxml2... yes
Checking if your kit is complete...
Looks good
Writing Makefile for XML::LibXML
# make
cp lib/XML/LibXML/SAX.pm blib/lib/XML/LibXML/SAX.pm
cp lib/XML/LibXML/Number.pm blib/lib/XML/LibXML/Number.pm
cp lib/XML/LibXML/DOM.pod blib/lib/XML/LibXML/DOM.pod
cp lib/XML/LibXML/SAX/Builder.pm blib/lib/XML/LibXML/SAX/Builder.pm
cp lib/XML/LibXML/Literal.pm blib/lib/XML/LibXML/Literal.pm
cp lib/XML/LibXML/Node.pod blib/lib/XML/LibXML/Node.pod
cp lib/XML/LibXML/Parser.pod blib/lib/XML/LibXML/Parser.pod
cp LibXML.pm blib/lib/XML/LibXML.pm
cp lib/XML/LibXML/DocumentFragment.pod
blib/lib/XML/LibXML/DocumentFragment.pod
cp lib/XML/LibXML/SAX/Parser.pm blib/lib/XML/LibXML/SAX/Parser.pm
cp lib/XML/LibXML/Element.pod blib/lib/XML/LibXML/Element.pod
cp lib/XML/LibXML/Namespace.pod blib/lib/XML/LibXML/Namespace.pod
cp lib/XML/LibXML/Attr.pod blib/lib/XML/LibXML/Attr.pod
cp lib/XML/LibXML/SAX/Builder.pod blib/lib/XML/LibXML/SAX/Builder.pod
cp lib/XML/LibXML/Document.pod blib/lib/XML/LibXML/Document.pod
cp lib/XML/LibXML/SAX/Generator.pm blib/lib/XML/LibXML/SAX/Generator.pm
cp lib/XML/LibXML/CDATASection.pod blib/lib/XML/LibXML/CDATASection.pod
cp LibXML.pod blib/lib/XML/LibXML.pod
cp lib/XML/LibXML/Boolean.pm blib/lib/XML/LibXML/Boolean.pm
cp lib/XML/LibXML/SAX.pod blib/lib/XML/LibXML/SAX.pod
cp lib/XML/LibXML/Text.pod blib/lib/XML/LibXML/Text.pod
cp lib/XML/LibXML/PI.pod blib/lib/XML/LibXML/PI.pod
cp lib/XML/LibXML/NodeList.pm blib/lib/XML/LibXML/NodeList.pm
cp lib/XML/LibXML/Comment.pod blib/lib/XML/LibXML/Comment.pod
cp lib/XML/LibXML/Dtd.pod blib/lib/XML/LibXML/Dtd.pod
/opt/perl5.8.0/bin/perl /opt/perl5.8.0/lib/5.8.0/ExtUtils/xsubpp
-typemap /opt/perl5.8.0/lib/5.8.0/ExtUtils/typemap -typemap typemap
LibXML.xs > LibXML.xsc && mv LibXML.xsc LibXML.c
cc -c -I/WWW/ns-home/sandpit/svcs/local/include/libxml2
-I/WWW/ns-home/sandpit/svcs/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -O -DVERSION=\"1.56\" -DXS_VERSION=\"1.56\"
-KPIC "-I/opt/perl5.8.0/lib/5.8.0/sun4-solaris/CORE" -DHAVE_UTF8
-DHAVE_BLANK LibXML.c
"/WWW/ns-home/sandpit/svcs/local/include/libxml2/libxml/DOCBparser.h",
line 18: #warning: "The DOCBparser module has been deprecated in
libxml2-2.6.0"
"LibXML.xs", line 73: only one storage class allowed
"LibXML.xs", line 74: only one storage class allowed
"LibXML.xs", line 76: only one storage class allowed
"LibXML.xs", line 77: only one storage class allowed
"LibXML.xs", line 78: only one storage class allowed
"LibXML.xs", line 79: only one storage class allowed
"LibXML.xs", line 4319: warning: argument #1 is incompatible with prototype:
prototype: pointer to const unsigned char :
"/WWW/ns-home/sandpit/svcs/local/include/libxml2/libxml/parser.h", line 811
argument : pointer to char
"LibXML.xs", line 4377: warning: implicit function declaration:
xmlC14NDocDumpMemory
cc: acomp failed for LibXML.c
make: *** [LibXML.o] Error 2
--
Blow the smoke from my address if replying personally.
------------------------------
Date: Tue, 16 Dec 2003 18:05:48 -0000
From: "Richard S Beckett" <spikeywan@bigfoot.com.delete.this.bit>
Subject: Problem with Win32::Console and END block.
Message-Id: <brnhku$k0i$1@newshost.mot.com>
I want to set my dos window up with 80 cols and 100 lines, but when I do I
break my END block. Here's an example...
use strict;
use warnings;
$| =1;
# use Win32::Console;
# my $BUFFER = new Win32::Console(STD_OUTPUT_HANDLE);
# $BUFFER->Size(80,100);
for (1..5) {print "."; sleep 1}
exit;
END {print "\n\nPress Enter\n"; <STDIN>;}
In the above form it works. BUT remove the comments from the first 2 or 3
(commented) lines, and the PRINT statement in the END block stops working.
The <STDIN> still works, though.
What am I doing wrong _this_ time? ;-)
W2K, active perl V5.8.1 build 807.
Thanks.
--
R.
GPLRank +79.699
------------------------------
Date: 16 Dec 2003 17:25:58 +0000
From: Brian McCauley <nobull@mail.com>
Subject: Re: recursive closures?
Message-Id: <u9k74wisih.fsf@wcl-l.bham.ac.uk>
Uri Guttman <uri@stemsystems.com> writes:
> >>>>> "BM" == Brian McCauley <nobull@mail.com> writes:
>
> > Uri Guttman <uri@stemsystems.com> writes:
> >> my $sub ;
> >> $sub = sub{ blah; $sub->() }
>
> > That leaks.
>
> it isn't real code anyhow. i don't recall if damian's leaked or he
> weakened it.
>
> > use Scalar::Util qw( weaken );
> > my $weak_sub;
> > my $sub = sub{ blah; $weak_sub->() }
> > weaken($weak_sub = $sub);
>
> it would only leak if you let it fall out of scope without destroying it
> (but how?).
"You only need weak references if you don't want use some other way to
take care of tracking and breaking the circular dependancy on every
possible exit path" is true of anything that uses weak references.
Of course if you want $sub to be a variable that is forcably undefined
implicitly at the end of a scope scope then Perl has just such a thing
- the local() variable!
Now, of course, it is an annoying miss-feature that local() can't be
applied to lexical variables so if you want to use local() you are for
forced to use package variables. What one really wants to do is...
# Won't work
my $sub;
local $sub = sub{ blah; $sub->() }
...but one is forced to do...
our $sub;
local $sub = sub{ blah; $sub->() }
--
\\ ( )
. _\\__[oo
.__/ \\ /\@
. l___\\
# ll l\\
###LL LL\\
------------------------------
Date: Tue, 16 Dec 2003 17:19:55 GMT
From: Don Stefani <groups@donstefani.com>
Subject: Re: Shrinkage: regexp rookie
Message-Id: <3FDF3EBE.5010405@donstefani.com>
Uri Guttman wrote:
> $_ = join( ',', /:\s+(.+?)</g ) for $ary2[2] ;
Thank you.
Don
------------------------------
Date: Tue, 16 Dec 2003 09:28:06 GMT
From: Bart Lateur <bart.lateur@pandora.be>
Subject: Re: stop plus (+) symbol within scalar variable being interpolated in RE when followed by a number
Message-Id: <apjttvckf943a5j139vdmoprg2q3f6556o@4ax.com>
Matthew Braid wrote:
>if ($string =~ /\Q$RE/) {
> print "I found the RE!\n";
>}
>
>\Q quotes everything up to the end of the re or until a \E is found.
>
>There is still a problem - if $RE contains '\E'.
That's not how it works. \Q applies a quotemeta() to the whole of the
variables in the regex, irrespective of their contents. Only literal
embedded '\E' sequences in the regex itself, are taken into account.
$RE = 'a\E+';
$_ = 'aaaaa\E+++++';
/(\Q$RE\E)/ and print $1;
-->
a\E+
--
Bart.
------------------------------
Date: Tue, 16 Dec 2003 12:32:34 +0300
From: "Anton Shcherbinin" <useperl@fastmail.fm>
Subject: Re: stop plus (+) symbol within scalar variable being interpolated in RE when followed by a number
Message-Id: <brmjfj$54lqn$1@ID-211973.news.uni-berlin.de>
Tuesday, December 16, 2003 5:17 "Tom" <clicker@well.ox.ac.uk> wrote in
news:bdc11bf2.0312151817.67e55abc@posting.google.com ...
> my $string = "catch+22";
> my $RE = "h+22";
> if ($string =~ /$RE/) {
> print "I found the RE.\n";
> }
> It does not find the string h+22 within the catch+22. I can see why,
> but don't know how to remedy it.
Tom, it looks like you just need to find a substring $RE within a string
$string. If so, you may not use regular expressions at all.
print "I found the RE.\n" if index($string, $RE) > -1;
index() function will do.
--
Anton
------------------------------
Date: Tue, 16 Dec 2003 06:02:35 GMT
From: James Willmore <jwillmore@remove.adelphia.net>
Subject: Re: ticks and FreeBSD
Message-Id: <20031216010233.6ea32a7c.jwillmore@remove.adelphia.net>
On Mon, 15 Dec 2003 17:38:49 GMT
Erik Tank <jundy@jundy.com> wrote:
> I just migrated a program from RedHat 9 to FreeBSD 5.1. Everything
> is working well with the exception of the following:
> my @jmail_return_lines = `ps -aux | grep 'jmaild' | grep -v grep`;
>
>
> The baisc idea is that I want to see if a program called jmaild is
> running. On RedHat 9 it @jmail_return_lines would contain the ps
> -aux lines but under FreeBSD it returns nothing even though when I
> take the command in the ticks and run it from the command line it
> does return a line.
>
> Any help or suggestions would be greatly appreciated.
You could look into using a module..
Take a look at Proc::Table.
HTH
--
Jim
Copyright notice: all code written by the author in this post is
released under the GPL. http://www.gnu.org/licenses/gpl.txt
for more information.
a fortune quote ...
The light at the end of the tunnel is the headlight of an
approaching train.
------------------------------
Date: Tue, 16 Dec 2003 17:48:53 +0900
From: ko <kuujinbo@hotmail.com>
Subject: Re: ticks and FreeBSD
Message-Id: <brmgun$at4$1@pin3.tky.plala.or.jp>
Erik Tank wrote:
> I just migrated a program from RedHat 9 to FreeBSD 5.1. Everything is
> working well with the exception of the following:
> my @jmail_return_lines = `ps -aux | grep 'jmaild' | grep -v grep`;
>
>
> The baisc idea is that I want to see if a program called jmaild is
> running. On RedHat 9 it @jmail_return_lines would contain the ps -aux
> lines but under FreeBSD it returns nothing even though when I take the
> command in the ticks and run it from the command line it does return a
> line.
>
> Any help or suggestions would be greatly appreciated.
>
> Erik
Works for me, Perl 5.005_03 and 5.8.2 (changed shebang line for 5.8.2).
FreeBSD 4.9 - but that shouldn't matter since the options to grep and ps
are the same:
$ cat ticks && ./ticks
#!/usr/bin/perl -w
use strict;
my @sh = `ps -ax | grep '/bin/sh' | grep -v grep`;
print $sh[0];
452 p1 S 0:00.01 /bin/sh
Have you tried looking for problems elsewhere in the script? Do you have:
use strict;
use warnings;
enabled at the top of the script? If not, that would be a good start.
HTH - keith
------------------------------
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 5945
***************************************
