[32260] in Perl-Users-Digest
Perl-Users Digest, Issue: 3527 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Oct 25 06:09:28 2011
Date: Tue, 25 Oct 2011 03:09:06 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 25 Oct 2011 Volume: 11 Number: 3527
Today's topics:
Re: Issue with Time::Local <sssdevelop@gmail.com>
Re: Issue with Time::Local <justin.1104@purestblue.com>
Re: Issue with Time::Local <rweikusat@mssgmbh.com>
Re: Net-SMTP on Win32 converts \n to \r\n and destroys <ben@morrow.me.uk>
Re: Net-SMTP on Win32 converts \n to \r\n and destroys <tadmc@seesig.invalid>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
service script <nospam.gravitalsun@hotmail.com.nospam>
Re: service script <john1949@yahoo.com>
Trying to get CGI selection to print <rodbass63@gmail.com>
Re: Trying to get CGI selection to print <ben@morrow.me.uk>
Re: Trying to get CGI selection to print <stevem_@nogood.com>
Re: Trying to get CGI selection to print <tadmc@seesig.invalid>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Sun, 23 Oct 2011 22:14:48 -0700 (PDT)
From: SSS Develop <sssdevelop@gmail.com>
Subject: Re: Issue with Time::Local
Message-Id: <e16144bc-58d9-4fd3-b714-3f06f9e8d211@q13g2000vbd.googlegroups.com>
On Oct 23, 10:54=A0am, "John W. Krahn" <jwkr...@example.com> wrote:
> SSS Develop wrote:
>
> > When i run the following script, I get error:
>
> > Day '31' out of range 1..28 at exp.pl line 18
>
> perldoc -f localtime
>
> =A0 =A0 =A0localtime EXPR
> =A0 =A0 =A0localtime
> =A0 =A0 =A0 =A0 =A0 =A0 =A0Converts a time as returned by the time functi=
on to a
> =A0 =A0 =A0 =A0 =A0 =A0 =A09-element list with the time analyzed for the =
local time
> =A0 =A0 =A0 =A0 =A0 =A0 =A0zone. =A0Typically used as follows:
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# =A00 =A0 =A01 =A0 =A02 =A0 =A0 3 =A0=
=A0 4 =A0 =A05 =A0 =A0 6 =A0 =A0 7 =A0 =A0 8
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0($sec,$min,$hour,$mday,$mon,$year,$wda=
y,$yday,$isdst) =3D
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0localtime(time);
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0All list elements are numeric, and come straig=
ht out of the
> =A0 =A0 =A0 =A0 =A0 =A0 =A0C `struct tm'. =A0$sec, $min, and $hour are th=
e seconds,
> =A0 =A0 =A0 =A0 =A0 =A0 =A0minutes, and hours of the specified time.
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0$mday is the day of the month, and $mon is the=
month
> =A0 =A0 =A0 =A0 =A0 =A0 =A0itself, in the range 0..11 with 0 indicating J=
anuary and 11
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^=
^^^^^^^^^^^^^^^^^^^^^
> =A0 =A0 =A0 =A0 =A0 =A0 =A0indicating December. =A0This makes it easy to =
get a month
> =A0 =A0 =A0 =A0 =A0 =A0 =A0^^^^^^^^^^^^^^^^^^^
> =A0 =A0 =A0 =A0 =A0 =A0 =A0name from a list:
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0my @abbr =3D qw( Jan Feb Mar Apr May J=
un Jul Aug Sep Oct
> Nov Dec );
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0print "$abbr[$mon] $mday";
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0# $mon=3D9, $mday=3D18 gives "Oct 18"
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0$year is the number of years since 1900, not j=
ust the last
> =A0 =A0 =A0 =A0 =A0 =A0 =A0^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> =A0 =A0 =A0 =A0 =A0 =A0 =A0two digits of the year. =A0That is, $year is 1=
23 in year
> =A0 =A0 =A0 =A0 =A0 =A0 =A02023. =A0The proper way to get a complete 4-di=
git year is
> =A0 =A0 =A0 =A0 =A0 =A0 =A0simply:
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0$year +=3D 1900;
>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0Otherwise you create non-Y2K-compliant program=
s--and you
> =A0 =A0 =A0 =A0 =A0 =A0 =A0wouldn't want to do that, would you?
>
> > use strict;
> > use warnings;
> > use Time::Local;
>
> > my $date_string =A0=3D '2011-01-31 17:30:55';
> > my ($date, $time) =3D split /\s+/, $string;
>
> > my ($y, $m, $d) =3D split /-/, $date;
> > my ($hr, $min, $sec) =3D split /:/, $time;
>
> > print timelocal($sec,$min,$hr,$d,$m,$y);
>
> my ( $y, $m, $d, $hr, $min, $sec ) =3D $date_string =3D~ /\d+/g
>
> print timelocal( $sec, $min, $hr, $d, $m - 1, $y - 1900 );
>
> John
> --
> Any intelligent fool can make things bigger and
> more complex... It takes a touch of genius -
> and a lot of courage to move in the opposite
> direction. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 -- Albert Einstein
Thank you,
this works ! was stupid mistake of not going through the details of
documentation :(
---sssdevelop
------------------------------
Date: Mon, 24 Oct 2011 12:15:54 +0100
From: Justin C <justin.1104@purestblue.com>
Subject: Re: Issue with Time::Local
Message-Id: <a0ufn8-gnt.ln1@zem.masonsmusic.co.uk>
On 2011-10-22, Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>
> The code I requoted above led to a comment 'trying to parse date
> formats yourself is usually a mistake'. But no mistake was made when
> parsing this date. Instead...
<Yawn>
From: rweikusat@mssgmbh.com
Score: -1000
Justin.
--
Justin C, by the sea.
------------------------------
Date: Mon, 24 Oct 2011 13:44:01 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Issue with Time::Local
Message-Id: <87ipne1rvy.fsf@sapphire.mobileactivedefense.com>
Justin C <justin.1104@purestblue.com> writes:
> On 2011-10-22, Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>>
>> The code I requoted above led to a comment 'trying to parse date
>> formats yourself is usually a mistake'. But no mistake was made when
>> parsing this date. Instead...
>
> <Yawn>
>
> From: rweikusat@mssgmbh.com
> Score: -1000
I usually score people down by -9999 because I really don't want to
read nonsense texts from people who are much more interested in
farting loudly in public than discuss language or programming issues.
HTH.
------------------------------
Date: Mon, 24 Oct 2011 14:35:00 -0500
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Net-SMTP on Win32 converts \n to \r\n and destroys PDF attachments etc.
Message-Id: <ls2dnY7n-dV5IDjTnZ2dnUVZ7o2dnZ2d@bt.com>
Quoth andipfaff <andreas.pfaff.wangen@gmail.com>:
>
> You are absolutely right. THIS code works but I use a variable instead
> of pure "application/pdf".
Please don't post code you *haven't* *actually* *run*. It just wastes
everybody's time.
> This variable was define via my $t_type inside an if statement. So it
> was useless outside. After removing "my" the code was working perfect.
> You brought me on the right track!
Oh, no, that's *not* the right way to solve that problem.
I suspected you weren't using strictures. You should put
use warnings;
use strict;
at the top of *every* Perl file, and then go through and fix all the
errors and warnings it gives you. You should do this *now*, before the
problem gets any worse.
If you need to conditionally set a variable, you do it like this:
my $t_type;
if (...) {
$t_type = ...;
}
$msg->attach(Type => $t_type, ...);
though you need to consider what will happen to the ->attach call if the
variable doesn't get set.
Ben
------------------------------
Date: Mon, 24 Oct 2011 17:58:50 -0500
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: Net-SMTP on Win32 converts \n to \r\n and destroys PDF attachments etc.
Message-Id: <slrnjabqbq.atd.tadmc@tadbox.sbcglobal.net>
Ben Morrow <ben@morrow.me.uk> wrote:
> Quoth andipfaff <andreas.pfaff.wangen@gmail.com>:
> I suspected you weren't using strictures. You should put
>
> use warnings;
> use strict;
>
> at the top of *every* Perl file, and then go through and fix all the
> errors and warnings it gives you. You should do this *now*, before the
> problem gets any worse.
I pointed that out to this OP (I assume) in 2003:
http://groups.google.com/groups/search?as_umsgid=slrnbd6o4c.2fq.tadmc%40magna.augustmail.com
Talking to the hand seems to be the order of the day...
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Tue, 25 Oct 2011 02:27:57 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <APmdnQnGIJBg-TvTnZ2dnUVZ5qydnZ2d@giganews.com>
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.9 $)
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.rehabitation.com/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 that they do
know and are being the "bad kind" of Lazy.
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_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 and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Mon, 24 Oct 2011 16:09:03 +0300
From: "George Mpouras" <nospam.gravitalsun@hotmail.com.nospam>
Subject: service script
Message-Id: <j83o0h$191h$1@news.ntua.gr>
https://docs.google.com/leaf?id=0B9k0TvGkT7ZyNDRkYjA0Y2YtNmU4OS00M2ViLWJhZTAtZDRjMGQyMTE5ZTQ4&hl=el
Simple script to make any program you want run as service.
Place it inside /etc/init.d/ with any name you want e.g. MyServiceName
Make it executable. Change its first lines with the correct info.
Give the following command and you are ready to go.
sysv-rc-conf --level 2345 MyServiceName on
------------------------------
Date: Tue, 25 Oct 2011 08:20:18 +0100
From: "John" <john1949@yahoo.com>
Subject: Re: service script
Message-Id: <j85nvb$b65$1@news.albasani.net>
"George Mpouras" <nospam.gravitalsun@hotmail.com.nospam> wrote in message
news:j83o0h$191h$1@news.ntua.gr...
> https://docs.google.com/leaf?id=0B9k0TvGkT7ZyNDRkYjA0Y2YtNmU4OS00M2ViLWJhZTAtZDRjMGQyMTE5ZTQ4&hl=el
>
>
>
> Simple script to make any program you want run as service.
>
> Place it inside /etc/init.d/ with any name you want e.g. MyServiceName
>
> Make it executable. Change its first lines with the correct info.
>
> Give the following command and you are ready to go.
>
> sysv-rc-conf --level 2345 MyServiceName on
>
>
>
>
>
>
Hi
How to get English version? It is all in the Greek language.
Regards
John
------------------------------
Date: Mon, 24 Oct 2011 13:25:53 -0700 (PDT)
From: Nene <rodbass63@gmail.com>
Subject: Trying to get CGI selection to print
Message-Id: <68117e91-71e7-4ccc-95de-631750c1a780@er6g2000vbb.googlegroups.com>
I'm still in the process of learning Perl CGI and OOP for Perl.
I'm trying get what I selected to print to screen but It doesn't. I
want to print $object->getNodes(), br;
#!/usr/bin/perl -w
use strict;
use CGI ':standard';
use Practice;
use Data::Dumper;
my $status;
print "Content-type: text/html\n\n";
print start_html(-title=>'ESP F5 Control',
-bgcolor=>'black',
-text=>'#00FFFF');
print "<h1>DR F5 Control</h1>\n";
print_prompt();
do_work();
print end_html;
sub print_prompt {
print start_form;
print "\n", br;
print popup_menu(
-name=>'Env',
-values=>['abc','cde','efg'],
-linebreak=>'yes');
print "<p><em>Servers</em><br>",
checkbox_group(
-name=>'sequence',
-default=>'',
-linebreak=>'true',
-values=>['10.254.22.66',
'10.254.22.67',
'10.254.22.68',
'10.254.22.69',
'10.254.22.70',
'10.254.22.71',
'10.254.22.72',
'10.254.22.73'],
-labels=>\my %labels,
-attributes=>\my %attributes);
print "<p><em>What action to execute?</em> ";
print "\n", br;
print radio_group(-name=>'status',
-
values=>['enabled','disabled']);
print "\n\n", br;
print "\n", br submit('Action','Submit');
print "\n\n", br;
print endform;
print "<hr>\n";
}
my @n;
sub do_work {
##################################
##################################
my(@values,$key);
print "<h2>Here are the current settings in this
form</h2>";
@values = param('sequence');
chomp(@values);
for my $value (@values) {
my $line = "$value:a";
push(@n, "$line");
}
#####################################
}
my $object = new Practice();
$object->setNodes(@n);
print $object->getNodes(), br;
#####
package Practice;
sub new
{
my $class = shift;
my $self = {};
bless $self, $class;
return $self;
}
sub setEsp {
my ( $self, @esp ) = @_;
$self->{_esp} = \@esp if @esp;
return $self->{_esp};
}
sub getEsp {
my( $self ) = @_;
return @{ $self->{_esp} };
}
sub setStatus {
my ( $self, $status ) = @_;
$self->{_status} = \$status if $status;
return $self->{_status};
}
sub getStatus {
my( $self ) = @_;
return @{ $self->{_status} };
}
sub setNodes {
my ( $self, $nodes ) = @_;
$self->{_nodes} = \@nodes if @nodes;
return $self->{_nodes};
}
sub getNodes {
my( $self ) = @_;
return @{ $self->{_nodes} };
}
1;
~
------------------------------
Date: Mon, 24 Oct 2011 16:13:34 -0500
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Trying to get CGI selection to print
Message-Id: <dI-dnQRK7sljSTjTnZ2dnUVZ8vqdnZ2d@bt.com>
Quoth Nene <rodbass63@gmail.com>:
> I'm still in the process of learning Perl CGI and OOP for Perl.
>
> I'm trying get what I selected to print to screen but It doesn't. I
> want to print $object->getNodes(), br;
>
> #!/usr/bin/perl -w
You want
use warnings;
instead of -w. warnings allows you to turn some warnings off for
sections of your code where you need to, which makes always having
warnings on by default much less irritating.
> use strict;
> use CGI ':standard';
> use Practice;
> use Data::Dumper;
> my $status;
You don't seem to do anything with $status.
>
> print "Content-type: text/html\n\n";
If you indent your code properly it will be much easier to read. If
you're having trouble pasting code into Google Groups you may want to
consider getting a real newsreader instead.
> print start_html(-title=>'ESP F5 Control',
> -bgcolor=>'black',
> -text=>'#00FFFF');
> print "<h1>DR F5 Control</h1>\n";
> print_prompt();
> do_work();
> print end_html;
> sub print_prompt {
<snip>
> -labels=>\my %labels,
> -attributes=>\my %attributes);
You don't appear to do anything with %labels or %attributes, either.
> my @n;
Passing values back from a sub in a (file-scoped) global, like this, is
not good practice. It makes it much harder to see where the values come
from. You want to change the sub to return the list of values, and then
you can make the scope of @n much smaller; something like this:
print_prompt();
my @n = do_work();
my $object = Practice->new();
$object->setNodes(@n);
print $object->getNodes(), br;
end_html;
I would then further go on to say that a sub like do_work which both
prints a heading and returns results to be printed later is trying to do
two different jobs at once, but one step at a time :).
> sub do_work {
> ##################################
> ##################################
If you indented your code properly you wouldn't need these ugly comment
blocks to find your way around the file.
> my(@values,$key);
Assuming you get rid of the file-scoped @n above, you will find this sub
needs its own @n to temporarily hold the results until you can pass them
to return.
<snip>
> }
>
> my $object = new Practice();
> $object->setNodes(@n);
> print $object->getNodes(), br;
Now this is just *really* confusing. Mixing up directly-executed code
and subs like this makes it impossible to see what's going on. You may
have already realised this, but this section of code executes after
you've printed end_html above. Depending on how you're viewing the
result this may mean you end up not seeing it.
I would say, as a general rule, that once your 'main program' gets to be
more than a few lines long you should put it in a sub of its own (I
usually call that sub 'main', since I came to Perl from C) and make the
'main program' just consist of a call to that sub.
> #####
> package Practice;
Is this module in its own file? You may not have realised this yet, but
'strict' and 'warnings' only apply to the file they're used in. If you
start a new file you need to
use strict;
use warnings;
at the top all over again.
If you add them to this module, Perl will tell you where your mistake
is.
Ben
------------------------------
Date: Mon, 24 Oct 2011 14:13:59 -0700
From: Steve May <stevem_@nogood.com>
Subject: Re: Trying to get CGI selection to print
Message-Id: <6Akpq.7$0s1.6@newsfe11.iad>
On 10/24/2011 01:25 PM, Nene wrote:
> I'm still in the process of learning Perl CGI and OOP for Perl.
>
> I'm trying get what I selected to print to screen but It doesn't. I
> want to print $object->getNodes(), br;
>
>
> sub setNodes {
> my ( $self, $nodes ) = @_;
> $self->{_nodes} = \@nodes if @nodes;
> return $self->{_nodes};
> }
>
Methinks $nodes is not the same thing as @nodes above...
\s
------------------------------
Date: Mon, 24 Oct 2011 17:43:11 -0500
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: Trying to get CGI selection to print
Message-Id: <slrnjabpef.atd.tadmc@tadbox.sbcglobal.net>
Ben Morrow <ben@morrow.me.uk> wrote:
> Quoth Nene <rodbass63@gmail.com>:
>> I'm still in the process of learning
It will go much faster if you can manage to apply the
suggestions that are given to you.
If you don't understand why a suggested change is better, then ask.
>> Perl CGI and OOP for Perl.
>> #!/usr/bin/perl -w
>
> You want
>
> use warnings;
>
> instead of -w. warnings allows you to turn some warnings off for
> sections of your code where you need to, which makes always having
> warnings on by default much less irritating.
I pointed that out to this OP in December 2008.
[wherein someone also suggested indenting properly]
Sometimes you get the feeling that you are talking to the hand...
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
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:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#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 V11 Issue 3527
***************************************
