[24186] in Perl-Users-Digest
Perl-Users Digest, Issue: 6378 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Apr 9 03:05:38 2004
Date: Fri, 9 Apr 2004 00:05:08 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 9 Apr 2004 Volume: 10 Number: 6378
Today's topics:
Re: [VERY OT] a linguistic question (.sig-related, xpos <bik.mido@tiscalinet.it>
Re: Detecting Local Admin for Win32 <MrReallyVeryNice.NOVIRUS@NoSpam.yahoo.com>
Re: Help: exporter is "internal" class <dug@plusthree.com>
Re: I cann't scale gif with correctly with perlmagick. (kenny)
Re: MySQL perl script <jtc@shell.dimensional.com>
Re: MySQL perl script <tojess2@btinternet.com>
Re: MySQL perl script <tojess2@btinternet.com>
Re: MySQL perl script <1usa@llenroc.ude>
Re: Object oriented gui with Perl/Tk ... how can I make (Nataku)
Re: Perl neq Python <bik.mido@tiscalinet.it>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
problem calling perl script from SOAP server perl scrip (pj)
Re: scoping, sig handlers, and labels <bik.mido@tiscalinet.it>
Re: Stick Lines Between Text vjp2.at@at.BioStrategist.dot.dot.com
Re: Tough (for me) regex case (ko)
Re: Tough (for me) regex case <matthew.garrish@sympatico.ca>
Re: Tough (for me) regex case <matthew.garrish@sympatico.ca>
Re: WebExplorer as Perl-CGI <nospam@bigpond.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 09 Apr 2004 09:00:53 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: [VERY OT] a linguistic question (.sig-related, xposted)
Message-Id: <7p5b705bhkebrsmpbvaspah1pic3d7uoon@4ax.com>
On 7 Apr 2004 21:56:21 GMT, Giuseppe Bilotta <bilotta78@hotpop.com>
wrote:
>I'm not a native speaker, but I would go for "in"; "on" sounds a
>little like Mr. Hacker was talking *about* comp.foo.bar, rather tha
>posting *to* the newsgroup.
Grazie, sembra che la maggior parte della gente sia d'accordo con
questa opinone!
[Thank you, it seems that people mostly share this opinion!]
Not a native speaker either,
Michele
--
you'll see that it shouldn't be so. AND, the writting as usuall is
fantastic incompetent. To illustrate, i quote:
- Xah Lee trolling on clpmisc,
"perl bug File::Basename and Perl's nature"
------------------------------
Date: Thu, 8 Apr 2004 20:39:01 -0700
From: "MrReallyVeryNice" <MrReallyVeryNice.NOVIRUS@NoSpam.yahoo.com>
Subject: Re: Detecting Local Admin for Win32
Message-Id: <muadnaaNJo41huvdRVn-sA@comcast.com>
Hi AgnosticPope,
A few months back I had the same needs and I did a bit of research on
Google. No need to reinvent the wheel if someone has already done the work.
I came up with the following results:
http://www.faqchest.com/prgm/perlu-l/perl-03/perl-0305/perl-030500/perl03050
716_23494.html
I have been running a variant of the code provided in the above URL
successfully on W2K since then. Mileage might vary depending on your
operating system. I make no guarantee. :-) Just because I'm nice and
honest, I'm pasting the original code here instead of giving you my script.
Give a try to:
use Win32::API;
$isadmin = new Win32::API('advpack.dll', 'IsNTAdmin', 'NN', 'N');
$status=$isadmin->Call(0,0);
if($status != 0) { print "You are an administrator."; }
else { print "You are not an administrator."; }
Let us know if that solves your problem.
MrReallyVeryNice (who gives credit where it is due!)
------------------------------
Date: Fri, 09 Apr 2004 00:53:46 -0400
From: Douglas Hunter <dug@plusthree.com>
Subject: Re: Help: exporter is "internal" class
Message-Id: <c55a9g$rke$0@pita.alt.net>
Amanda wrote:
> I'm stumped. I'm trying to import symbols from a subclass of
> Exporter that is not named after the file it is in (to be more
> specific, the Exporter subclass is XML::DOM::Node, which is defined
> in the file XML/DOM.pm). When I try lines such as
>
> use XML::DOM::Node '_C';
>
> perl complains with "Can't locate XML/DOM/Node.pm".
`perldoc -f require` should shed some light on that.
> (In this case,
> the symbol _C is in @EXPORT_OK, so it must be imported explicitly.)
> How can I import symbols from XML::DOM::Node?
You have a different version of XML::DOM than I do, but one way you
should be able to do this is:
use XML::DOM;
*_C = \&XML::DOM::Node::_C; # alias &_C to its
# counterpart in XML::DOM::Node;
# and later...
_C();
>
> Thanks,
>
> amanda
>
-- Douglas
------------------------------
Date: 8 Apr 2004 21:48:25 -0700
From: kennyjohn00001@yahoo.com (kenny)
Subject: Re: I cann't scale gif with correctly with perlmagick.
Message-Id: <2eebf9a.0404082048.46dd8d1@posting.google.com>
Thanks correct my syntax.
$image->Scale(Width => $Width, Height => $Height);
but anyway, after i correct to this also face the same problem.
after scaling animate gif(multiple image).
the first image look is okay.
but the 2nd image and following image look like got some white dot or
sometime got black dot at the image.
i think it cann't scale in correct way especially scale the image to
small size.
anyone got any ideal or method to scale the gif?
------------------------------
Date: 8 Apr 2004 23:22:27 -0600
From: Jim Cochrane <jtc@shell.dimensional.com>
Subject: Re: MySQL perl script
Message-Id: <slrnc7ccoj.1ga.jtc@shell.dimensional.com>
In article <4075da0d$0$24341$58c7af7e@news.kabelfoon.nl>, John Bokma wrote:
>
>
> Sandman wrote:
>
>> In article <c54hmo$dci$1@sparta.btinternet.com>,
>> "Jess" <tojess2@btinternet.com> wrote:
>>
>>
>>>I found this on the Internet. I think this is similar to what I want.
>>>However, I wanted to keep a log of the changes in case of problems, so I can
>>>undo the changes. So each record changed needs to be written to a file. I
>>>dont think this is possible using update, so how do I loop through a
>>>recordset using perl?
>>>
>>>#!/usr/bin/perl -w
>
> use warnings;
>
> not -w
Sorry to get off the topic of the thread, but I've been wondering whether
it's best to include "use warnings" in a module file or just use the -w
option when the program is run. So, with that background, I'll ask:
Why do you suggest the "use warnings" method?
Thanks.
------------------------------
Date: Fri, 9 Apr 2004 06:32:38 +0000 (UTC)
From: "Jess" <tojess2@btinternet.com>
Subject: Re: MySQL perl script
Message-Id: <c55g26$iko$1@sparta.btinternet.com>
>
>>$dbh=DBI->connect('DBI:mysql:$db_info[dbname]:localhost','$username','$pas
sw
> >>ord')
>
> This line has 4 errors. '' doesn´t interpolate, and [dbname] is the
> wrong way to access a hash.
Do you mean it doesnt have a $ in front of it? Should I be using [$dbname]
?
What do you mean by interpolate ?
The data is important, you are scaring me off this idea. Can using perl
corrupt the data?
Jess
"John Bokma" <postmaster@castleamber.com> wrote in message
news:4075da0d$0$24341$58c7af7e@news.kabelfoon.nl...
>
>
> Sandman wrote:
>
> > In article <c54hmo$dci$1@sparta.btinternet.com>,
> > "Jess" <tojess2@btinternet.com> wrote:
> >
> >
> >>I found this on the Internet. I think this is similar to what I want.
> >>However, I wanted to keep a log of the changes in case of problems, so I
can
> >>undo the changes. So each record changed needs to be written to a file.
I
> >>dont think this is possible using update, so how do I loop through a
> >>recordset using perl?
> >>
> >>#!/usr/bin/perl -w
>
> use warnings;
>
> not -w
>
> >>use strict;
> >>use DBI;
> >>my $username = 'username';
> >>my $password = 'password';
> >>my %db_info = (dbname => 'dbname');
> >>my
>
>>$dbh=DBI->connect('DBI:mysql:$db_info[dbname]:localhost','$username','$pas
sw
> >>ord')
>
> This line has 4 errors. '' doesn´t interpolate, and [dbname] is the
> wrong way to access a hash.
>
> or
> >>die "Could not connect to database: " . DBI->errstr;
> >>my $Query = "UPDATE tablename SET fieldname = newvalue WHERE value = 1";
> >>my $insert=$dbh->prepare("$Query");
>
> No need to put "" around $Query. Also use the convention(s) most Perl
> programmers use, variable names lower case.
>
> >>$insert->execute() or die "Could not execute SQL statement";
> >>$insert->finish();
> >>$dbh->disconnect();
> >
> > Too loop through a recordset, do something like this:
> >
> > my $get_people = $dbh->prepare("select * from people");
> > $get_people->execute;
> >
> > while ($a = $get_people->fetchrow_hashref()) {
> > print "$$a{firstname}\n";
> > }
> >
>
>
> --
> John personal page: http://johnbokma.com/
>
> Experienced Perl / Java developer available - http://castleamber.com/
------------------------------
Date: Fri, 9 Apr 2004 06:33:42 +0000 (UTC)
From: "Jess" <tojess2@btinternet.com>
Subject: Re: MySQL perl script
Message-Id: <c55g46$fp2$1@titan.btinternet.com>
Thanks for the assistance sandman, I can see what you are doing there and
will try a few testers with this info.
Jess
"Sandman" <mr@sandman.net> wrote in message
news:mr-142507.00084409042004@news.fu-berlin.de...
> In article <c54hmo$dci$1@sparta.btinternet.com>,
> "Jess" <tojess2@btinternet.com> wrote:
>
> > I found this on the Internet. I think this is similar to what I want.
> > However, I wanted to keep a log of the changes in case of problems, so I
can
> > undo the changes. So each record changed needs to be written to a file.
I
> > dont think this is possible using update, so how do I loop through a
> > recordset using perl?
> >
> > #!/usr/bin/perl -w
> > use strict;
> > use DBI;
> > my $username = 'username';
> > my $password = 'password';
> > my %db_info = (dbname => 'dbname');
> > my
> >
$dbh=DBI->connect('DBI:mysql:$db_info[dbname]:localhost','$username','$passw
> > ord') or
> > die "Could not connect to database: " . DBI->errstr;
> > my $Query = "UPDATE tablename SET fieldname = newvalue WHERE value = 1";
> > my $insert=$dbh->prepare("$Query");
> > $insert->execute() or die "Could not execute SQL statement";
> > $insert->finish();
> > $dbh->disconnect();
>
> Too loop through a recordset, do something like this:
>
> my $get_people = $dbh->prepare("select * from people");
> $get_people->execute;
>
> while ($a = $get_people->fetchrow_hashref()) {
> print "$$a{firstname}\n";
> }
>
> --
> Sandman[.net]
------------------------------
Date: 9 Apr 2004 06:51:46 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude>
Subject: Re: MySQL perl script
Message-Id: <Xns94C61D1FB6E26asu1cornelledu@132.236.56.8>
"Jess" <tojess2@btinternet.com> wrote in
news:c55g26$iko$1@sparta.btinternet.com:
>>
>>>$dbh=DBI->connect('DBI:mysql:$db_info[dbname]:localhost','$username','
>>>$password')
>>
>> This line has 4 errors. '' doesn´t interpolate, and [dbname] is the
>> wrong way to access a hash.
>
> Do you mean it doesnt have a $ in front of it? Should I be using
> [$dbname] ?
$db_info{db_name}
You should be reading the first chapter of an introductory Perl book or
perldoc perlsyn.
> What do you mean by interpolate ?
Again, learning just a little bit of Perl before programming in Perl
might be a good idea.
> The data is important, you are scaring me off this idea. Can using
> perl corrupt the data?
Perl will not corrupt your data but you might.
--
A. Sinan Unur
1usa@llenroc.ude (reverse each component for email address)
------------------------------
Date: 8 Apr 2004 20:50:25 -0700
From: Crapnut566@yahoo.com (Nataku)
Subject: Re: Object oriented gui with Perl/Tk ... how can I make this work?
Message-Id: <7e48fc99.0404081950.608d051b@posting.google.com>
Good news - it works, and I havent been able to detect any memory
leaks as of yet.
True, Java does not have them ... but im not a Java developer, I do
Perl for my living. I just did Java for classes, Perl is my passion -
and what work pays me for, at least currently. If need be I can learn
a different language, but I would rather not don a different guru hat.
------------------------------
Date: Fri, 09 Apr 2004 09:00:57 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Perl neq Python
Message-Id: <636b70lq5kocjf7dfr8qdt0qjk02o7o7dl@4ax.com>
On Thu, 08 Apr 2004 08:50:49 GMT, Joe Smith <Joe.Smith@inwap.com>
wrote:
>>>>Under what circumstances should I use Perl, Python or straight shell
>>>>scripting?
>>>
>>>If you _really_ know each of these programming languages/techniques,
>>>you know what to use and when to use it.
>>
>> Re read his question. He never claimed to be an expert.
>
>I agree with Tore; it's sort of a Zen question.
> If you have to ask, it means you won't understand the answer.
> If you know enough to understand the answer, you won't need the question.
Cool!
OTOH the OP may be interested in reading:
perldoc -q 'How does Perl compare with other languages'
perldoc -q 'Can I do [task] in Perl'
perldoc -q 'When shouldn\'t I program in Perl?'
Michele
--
you'll see that it shouldn't be so. AND, the writting as usuall is
fantastic incompetent. To illustrate, i quote:
- Xah Lee trolling on clpmisc,
"perl bug File::Basename and Perl's nature"
------------------------------
Date: Fri, 09 Apr 2004 01:22:23 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <nfqdnRkMqq6C3OvdRVn-hA@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.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: 8 Apr 2004 22:49:21 -0700
From: nsf470@yahoo.com (pj)
Subject: problem calling perl script from SOAP server perl script
Message-Id: <11711ebf.0404082149.1fe44413@posting.google.com>
Hi
I am trying to call a perl script from SOAP server side perl script,
but no luck.
following is the SOAP server perl script where I call other perl
script. read_query function writes to a file okay, but does nothing
for the two system calls after that. Any ideas? thanks in advance
#!/usr/bin/perl
use lib '../lib';
use SOAP::Transport::HTTP;
SOAP::Transport::HTTP::CGI
-> dispatch_to('predictor')
-> handle;
package predictor;
sub read_query{
my $file=$_[0];
open (fileOUT, "> dBDataFiles/$file");
foreach $line (@_)
{
print fileOUT "$line";
}
close (fileOUT);
# Problem:: nothing happens for the nest two system commands.
system ("/bin/echo hello > dBDataFiles/test");
system ("/usr/bin/perl /home/nsf470/out.pl");
return "done"."\n\n";
}
------------------------------
Date: Fri, 09 Apr 2004 09:00:49 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: scoping, sig handlers, and labels
Message-Id: <5m3b70hrilmqbfajhrbm9b34mpq1grhjbo@4ax.com>
On Wed, 07 Apr 2004 18:52:49 -0600, Bill <wherrera@lynxview.com>
wrote:
>my $rdo = sub { goto REDO; };
>
>REDO:
>foreach(1...1000) {
> print "$_ ... ";
> $SIG{ALRM}= $rdo->();
> alarm 10;
> system "sleep $_"; # don't use builtin sleep, just in case.
> alarm 0;
> print "$_\n";
>}
>
>This one loops forever, but I don't see why it does, and why your
>example cannot see the REDO scope. Maybe closures are buggy here?
What does this have to do with closures? Do you see any closure?!?
You want
$SIG{ALRM}= $rdo
instead!
Michele
--
you'll see that it shouldn't be so. AND, the writting as usuall is
fantastic incompetent. To illustrate, i quote:
- Xah Lee trolling on clpmisc,
"perl bug File::Basename and Perl's nature"
------------------------------
Date: Fri, 9 Apr 2004 04:21:11 +0000 (UTC)
From: vjp2.at@at.BioStrategist.dot.dot.com
Subject: Re: Stick Lines Between Text
Message-Id: <c558bm$hhi$2@reader1.panix.com>
*+-I want to take a text file less than 80 chars across
*+-and break each line in two at the space neared the middle
*+-(I can use fold if the batch editor can't)
*+-Then I want to make it double spaced.
*+-Every second blank (fourth of the total) line should then
*+-be replace with a line of "-" characters..
*+-and then every second dashed line (every fourth blank aka every eighth
*+-actual) should be replace wit a line of "+" characters..
*+-anyone have any good ways to do this?
*+-I prefer SED but I'd take PERL or AWK
*+-pls cc email
- = -
Vasos-Peter John Panagiotopoulos II, Columbia'81+, Bio$trategist
BachMozart ReaganQuayle EvrytanoKastorian
http://ourworld.compuserve.com/homepages/vjp2/vasos.htm
---{Nothing herein constitutes advice. Everything fully disclaimed.}---
------------------------------
Date: 8 Apr 2004 19:15:10 -0700
From: kuujinbo@hotmail.com (ko)
Subject: Re: Tough (for me) regex case
Message-Id: <92d64088.0404081815.7e312bd0@posting.google.com>
spamtotrash@toomuchfiction.com (Kevin Collins) wrote in message news:<a6882f32.0404081415.5c26119c@posting.google.com>...
> "Brian Davis" <brian@knowdotnet.nospam.com> wrote in message news:<ek957sFGEHA.3404@TK2MSFTNGP10.phx.gbl>...
> > You can use the following expression:
> >
> > "(?<no_quotes>(""|[^"])*)"
> >
> > Simply access the value of the named group "no_quotes" for each match
> > returned.
> >
> >
> > Brian Davis
> > http://www.knowdotnet.com
[snip]
> Can you point me to some documentation (man page, etc) that describes
> a "named group"? I've searched the perlre man page and cannot seem to
> find any reference to named groups or an example similar to yours.
>
> How about showing us (me?) how to access the named group?
>
> Thanks,
>
> Kevin
I couldn't find a reference either - also checked 'perlreref' and
'perlrequick'.
The OP posted to microsoft.public.dotnet.framework besides
comp.lang.perl.misc, so did a quick index check of the second edition
of 'Mastering Regular Expressions'. It states that named capture is
specific to .NET and Python.
HTH - keith
------------------------------
Date: Thu, 8 Apr 2004 23:08:31 -0400
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Tough (for me) regex case
Message-Id: <Jsodc.11262$BF2.1086405@news20.bellglobal.com>
"Richard Morse" <remorse@partners.org> wrote in message
news:remorse-41C993.17314006042004@plato.harvard.edu...
> In article <lt0n60d4k4rv7hukaei12s0tsq2p6btc80@4ax.com>,
> Rob Perkins <rob_perkins@hotmail.com> wrote:
>
> > /(?<!")"(?!")(.*?)(?<!")"(?!")/, on my sample string, produces:
> >
> > <>
> > "quick"
> > "fox jumped ""over"" the"
> > </>
> >
> > How should I modify the regex to get:
> > <>
> > quick
> > fox jumped ""over"" the
> > </>
> >
> > ...in other words, without the quotes as first and last characters in
> > the matches?
>
> You could add a second and third pass:
> s/^"//;
> s/"$//;
>
Second and third passes? Yuck!
The quotes could be removed in one regex, but in this case the match pattern
*does not* produce the results the OP claims and so no other processing
should be necessary. If there are quotation marks at the beginning and end
of the strings, I would hazard a guess that the OP added them somewhere his
code.
Matt
------------------------------
Date: Thu, 8 Apr 2004 23:24:37 -0400
From: "Matt Garrish" <matthew.garrish@sympatico.ca>
Subject: Re: Tough (for me) regex case
Message-Id: <OHodc.11273$BF2.1092152@news20.bellglobal.com>
"ko" <kuujinbo@hotmail.com> wrote in message
news:92d64088.0404081815.7e312bd0@posting.google.com...
> spamtotrash@toomuchfiction.com (Kevin Collins) wrote in message
news:<a6882f32.0404081415.5c26119c@posting.google.com>...
> > "Brian Davis" <brian@knowdotnet.nospam.com> wrote in message
news:<ek957sFGEHA.3404@TK2MSFTNGP10.phx.gbl>...
> > > You can use the following expression:
> > >
> > > "(?<no_quotes>(""|[^"])*)"
> > >
> > > Simply access the value of the named group "no_quotes" for each match
> > > returned.
> > >
>
> > Can you point me to some documentation (man page, etc) that describes
> > a "named group"? I've searched the perlre man page and cannot seem to
> > find any reference to named groups or an example similar to yours.
> >
> > How about showing us (me?) how to access the named group?
> >
>
> I couldn't find a reference either - also checked 'perlreref' and
> 'perlrequick'.
>
> The OP posted to microsoft.public.dotnet.framework besides
> comp.lang.perl.misc, so did a quick index check of the second edition
> of 'Mastering Regular Expressions'. It states that named capture is
> specific to .NET and Python.
>
They allow you to give a name to your captured text as you're writing your
expression. So, instead of using $1, $2, etc. you could just reference the
captured text by the name you gave it. Not the most useful of additions, in
my opinion.
Matt
------------------------------
Date: Fri, 09 Apr 2004 15:49:53 +1000
From: Gregory Toomey <nospam@bigpond.com>
Subject: Re: WebExplorer as Perl-CGI
Message-Id: <2224115.Gnqc2Pqtg9@GMT-hosting-and-pickle-farming>
Matthias Klein wrote:
> Does anybody know a freeware/opensource Perl-CGI that acts like a regular
> file-explorer?
>
> The internet project I am working on will be hosted on a regular
> shared-hosting environment based on Red Hat Linux 7.3 (no root access, but
> own perl-cgi permitted).
>
> It requires some sort of web-based file-explorer so that users can upload
> and download even large files: the user browses to a certain URL, types in
> his passwd and can then browse in the existing files on the remote host,
> download them and upload new ones. That is what I am hoping for...
>
> Does anybody know a program like this?
>
> Tnx
>
> Matthias
No need for Perl - the basic functionality is built into Apache. If you put
Option +Indexes
into .htaccess in a directory, Apache will allow you to "browse" the
directory & subdirectoires without the need for cgi.
See: http://httpd.apache.org/docs/mod/core.html#options
" If a URL which maps to a directory is requested, and the there is no
DirectoryIndex (e.g., index.html) in that directory, then the server will
return a formatted listing of the directory."
gtoomey
------------------------------
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 6378
***************************************
