[28352] in Perl-Users-Digest
Perl-Users Digest, Issue: 9716 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Sep 12 09:05:57 2006
Date: Tue, 12 Sep 2006 06:05:07 -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 Tue, 12 Sep 2006 Volume: 10 Number: 9716
Today's topics:
Re: converting vba to perl without win32::ole <daveandniki@ntlworld.com>
Re: Decode data of different charsets into UTF8 (Perl i <rvtol+news@isolution.nl>
Re: i need to ssh to remote server using Perl vish.chitnis@gmail.com
Re: i need to ssh to remote server using Perl <christoph.lamprecht.no.spam@web.de>
Re: i need to ssh to remote server using Perl <mritty@gmail.com>
Keeping changes to %ENV in Win32 process <eldridge.jeff@gmail.com>
Re: Keeping changes to %ENV in Win32 process <mritty@gmail.com>
Re: Keeping changes to %ENV in Win32 process <eldridge.jeff@gmail.com>
Re: localtime is now wrong after server change anno4000@radom.zrz.tu-berlin.de
Re: localtime is now wrong after server change <zen13097@zen.co.uk>
Re: localtime is now wrong after server change <1usa@llenroc.ude.invalid>
Re: Modifying and printing a string variable <josef.moellers@fujitsu-siemens.com>
Re: Modifying and printing a string variable <kenslaterpa@hotmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
selenium with www::mechanize <nospam@home.com>
Re: variable inheritance <mgarrish@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 12 Sep 2006 09:53:53 +0200
From: "Dave" <daveandniki@ntlworld.com>
Subject: Re: converting vba to perl without win32::ole
Message-Id: <4506679b$0$5086$ba4acef3@news.orange.fr>
> You are probably looking for the \G modifier:
>
> if ($_ =~ /<R [,;)].*<R [,;)].*<R [,;)].*[0-9]+ [0-9]+ [0-9]/) {
> $_ =~ s/\G(\n\+pg,[0-9]+\n)(\+l)/ $2$1/g;
> &Subroutine;
> }
>
> (untested)
>
>
No, please ignore this I misunderstood the /G anchor.
This should work :
if ($_ =~ /<R [,;)].*<R [,;)].*<R [,;)].*[0-9]+ [0-9]+ [0-9]/) {
# Use lookbehind assertion and loop to make global
1 while ($_ =~ s/(?<=<R [,;)].*<R [,;)].*<R [,;)].*[0-9]+ [0-9]+
[0-9].*)(\n\+pg,[0-9]+\n)(\+l)/ $2$1/;)
&Subroutine;
}
(untested)
You might get away with the /g modifier rather than the while loop - try it
and see. I can't quite work out all the consequences of the multiple .* in
the look-behind assertion on the behavior of /g, although it might be OK. If
it is slow there may be ways to optimise it (using .*? may help).
------------------------------
Date: Tue, 12 Sep 2006 13:09:35 +0200
From: "Dr.Ruud" <rvtol+news@isolution.nl>
Subject: Re: Decode data of different charsets into UTF8 (Perl internal format)
Message-Id: <ee6bt3.q4.1@news.isolution.nl>
Peter J. Holzer schreef:
> iso-8859-1 and cp437 are easy as the ranges for accented characters
> overlap very little. In fact the range where most accented characters
> are in cp437 isn't even defined in iso-8859-1, so if you find a
> character in this range it can't be iso-8859-1 (but it might be
> win-1252).
The character map "ISO_8859-1:1987", more commonly known by its
preferred MIME name of "ISO-8859-1" (note the extra hyphen over "ISO
8859-1"), has both the ranges 00-1F and 80-9F defined.
ISO-8859-1 is also incorporated as the first 256 code points of Unicode.
--
Affijn, Ruud
"Gewoon is een tijger."
------------------------------
Date: 12 Sep 2006 01:43:09 -0700
From: vish.chitnis@gmail.com
Subject: Re: i need to ssh to remote server using Perl
Message-Id: <1158050589.013317.169420@h48g2000cwc.googlegroups.com>
hi paul,
i get this error when i try to install the Net::SSH::Perl package.. wht
else i need to do in order to install this package successfully
vish
nmake -- NOT OK
unning make test
Can't test without successful make
unning make install
make had returned bad status, install seems impossible
Paul Lalli wrote:
> vish.chit...@gmail.com wrote:
> > hi Binod
> > thanks for ur quick reply, i have verified that and found that the flie
> > ssh.pm does exist in the proper location..
>
> URI::ssh has *nothing* to do with Net::SSH::Perl.
>
> > still i have to install the package?
>
> Yes.
>
> > if yes wht is the package name shall i give
>
> The package you're trying to use is the package you need to install.
> Net::SSH::Perl
>
> Paul Lalli
------------------------------
Date: Tue, 12 Sep 2006 11:40:44 +0200
From: Ch Lamprecht <christoph.lamprecht.no.spam@web.de>
Subject: Re: i need to ssh to remote server using Perl
Message-Id: <ee5var$gov$1@online.de>
vish.chitnis@gmail.com wrote:
> hi paul,
>
> i get this error when i try to install the Net::SSH::Perl package.. wht
> else i need to do in order to install this package successfully
>
> vish
>
> nmake -- NOT OK
> unning make test
> Can't test without successful make
> unning make install
> make had returned bad status, install seems impossible
>
Why don't you use ppm to install the package:
ppm
i net-ssh-perl
HTH, Christoph
--
perl -e "print scalar reverse q/ed.enilno@ergn.l.hc/"
------------------------------
Date: 12 Sep 2006 03:12:44 -0700
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: i need to ssh to remote server using Perl
Message-Id: <1158055964.234165.257950@m73g2000cwd.googlegroups.com>
vish.chitnis@gmail.com wrote:
> i get this error when i try to install the Net::SSH::Perl package.. wht
> else i need to do in order to install this package successfully
> nmake -- NOT OK
> unning make test
> Can't test without successful make
> unning make install
> make had returned bad status, install seems impossible
Please stop top-posting. Post your replies BELOW what you are replying
to. Thank you.
First, I don't believe for a second that's the FULL error message.
What happened before the "NOT OK"?
Second, have you tried installing the package through ActiveState's
Perl Package Manager (ppm)? That's generally far easier for Windows
module installations.
Paul Lalli
------------------------------
Date: 12 Sep 2006 02:43:31 -0700
From: "jeffeld" <eldridge.jeff@gmail.com>
Subject: Keeping changes to %ENV in Win32 process
Message-Id: <1158054211.501290.53730@e3g2000cwe.googlegroups.com>
Hi,
I have a couple of scripts where I want to keep changes made to the
process environment variables after the perl script ends.
e.g.
In jeff.pl
$ENV{JEFF}="FOO";
and then in a Win32 .cmd file
perl jeff.pl
echo %JEFF%
Is this possible? If not, what would be a better way to return a simple
status to the command shell for processing after the script has ended.
Thanks,
Jeff
------------------------------
Date: 12 Sep 2006 03:36:28 -0700
From: "Paul Lalli" <mritty@gmail.com>
Subject: Re: Keeping changes to %ENV in Win32 process
Message-Id: <1158057388.528445.77210@b28g2000cwb.googlegroups.com>
jeffeld wrote:
> I have a couple of scripts where I want to keep changes made to the
> process environment variables after the perl script ends.
Please check the Perl FAQ *before* posting!!
perldoc -q environment
> Is this possible? If not, what would be a better way to return a simple
> status to the command shell for processing after the script has ended.
Why aren't you just using the exit status from your program?
perldoc -f exit
Paul Lalli
------------------------------
Date: 12 Sep 2006 05:23:53 -0700
From: "jeffeld" <eldridge.jeff@gmail.com>
Subject: Re: Keeping changes to %ENV in Win32 process
Message-Id: <1158063833.427297.280590@p79g2000cwp.googlegroups.com>
Paul Lalli wrote:
> jeffeld wrote:
> > I have a couple of scripts where I want to keep changes made to the
> > process environment variables after the perl script ends.
>
<Snip> perldoc -f exit
>
> Paul Lalli
Excellent. Thank you.
And I'm off to read the FAQ now.
Cheers,
Jeff
------------------------------
Date: 12 Sep 2006 09:57:06 GMT
From: anno4000@radom.zrz.tu-berlin.de
Subject: Re: localtime is now wrong after server change
Message-Id: <4mnejiF6qk7hU1@news.dfncis.de>
Jason <jwcarlton@gmail.com> wrote in comp.lang.perl.misc:
> Regarding the first two replies... I appreciate the help, but when did
> everyone on this NG get to be so rude? Wow.
>
> Anyone remember how we used to all be helpful and sharing, proclaiming
> that the internet (and Perl) was designed for the free exchange of
> ideas and information?
"We" used to be helpful?
You have never once given help to anyone on CLPM. Considering your
coding skills that is a good thing.
[...]
> > Here. you are adding one hour to the current time.
>
> Thanks, and of course you're correct. I wrote that little bit of code
> more than 8 years ago and have never needed to modify it, so it just
> makes sense that I forgot why I did that.
You didn't write that code, you cribbed it from somewhere. This
crap is all over the net, almost literally. Don't try to pass off
(bad) folklore as your own work.
> To answer the question of
> "why didn't I change the time on the server," it's because (as I
> mentioned in the original post) I was using a remote host, and didn't
> have the ability to change their time zone.
Of course you can't change the server's time. It's a good thing
you can't because that would be the wrongest thing to do. You can
however change the time zone your program uses and that's what you
should have done. You don't need privileges for that.
[...]
> > Because you are adding one hour to the current time. How hard is that to
> > figure out?
>
> While working on old code, after having been awake for more than 48
> hours... very hard!
So you were too exhausted to keep a clear thought in your head, but
decided that was a good time to ask questions on Usenet? Thank you
very much for your consideration.
> Be fair; if you weren't familiar with the logic,
> what would make you think that 60*60 was equivalent to an hour?
Ah, but we all are familiar with the logic of "your" code. Is that
what you're saying?
You have entered the category of just another KLB.
Anno
------------------------------
Date: 12 Sep 2006 11:08:07 GMT
From: Dave Weaver <zen13097@zen.co.uk>
Subject: Re: localtime is now wrong after server change
Message-Id: <45069517$0$1385$da0feed9@news.zen.co.uk>
On Mon, 11 Sep 2006 21:47:10 +1200, Tintin <tintin@invalid.invalid> wrote:
> Replace the entire awful code above with
>
> use POSIX 'strftime';
> my $thistimestamp = "%Y%m%d%H%M%S",localtime;
>
> Much easier on the eye.
But, surprisingly, not so useful.
ITYM:
my $thistimestamp = strftime "%Y%m%d%H%M%S",localtime;
^^^^^^^^
------------------------------
Date: Tue, 12 Sep 2006 11:10:53 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: localtime is now wrong after server change
Message-Id: <Xns983C490E19CC0asu1cornelledu@24.24.2.167>
"Jason" <jwcarlton@gmail.com> wrote in news:1158029547.380968.166590
@e63g2000cwd.googlegroups.com:
[ Relevant attributions an quotes were snipped by the OP. Reinserted. ]
> "A. Sinan Unur" <1usa@llenroc.ude.invalid> wrote in
> news:Xns983A776F879DBasu1cornelledu@127.0.0.1:
>
>> "Jason" <jwcarlton@gmail.com> wrote in news:1157899110.648602.211210
>> @b28g2000cwb.googlegroups.com:
>>
>>> Until recently, my site was on a remote-hosted shared server; as of
>>> today, I've completely upgraded to a dedicated.
>>>
>>> I use to use the following to determine the timestamp for my forum:
>>>
>>> ($sec, $min, $hour, $day, $mon, $year, $wday) = (localtime(time +
>>> (60*60)))[0,1,2,3,4,5,6];
>>
>> Here. you are adding one hour to the current time.
...
> Be fair; if you weren't familiar with the logic,
> what would make you think that 60*60 was equivalent to an hour?
Every Perl programmer ought to know or ought to be able to look up the
fact that time returns seconds since the epoch.
Every human being ought to know that there are 60 seconds in every
minute and 60 minutes in every hour. Therefore, 60*60 represents an hour
in seconds.
You are adding an hour to the current time.
It is natural to assume that someone posting in programming newsgroup is
familiar with logical reasoning. If not, programming is not for you.
Bye.
Sinan
------------------------------
Date: Tue, 12 Sep 2006 09:59:08 +0200
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: Modifying and printing a string variable
Message-Id: <ee5pgd$anr$1@nntp.fujitsu-siemens.com>
JC wrote:
> I have a hash, with key bodybgcolor pointing to a hexadecimal color
> string "#FF9966". Problem is, I'm not allowed to pring the "#" sign, so=
> I need to print "FEDCBA". How do I do that?
>=20
What have you tried and where did it fail to meet your expectations?
As it is a veeeery simple problem with numerous possible solutions (a=20
truly TMTOWTDI):
my $string =3D '#FF9966';
my $result1 =3D substr($string, 1);
my $result2; ($string2 =3D $string) =3D~ s/^#//;
my $result3; ($string3 =3D $string) =3D~ tr/^#//d;
Pick your choice.
However, as your original string is "#FF9966" and your resulting string=20
has absolutely no connection with the original string (apart from some=20
length and character set considerations):
$result =3D 'FEDCBA';
Josef
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: 12 Sep 2006 04:45:21 -0700
From: "kens" <kenslaterpa@hotmail.com>
Subject: Re: Modifying and printing a string variable
Message-Id: <1158061521.794155.184860@d34g2000cwd.googlegroups.com>
Josef Moellers wrote:
> JC wrote:
> > I have a hash, with key bodybgcolor pointing to a hexadecimal color
> > string "#FF9966". Problem is, I'm not allowed to pring the "#" sign, so
> > I need to print "FEDCBA". How do I do that?
> >
>
> What have you tried and where did it fail to meet your expectations?
>
> As it is a veeeery simple problem with numerous possible solutions (a
> truly TMTOWTDI):
>
> my $string =3D '#FF9966';
>
> my $result1 =3D substr($string, 1);
> my $result2; ($string2 =3D $string) =3D~ s/^#//;
> my $result3; ($string3 =3D $string) =3D~ tr/^#//d;
>
I assume you meant:
my $result2; ($result2 =3D $string) =3D~ s/^#//;
my $result3; ($result3 =3D $string) =3D~ tr/^#//d;
> ...
>
> Josef
> --
> Josef M=F6llers (Pinguinpfleger bei FSC)
> If failure had no penalty success would not be a prize
> -- T. Pratchett
------------------------------
Date: 12 Sep 2006 07:22:07 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.6 $)
Message-Id: <4506601e$0$47253$ae4e5890@news.nationwide.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.6 $)
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://www.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: Tue, 12 Sep 2006 10:52:46 GMT
From: "Nospam" <nospam@home.com>
Subject: selenium with www::mechanize
Message-Id: <2kwNg.19774$7D6.9802@newsfe2-win.ntli.net>
Does anyone have a sample script of the use of selenium with www::mechanize
to handle javascript buttons?
------------------------------
Date: 12 Sep 2006 03:56:52 -0700
From: "Matt Garrish" <mgarrish@gmail.com>
Subject: Re: variable inheritance
Message-Id: <1158058612.530291.276400@i42g2000cwa.googlegroups.com>
attn.steven.kuo@gmail.com wrote:
> Matt Garrish wrote:
> > I'm faced with the problem of one module serving up data for 10
> > different applications, where the only difference is the data being
> > generated. Without going into the gory details, each year the data
> > structure (the database) can change for each application and the
> > applications have no relation to each other.
> >
> > For this reason, I've set up 10 separate modules each defining the same
> > set of variables so that my generic class can access the configuration
> > information without needing to know which application it is dealing
> > with. Some of the data is the same between applications, so I keep that
> > in the base class and then the subclasses override the variables that
> > are specific to each of the children. As I'm sure the above must sound
> > like gibberish, take for example:
> >
> > ### DataBase.pm
> >
> > package DataBase;
> >
> > use Exporter;
> > @ISA = qw/Exporter/;
> > @EXPORT = qw/%appInfo %someOtherConfig/;
> >
> > # this variable will get overriden by the child module
> > # but declaring it here means I can use it in the
> > # module and avoid problems with strictures
> > # not finding the variable before the child require
> > our %appInfo;
> >
> > our %someOtherConfig = (test => 1);
> >
>
>
> I don't see how the %appInfo has in this package
> gets over-writtten.
>
>
> > ### Child1.pm
> >
> > package DataBase::Child1;
> >
> > use base 'DataBase';
> >
> > use Exporter;
> > @ISA = qw/Exporter/;
> > @EXPORT = qw/%appInfo/;
> >
> > our %appInfo = (table1 => 'col1, col2, col3');
> >
> >
> > ### application
> >
> > use strict;
> > use warnings;
> >
> > use DataBase;
> >
> > my $test = 1;
> >
> > if ($test == 1) {
> > require DataBase::Child1;
> > import DataBase::Child1;
> > }
> >
> > print keys %appInfo;
> >
> >
> > #########
> >
> > The above will print the correct 'table1' key, but my question is am I
> > setting myself up for disaster if I actually try and go this route? I'm
> > not saying it's the most elegant code, but since it's not a true object
> > that I want but more of a configuration file is there any danger in my
> > assumption that the require will properly result in the %appInfo being
> > the child version.
>
>
> Well, it's confusing to say the least. Are you expecting the %appInfo
> in package DataBase to contain the same information as the %appInfo
> in package main?
>
> With a bit of code added for debugging and introspection, you'll see
> that they aren't the same:
>
> Importing into main from DataBase::Child1: %appInfo at app.pl line 10
>
> $VAR1 = {
> 'table1' => 'col1, col2, col3'
> };
> $VAR1 = {};
> $VAR1 = [
> 'Exporter'
> ];
>
>
> Note that the %appInfo hash in DataBase remains empty.
> Also note that the @ISA array in DataBase::Child1 only contains
> exporter -- it's not a derived class of DataBase; you've wiped
> out the inheritance by reassigning to @ISA.
>
Sorry, I haven't actually rewritten the code, so you're right that my
hasty example probably doesn't make a whole lot of sense (I'm just
thinking of ways around the problem right now, and "use vars" is
probably the way I should be going so that I only have to export from
the child and still have the code behave under strictures).
The problem in a nutshell is how do I make the variable "exist" in the
eyes of strictures but not know what it contains until the require
happens. I was trying to come up with any trickery I could just in the
interests of seeing what else was possible, but I think I'll just go
back to tried and true.
Matt
------------------------------
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 9716
***************************************
