[30167] in Perl-Users-Digest
Perl-Users Digest, Issue: 1410 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Apr 1 03:09:42 2008
Date: Tue, 1 Apr 2008 00: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, 1 Apr 2008 Volume: 11 Number: 1410
Today's topics:
Re: empty variables - getting rid of "uninitialized val <szrRE@szromanMO.comVE>
Re: every combination of Y/N in 5 positions joemacbusiness@yahoo.com
Re: every combination of Y/N in 5 positions <uri@stemsystems.com>
glade whit multiple windows <sputacatarro@gmail.com>
new CPAN modules on Tue Apr 1 2008 (Randal Schwartz)
Re: Parse x.500 DN and change order displayed <uri@stemsystems.com>
Re: Parse x.500 DN and change order displayed dummy@phony.info
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Returning a dataset with arrays <jqmicro@gmail.com>
Re: Returning a dataset with arrays <tadmc@seesig.invalid>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 31 Mar 2008 16:24:41 -0700
From: "szr" <szrRE@szromanMO.comVE>
Subject: Re: empty variables - getting rid of "uninitialized value" warnings?
Message-Id: <fsrrrq01hd9@news2.newsguy.com>
Frank Seitz wrote:
> szr wrote:
>> Gunnar Hjalmarsson wrote:
>>>
>>> use warnings;
>>> @execargs = undef;
>
> Better:
> @execargs = (undef);
Yes. The effect is the same, but this makes it clearer. Why someone
would do this in practice is another question entirely, though.
>>> if (exists $execargs[0] && $execargs[0] ne '') {
>>> # ...
>>> }
>>>
>>> C:\home>perl test.pl
>>> Use of uninitialized value $execargs[0] in string ne at test.pl line
>>> 3.
>>
>> I ran the same test and got the same result.
>>
>> Removing the " && $execargs[0] ne '' " portion prevented the error.
>
> Yes, because this test produces the warning.
Yes I now understand why it was coming out that way, thanks.
>> This works too:
>>
>> if (exists $execargs[0] && !!$execargs[0]) {
>>
>> (Tested in 5.10.0, 5.8.8, and 5.6.1)
>>
>> So I wonder, since " exists $execargs[0] " fails,
>
> No, "exists $execargs[0]" succeeds, because there is an element 0.
Oh, yeah, because of the assingment of C<undef> to the array. My brain,
for whatever reason, translated that into C<@execargs = ()> as if it was
the same.
Thanks.
--
szr
------------------------------
Date: Mon, 31 Mar 2008 15:21:22 -0700 (PDT)
From: joemacbusiness@yahoo.com
Subject: Re: every combination of Y/N in 5 positions
Message-Id: <58afb7c3-dc87-4910-b155-036ec809324e@p25g2000hsf.googlegroups.com>
On Mar 31, 2:36=A0pm, J=FCrgen Exner <jurge...@hotmail.com> wrote:
> joemacbusin...@yahoo.com wrote:
> >This has probably already been written but I did not see it on CPAN.
> >Is there a code snippent that can print every possible combination
> >of Y/N's in a 5 position array or string?
>
> I am sure it has been written many times. Search for permutation with
> repetitions.
>
> However, just for the fun of it, here's yet another implementation:
>
> for (0..2**5-1) {
> =A0 =A0 $_ =3D sprintf "%05b", $_;
> =A0 =A0 s/0/N/g;
> =A0 =A0 s/1/Y/g;
> =A0 =A0 print "$_\n";
>
>
>
> }- Hide quoted text -
>
> - Show quoted text -
Hi All,
Got it!
Seriously - this was not an HW assignment. I want exception
reports for a report similar to the following:
Project Loc1 Loc2 Loc3 Loc4 Loc5
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
prod_1 Y Y Y Y Y
prod_2 Y Y N N N
prod_3 Y Y N N N
prod_4 Y Y Y Y Y
prod_5 Y Y Y Y Y
prod_6 Y Y Y Y Y
=2E..
stuff deleted.
So .... show all YYYYN's YNYNY's etc....
Very helpful, thanks again!
--JoeMac
------------------------------
Date: Mon, 31 Mar 2008 22:28:49 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: every combination of Y/N in 5 positions
Message-Id: <x763v2y1cu.fsf@mail.sysarch.com>
>>>>> "GH" == Gunnar Hjalmarsson <noreply@gunnar.cc> writes:
GH> smallpond wrote:
>> On Mar 31, 4:57 pm, joemacbusin...@yahoo.com wrote:
>>> Hi All,
>>>
>>> This has probably already been written but I did not see it on CPAN.
>>> Is there a code snippent that can print every possible combination
>>> of Y/N's in a 5 position array or string?
>>>
>>> For example: Y Y Y Y Y becomes
>>> N Y Y Y Y
>>> Y N Y Y Y....
>>> Y Y N N Y etc.
>>>
>> Who gets the credit for doing your homework?
GH> I do, I hope. :)
GH> foreach my $num ( 0 .. 0b11111 ) {
GH> local *_ = \ sprintf '%05b', $num;
GH> tr/01/NY/;
GH> print "$_\n";
GH> }
ok, now make it a oneliner and golf it! we ain't had a golf thread in
ages!
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Free Perl Training --- http://perlhunter.com/college.html ---------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Mon, 31 Mar 2008 15:13:40 -0700 (PDT)
From: Spocchio <sputacatarro@gmail.com>
Subject: glade whit multiple windows
Message-Id: <250b60cf-ff52-4255-8fdf-06e18cd9a11b@e6g2000prf.googlegroups.com>
hi,
I'm making a glade-based tool: there is a window "father" that have to
open more child windows, here my code:
sub btnNewMessage_onclick
{
my $newWin = Gtk2::GladeXML->new('gui/wSMS.glade');
my $newForm = $newWin->get_widget('wSMS');
$newWin->signal_autoconnect_from_package('callbackSMS');
$newForm->show;
}
package callbackSMS;
my $ID;
sub init #it's on form.show()
{
$ID=rand(0,1000);
}
sub btnOk_clicked
{
print $ID;
}
ok, if I open more than 1 windows, when i click btnOk i get the some
result from all windows.
so when i run the init(), I overwrite the data of the previous window.
What could be the correct method to open more of the some window? i
don't think the package is the best solution.
thanx!
------------------------------
Date: Tue, 1 Apr 2008 04:42:18 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Apr 1 2008
Message-Id: <JyMqEI.y0v@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Algorithm-OpenFST-0.01_03
http://search.cpan.org/~seano/Algorithm-OpenFST-0.01_03/
Perl bindings for the OpenFST library.
----
AnyEvent-Semaphore-0.00_01
http://search.cpan.org/~berle/AnyEvent-Semaphore-0.00_01/
AnyEvent based semaphores
----
Apache2-AuthzHatenaPoint-0.01
http://search.cpan.org/~danjou/Apache2-AuthzHatenaPoint-0.01/
a module to authorize http clients with hatena point.
----
CGI-Application-Plugin-Thumbnail-1.03
http://search.cpan.org/~leocharre/CGI-Application-Plugin-Thumbnail-1.03/
have a runmode that makes thumbnails
----
Crypt-CBC-2.28
http://search.cpan.org/~lds/Crypt-CBC-2.28/
Encrypt Data with Cipher Block Chaining Mode
----
Cwd-Ext-1.05
http://search.cpan.org/~leocharre/Cwd-Ext-1.05/
no symlink dereference
----
DBIx-AnyEvent-0.00_05
http://search.cpan.org/~berle/DBIx-AnyEvent-0.00_05/
AnyEvent wrapped DBI
----
Devel-StackTrace-1.18
http://search.cpan.org/~drolsky/Devel-StackTrace-1.18/
Stack trace and stack trace frame objects
----
File-Binary-1.6
http://search.cpan.org/~simonw/File-Binary-1.6/
Binary file reading module
----
Filesys-SamFS-0.1
http://search.cpan.org/~lupe/Filesys-SamFS-0.1/
Perl extension mapping the SamFS API to Perl
----
FindBin-libs-1.37
http://search.cpan.org/~lembark/FindBin-libs-1.37/
Locate and 'use lib' directories along the path of $FindBin::Bin to automate locating modules. Uses File::Spec and Cwd's abs_path to accomodate multiple O/S and redundant symlinks.
----
Games-Sudoku-CPSearch-0.05
http://search.cpan.org/~martyloo/Games-Sudoku-CPSearch-0.05/
Solve Sudoku problems quickly.
----
Games-Sudoku-CPSearch-0.06
http://search.cpan.org/~martyloo/Games-Sudoku-CPSearch-0.06/
Solve Sudoku problems quickly.
----
Geo-Point-0.08
http://search.cpan.org/~markov/Geo-Point-0.08/
a point on the globe
----
Getopt-Param-Tiny-0.1
http://search.cpan.org/~dmuey/Getopt-Param-Tiny-0.1/
Subset of Getopt::Param functionality with smaller memory footprint
----
Getopt-Param-Tiny-0.2
http://search.cpan.org/~dmuey/Getopt-Param-Tiny-0.2/
Subset of Getopt::Param functionality with smaller memory footprint
----
Getopt-Param-Tiny-0.3
http://search.cpan.org/~dmuey/Getopt-Param-Tiny-0.3/
Subset of Getopt::Param functionality with smaller memory footprint
----
HTML-WebDAO-0.85
http://search.cpan.org/~zag/HTML-WebDAO-0.85/
Perl extension for create complex web application
----
Image-Magick-NFPADiamond-1.00
http://search.cpan.org/~estrelow/Image-Magick-NFPADiamond-1.00/
This module renders a NFPA diamond using ImageMagick
----
Lingua-Translit-0.08
http://search.cpan.org/~alinke/Lingua-Translit-0.08/
transliterates text between writing systems
----
Mac-Pasteboard-0.002
http://search.cpan.org/~wyant/Mac-Pasteboard-0.002/
Manipulate Mac OS X clipboards/pasteboards.
----
Math-Expression-Evaluator-0.0.5
http://search.cpan.org/~moritz/Math-Expression-Evaluator-0.0.5/
parses, compiles and evaluates mathematic expressions
----
Module-Build-IkiWiki-0.0.2
http://search.cpan.org/~vmoral/Module-Build-IkiWiki-0.0.2/
Add to develop Ikiwiki plugins
----
Module-Build-IkiWiki-0.0.3
http://search.cpan.org/~vmoral/Module-Build-IkiWiki-0.0.3/
Extension for develop Ikiwiki plugins
----
Module-Build-IkiWiki-0.0.4
http://search.cpan.org/~vmoral/Module-Build-IkiWiki-0.0.4/
Extension for develop Ikiwiki plugins
----
Module-Build-JSAN-0.03
http://search.cpan.org/~dwheeler/Module-Build-JSAN-0.03/
Build JavaScript distributions for JSAN
----
Net-Partty-0.03
http://search.cpan.org/~yappo/Net-Partty-0.03/
Partty.org! interface
----
Object-Exercise-1.13
http://search.cpan.org/~lembark/Object-Exercise-1.13/
Generic execution & benchmark harness for method calls.
----
POE-Component-Client-NRPE-0.08
http://search.cpan.org/~bingos/POE-Component-Client-NRPE-0.08/
a POE Component that implements check_nrpe functionality
----
POE-Component-Client-NSCA-0.08
http://search.cpan.org/~bingos/POE-Component-Client-NSCA-0.08/
a POE Component that implements send_nsca functionality
----
POE-Component-Client-Pastebot-1.02
http://search.cpan.org/~bingos/POE-Component-Client-Pastebot-1.02/
Interact with Bot::Pastebot web services from POE.
----
RPC-Serialized-0.0605
http://search.cpan.org/~oliver/RPC-Serialized-0.0605/
Subroutine calls over the network using common serialization
----
RT-Authen-ExternalAuth-0.03
http://search.cpan.org/~zordrak/RT-Authen-ExternalAuth-0.03/
RT Authentication using External Sources
----
Rose-DBx-Object-Renderer-0.01
http://search.cpan.org/~danny/Rose-DBx-Object-Renderer-0.01/
Web UI Rendering for Rose::DB::Object
----
Rose-DBx-Object-Renderer-0.02
http://search.cpan.org/~danny/Rose-DBx-Object-Renderer-0.02/
Web UI Rendering for Rose::DB::Object
----
Rose-HTMLx-Form-Field-Boolean-0.03
http://search.cpan.org/~karman/Rose-HTMLx-Form-Field-Boolean-0.03/
extend RHTMLO RadioButtonGroup
----
Text-MicroMason-SafeServerPages-0.02
http://search.cpan.org/~satoh/Text-MicroMason-SafeServerPages-0.02/
Safety ServerPages syntax
----
Text-Printf-1.02
http://search.cpan.org/~roode/Text-Printf-1.02/
A simple, lightweight text fill-in class.
----
Time-Format-1.07
http://search.cpan.org/~roode/Time-Format-1.07/
Easy-to-use date/time formatting.
----
Unix-PID-Tiny-0.1
http://search.cpan.org/~dmuey/Unix-PID-Tiny-0.1/
Subset of Unix::PID functionality with smaller memory footprint
----
Unix-PID-Tiny-0.2
http://search.cpan.org/~dmuey/Unix-PID-Tiny-0.2/
Subset of Unix::PID functionality with smaller memory footprint
----
Verby-0.05
http://search.cpan.org/~nuffin/Verby-0.05/
A framework for compositing and sequencing steps of execution.
----
Verby-Action-Untar-0.04
http://search.cpan.org/~nuffin/Verby-Action-Untar-0.04/
Action to un-tar an archive.
----
WWW-Search-Yahoo-Japan-2.1
http://search.cpan.org/~mthurn/WWW-Search-Yahoo-Japan-2.1/
class for searching Yahoo! Japan
----
XML-Flow-0.85
http://search.cpan.org/~zag/XML-Flow-0.85/
Store (restore) perl data structures in XML stream.
----
XML-OverHTTP-0.08
http://search.cpan.org/~kawasaki/XML-OverHTTP-0.08/
A base class for XML over HTTP-styled web service interface
----
bitflag-0.01
http://search.cpan.org/~schoejo/bitflag-0.01/
Simplify export of bitflag names
----
bitflag-ct-0.01
http://search.cpan.org/~schoejo/bitflag-ct-0.01/
= bitflag + grouping
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: Mon, 31 Mar 2008 22:26:29 GMT
From: Uri Guttman <uri@stemsystems.com>
Subject: Re: Parse x.500 DN and change order displayed
Message-Id: <x7abkey1gr.fsf@mail.sysarch.com>
>>>>> "d" == dummy <dummy@phony.info> writes:
d> On Mon, 31 Mar 2008 04:09:07 GMT, Uri Guttman <uri@stemsystems.com>
d> wrote:
>>>>>>> "S" == SecureIT <gotsecure@gmail.com> writes:
>>
S> I am trying to change this
S> "cn=Bob Smith+serialNumber=CR013120080827,o=ICM,c=US"
>>
S> to this:
>>
S> "serialNumber=CR013120080827+cn=Bob Smith,o=ICM,c=US"
>>
S> There are about 2000 entries like this and I need to have them all
S> displayed with serialNumber first, and cn last then the rest of the
S> DN, the names and serialNumbers are all unique to each entry.
>>
>> are all the entries separated by +? how many are there (you show only 2)?
>>
>> if it is always + then you can just split the lines, grab out the cn one
>> (use grep) and also filter out the rest. then order them as you
>> want. call join '+' to rebuild the line. it can also be done with a hash
>> but that is about the same amount of code.
>>
>> uri
d> Am I missing something? Why can't (or shouldn't) he do this?
d> $entry =~ s/(cn[^+]+)\+([^,]+)(.*)$/$2+$1$3/;
d> Is it less efficient in some way?
that assumes the serial number is in slot 1 ($2) and i wouldn't make
that assumption. the other regex answers match the serial part and not
the cn part like you do. i was thinking about a more flexible solution
which would allow any reordering of many parts and no regex could do
that. hence my idea about split and joining in the desired order.
uri
--
Uri Guttman ------ uri@stemsystems.com -------- http://www.sysarch.com --
----- Perl Code Review , Architecture, Development, Training, Support ------
--------- Free Perl Training --- http://perlhunter.com/college.html ---------
--------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
------------------------------
Date: Mon, 31 Mar 2008 15:48:21 -0700
From: dummy@phony.info
Subject: Re: Parse x.500 DN and change order displayed
Message-Id: <i9q2v3tpk353qbdbqkh1krh2p7jkeitdqm@4ax.com>
On Mon, 31 Mar 2008 22:26:29 GMT, Uri Guttman <uri@stemsystems.com>
wrote:
>>>>>> "d" == dummy <dummy@phony.info> writes:
>
> d> On Mon, 31 Mar 2008 04:09:07 GMT, Uri Guttman <uri@stemsystems.com>
> d> wrote:
>
> >>>>>>> "S" == SecureIT <gotsecure@gmail.com> writes:
> >>
> S> I am trying to change this
> S> "cn=Bob Smith+serialNumber=CR013120080827,o=ICM,c=US"
> >>
> S> to this:
> >>
> S> "serialNumber=CR013120080827+cn=Bob Smith,o=ICM,c=US"
> >>
> S> There are about 2000 entries like this and I need to have them all
> S> displayed with serialNumber first, and cn last then the rest of the
> S> DN, the names and serialNumbers are all unique to each entry.
> >>
> >> are all the entries separated by +? how many are there (you show only 2)?
> >>
> >> if it is always + then you can just split the lines, grab out the cn one
> >> (use grep) and also filter out the rest. then order them as you
> >> want. call join '+' to rebuild the line. it can also be done with a hash
> >> but that is about the same amount of code.
> >>
> >> uri
>
> d> Am I missing something? Why can't (or shouldn't) he do this?
> d> $entry =~ s/(cn[^+]+)\+([^,]+)(.*)$/$2+$1$3/;
>
> d> Is it less efficient in some way?
>
>that assumes the serial number is in slot 1 ($2) and i wouldn't make
>that assumption. the other regex answers match the serial part and not
>the cn part like you do. i was thinking about a more flexible solution
>which would allow any reordering of many parts and no regex could do
>that. hence my idea about split and joining in the desired order.
>
>uri
Thanks. Naive on my part. But it got me pointed at the subject of
X.500 DN, which I think I could use.
------------------------------
Date: Tue, 01 Apr 2008 06:18:10 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <CskIj.8998$Rq1.4285@nlpi068.nbdc.sbc.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.8 $)
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_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 and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Mon, 31 Mar 2008 17:55:23 -0700 (PDT)
From: Macaruchi <jqmicro@gmail.com>
Subject: Returning a dataset with arrays
Message-Id: <91f15f9f-3b82-414a-8253-1722d84bdb92@y21g2000hsf.googlegroups.com>
Hi!
I am a newbie using Perl and I have a big problem , for me, and it is
that I need to return a query result into a array but I cant do that.
I did this code:
sub getcodigodb()
{ local($table)= shift;
local($field)= shift;
my $code=shift;
my $dbh = open_connection();
my $sql = "SELECT * FROM $table WHERE $field=$code ";
my $sth = $dbh->prepare($sql);
$sth->execute or die "Unable to execute SQL query: $dbh->errstr
\n";
my $sth = $dbh->prepare($sql);
$sth->execute or die "Unable to execute SQL query: $dbh->errstr
\n";
$ref = $sth->fetchall_arrayref;
$sth->finish;
$dbh->disconnect;
return $ref;
}
}
$sth->fetchall_arrayref; I use this because I read that I need a perl
structure for moving into it.
This select can return 0,1 or n rows so I suppose $ref has this rows
but I dont know how to access them.
Could be this way :
@rows=&getcodigodb('mytable','myfield',3434); Is it correct?
If it is how can I access the rows. If the query doesnt find records,
what the function return to determine if the dataset exist or not?
I do this but this just print the selection I want return the
selection and manipulate whenever I want because it is in array and I
can use everything functions from array
while (@row = $sth->fetchrow_array)
{ # retrieve one row
print join(", ", @row), "\n";
}
I just want to access the selection like a cursor.
Sorry for inconveniece but I am so confused with this.
Thks in Advance!
------------------------------
Date: Tue, 01 Apr 2008 01:42:28 GMT
From: Tad J McClellan <tadmc@seesig.invalid>
Subject: Re: Returning a dataset with arrays
Message-Id: <slrnfv37ne.ete.tadmc@tadmc30.sbcglobal.net>
Macaruchi <jqmicro@gmail.com> wrote:
> I am a newbie using Perl and I have a big problem , for me, and it is
> that I need to return a query result into a array but I cant do that.
>
> I did this code:
>
> sub getcodigodb()
> { local($table)= shift;
> local($field)= shift;
You should always prefer lexical (my) variables over package (local)
variables, except when you can't.
You can here, so those should be my() rather than local() declarations.
> my $code=shift;
Get all 3 arguments in one go:
my($table, $field, $code) = @_;
> my $dbh = open_connection();
>
> my $sql = "SELECT * FROM $table WHERE $field=$code ";
> my $sth = $dbh->prepare($sql);
> $sth->execute or die "Unable to execute SQL query: $dbh->errstr
> \n";
>
> my $sth = $dbh->prepare($sql);
> $sth->execute or die "Unable to execute SQL query: $dbh->errstr
> \n";
>
> $ref = $sth->fetchall_arrayref;
>
> $sth->finish;
> $dbh->disconnect;
>
> return $ref;
> }
> }
>
> $sth->fetchall_arrayref; I use this because I read that I need a perl
> structure for moving into it.
> This select can return 0,1 or n rows so I suppose $ref has this rows
> but I dont know how to access them.
Read:
perldoc perlreftut
> Could be this way :
> @rows=&getcodigodb('mytable','myfield',3434); Is it correct?
No, that won't work.
Apply "Use Rule 1" from the above documentation.
I like to do it in 3 steps:
1) pretend it is an ordinary array:
@rows = @query_rows;
2) replace the name with a block:
@rows = @{ };
3) put something in the block that returns the right kind of reference:
@rows = @{ getcodigodb('mytable', 'myfield', 3434) };
(do not use an ampersand when calling functions unless you know what
it does, and what it does is what you want to do (it seldom is).
)
> If it is how can I access the rows. If the query doesnt find records,
> what the function return to determine if the dataset exist or not?
warn "no results\n" unless @rows;
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
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 V11 Issue 1410
***************************************
