[30703] in Perl-Users-Digest
Perl-Users Digest, Issue: 1948 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Oct 28 06:09:44 2008
Date: Tue, 28 Oct 2008 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, 28 Oct 2008 Volume: 11 Number: 1948
Today's topics:
Re: dealing with time <jurgenex@hotmail.com>
file redirection paul_0403@yahoo.com
Re: file redirection <joost@zeekat.nl>
Re: How to overwrite or mock -e for testing? <nospam-abuse@ilyaz.org>
implementing getopts when called by functions <gourabbaksi@gmail.com>
new CPAN modules on Tue Oct 28 2008 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
subversion introspection <socyl@987jk.com.invalid>
Re: subversion introspection <john@castleamber.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 27 Oct 2008 14:42:07 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: dealing with time
Message-Id: <o8dcg4h65ha6vtq6co61mg147033numgh4@4ax.com>
Larry <dontmewithme@got.it> wrote:
>In article <h1abg4h6c9el4qjp16ogs7i4uqri0d7ujn@4ax.com>,
> J?rgen Exner <jurgenex@hotmail.com> wrote:
>
>> Chasing a running target is no fun, you know....
>
>yeah, I know. The is that your code MAY show: "X hour X secs" if minutes
>is 0 or it may show "X hour X min" if seconds is 0. Also, it may show "X
>min X secs" if hours is 0 which is OK! How can I get the code show value
>nontheless its 0 value based on the value next to it? "X hour 0 min X
>secs"
How about by modifying the condition for printing that value to match
your ever changing requirements?
I for my part are done with this topic.
jue
------------------------------
Date: Mon, 27 Oct 2008 13:11:36 -0700 (PDT)
From: paul_0403@yahoo.com
Subject: file redirection
Message-Id: <594f9b07-777d-4516-8a82-934608d2e90f@f63g2000hsf.googlegroups.com>
I have a perl program that opens and writes to a logfile, this all
works
well.
ie
if (! open (LOG, ">>$logfile"))
{
print STDERR "Cannot open logfile $logfile $!\n";
exit 1;
}
print LOG "Hello world\n"
I want to redirect the outpuf of a system command ot the same
log but I am having trouble getting it to work.
Can I do something like this? If not, how can I get this to work.
system("kill -USR1 \"$1\" > LOG 2>\&1");
When I issue this command on the command line I get a permissions
problem. When I run it from the perl script I was expecting to see the
same permssion problem in my log file.
THanks to all who answer
------------------------------
Date: Mon, 27 Oct 2008 21:25:26 +0100
From: Joost Diepenmaat <joost@zeekat.nl>
Subject: Re: file redirection
Message-Id: <874p2xlr9l.fsf@zeekat.nl>
paul_0403@yahoo.com writes:
> I have a perl program that opens and writes to a logfile, this all
> works
> well.
>
> ie
>
> if (! open (LOG, ">>$logfile"))
> {
> print STDERR "Cannot open logfile $logfile $!\n";
> exit 1;
> }
>
> print LOG "Hello world\n"
>
> I want to redirect the outpuf of a system command ot the same
> log but I am having trouble getting it to work.
>
> Can I do something like this? If not, how can I get this to work.
> system("kill -USR1 \"$1\" > LOG 2>\&1");
>
> When I issue this command on the command line I get a permissions
> problem. When I run it from the perl script I was expecting to see the
> same permssion problem in my log file.
You really should read the answers given before you re-post your
code in a slightly different (but still misguided) form.
--
Joost Diepenmaat | blog: http://joost.zeekat.nl/ | work: http://zeekat.nl/
------------------------------
Date: Mon, 27 Oct 2008 22:41:53 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: How to overwrite or mock -e for testing?
Message-Id: <ge5g3h$1dra$1@agate.berkeley.edu>
[A complimentary Cc of this posting was sent to
John W. Krahn
<jwkrahn@shaw.ca>], who wrote in article <H_oNk.8750$3w.3461@newsfe19.iad>:
> sub get_foo { my $fh; open $fh, '<', '/etc/foo.conf' and return scalar <$fh> }
This leaves no way for the caller to check for errors.
sub get_foo { my $fh; open $fh, '<', '/etc/foo.conf' or return; scalar <$fh> }
Note the differences,
Ilya
------------------------------
Date: Tue, 28 Oct 2008 01:55:06 -0700 (PDT)
From: Ironhide <gourabbaksi@gmail.com>
Subject: implementing getopts when called by functions
Message-Id: <dabe7a0a-c5bd-403b-b950-46e2c2c91509@w24g2000prd.googlegroups.com>
Hi,
Is it possible to do this in perl?
If yes, please let me know how.
sub A {
IOWorkload -v .. -a ..
}
sub IOWorkload {
..
..
}
_G
------------------------------
Date: Tue, 28 Oct 2008 04:42:23 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Oct 28 2008
Message-Id: <K9FMEn.1Crq@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.
AFS-2.6.0
http://search.cpan.org/~nog/AFS-2.6.0/
Basic functions and variables of the AFS module
----
Acme-CPANAuthors-0.05
http://search.cpan.org/~ishigaki/Acme-CPANAuthors-0.05/
We are CPAN authors
----
Acme-PlayCode-0.06
http://search.cpan.org/~fayland/Acme-PlayCode-0.06/
Play code to win
----
Alien-wxWidgets-0.41
http://search.cpan.org/~mbarbon/Alien-wxWidgets-0.41/
building, finding and using wxWidgets binaries
----
AnyEvent-Mojo-0.4
http://search.cpan.org/~melo/AnyEvent-Mojo-0.4/
Run Mojo apps using AnyEvent framework
----
Apache2-ASP-2.00_10
http://search.cpan.org/~johnd/Apache2-ASP-2.00_10/
ASP for Perl, reloaded.
----
App-Addex-AddressBook-Apple-0.013
http://search.cpan.org/~rjbs/App-Addex-AddressBook-Apple-0.013/
use Apple Address Book as the addex source
----
App-Env-0.15
http://search.cpan.org/~djerius/App-Env-0.15/
manage application specific environments
----
Astro-satpass-0.019
http://search.cpan.org/~wyant/Astro-satpass-0.019/
----
BDB-Wrapper-0.22
http://search.cpan.org/~hikarine/BDB-Wrapper-0.22/
Wrapper module for BerkeleyDB.pm
----
Business-DPD-0.14
http://search.cpan.org/~domm/Business-DPD-0.14/
handle DPD lable generation
----
Business-ISBN-2.04_01
http://search.cpan.org/~bdfoy/Business-ISBN-2.04_01/
work with International Standard Book Numbers
----
CPAN-PackageDetails-0.11_02
http://search.cpan.org/~bdfoy/CPAN-PackageDetails-0.11_02/
Create or read 02.packages.details.txt.gz
----
CPAN-PackageDetails-0.11_03
http://search.cpan.org/~bdfoy/CPAN-PackageDetails-0.11_03/
Create or read 02.packages.details.txt.gz
----
Catalyst-Authentication-Store-DBIx-Class-0.1081
http://search.cpan.org/~jayk/Catalyst-Authentication-Store-DBIx-Class-0.1081/
A storage class for Catalyst Authentication using DBIx::Class
----
Catalyst-Authentication-Store-DBIx-Class-0.1082
http://search.cpan.org/~jayk/Catalyst-Authentication-Store-DBIx-Class-0.1082/
A storage class for Catalyst Authentication using DBIx::Class
----
Catalyst-Plugin-InflateMore-0.1.32
http://search.cpan.org/~pjfl/Catalyst-Plugin-InflateMore-0.1.32/
Inflates symbols in application config
----
Class-DBI-Lite-0.016
http://search.cpan.org/~johnd/Class-DBI-Lite-0.016/
Lightweight ORM for Perl
----
Config-Crontab-1.30
http://search.cpan.org/~scottw/Config-Crontab-1.30/
Read/Write Vixie compatible crontab(5) files
----
Data-Util-0.041
http://search.cpan.org/~gfuji/Data-Util-0.041/
A selection of utilities for data and data types
----
DateTime-TimeZone-0.83
http://search.cpan.org/~drolsky/DateTime-TimeZone-0.83/
Time zone object base class and factory
----
Devel-CheckOS-1.46
http://search.cpan.org/~dcantrell/Devel-CheckOS-1.46/
check what OS we're running on
----
Devel-Declare-0.003003
http://search.cpan.org/~flora/Devel-Declare-0.003003/
Adding keywords to perl, in perl
----
EBook-Tools-0.1.0
http://search.cpan.org/~azed/EBook-Tools-0.1.0/
An object class for the manipulation and generation of E-books based on IDPF standards
----
File-Fingerprint-0.10_02
http://search.cpan.org/~bdfoy/File-Fingerprint-0.10_02/
This is the description
----
GD-Tab-Guitar-0.03
http://search.cpan.org/~taniguchi/GD-Tab-Guitar-0.03/
Guitar tab image generator.
----
Games-Risk-2.1.0
http://search.cpan.org/~jquelin/Games-Risk-2.1.0/
classical 'risk' board game
----
HTTP-Session-0.06
http://search.cpan.org/~tokuhirom/HTTP-Session-0.06/
simple session
----
Image-ExifTool-7.51
http://search.cpan.org/~exiftool/Image-ExifTool-7.51/
Read and write meta information
----
LCFG-Build-Tools-0.0.42
http://search.cpan.org/~sjquinney/LCFG-Build-Tools-0.0.42/
LCFG software release tools
----
LEOCHARRE-Checksetup-1.02
http://search.cpan.org/~leocharre/LEOCHARRE-Checksetup-1.02/
----
Mail-Postfix-Postdrop-0.2
http://search.cpan.org/~pmakholm/Mail-Postfix-Postdrop-0.2/
Inject mails to a Postfix maildrop directory
----
Module-MakeMaker-0.03
http://search.cpan.org/~ingy/Module-MakeMaker-0.03/
A New Way to Make Modules
----
Module-Setup-0.06_01
http://search.cpan.org/~yappo/Module-Setup-0.06_01/
a simple module maker "yet another Module::Start(?:er)?"
----
MooseX-DOM-0.00999_02
http://search.cpan.org/~dmaki/MooseX-DOM-0.00999_02/
Easily Create DOM Based Objects
----
MooseX-Types-Structured-0.01
http://search.cpan.org/~jjnapiork/MooseX-Types-Structured-0.01/
----
Net-Amazon-HadoopEC2-S3fs-0.01
http://search.cpan.org/~danjou/Net-Amazon-HadoopEC2-S3fs-0.01/
Perl interface to hadoop s3fs
----
Net-IPTrie-v0.4
http://search.cpan.org/~cvicente/Net-IPTrie-v0.4/
Perl module for building IPv4 and IPv6 address space hierarchies fast
----
Object-InsideOut-3.52
http://search.cpan.org/~jdhedden/Object-InsideOut-3.52/
Comprehensive inside-out object support module
----
PAR-Dist-0.40
http://search.cpan.org/~smueller/PAR-Dist-0.40/
Create and manipulate PAR distributions
----
POE-Component-MessageQueue-0.2.4
http://search.cpan.org/~dsnopek/POE-Component-MessageQueue-0.2.4/
A POE message queue that uses STOMP for its communication protocol
----
Padre-0.14
http://search.cpan.org/~szabgab/Padre-0.14/
Perl Application Development and Refactoring Environment
----
Parse-Apache-ServerStatus-0.07_01
http://search.cpan.org/~bloonix/Parse-Apache-ServerStatus-0.07_01/
Simple module to parse apache's server-status.
----
Parse-Apache-ServerStatus-0.07_02
http://search.cpan.org/~bloonix/Parse-Apache-ServerStatus-0.07_02/
Simple module to parse apache's server-status.
----
Path-Extended-0.03
http://search.cpan.org/~ishigaki/Path-Extended-0.03/
yet another Path class
----
PathTools-3.28_02
http://search.cpan.org/~smueller/PathTools-3.28_02/
----
PathTools-3.28_03
http://search.cpan.org/~smueller/PathTools-3.28_03/
----
Pg-Loader-0.11
http://search.cpan.org/~ioannis/Pg-Loader-0.11/
Perl extension for loading Postgres tables
----
Rose-HTMLx-Form-Related-0.10
http://search.cpan.org/~karman/Rose-HTMLx-Form-Related-0.10/
RHTMLO forms, living together
----
Rose-HTMLx-Form-Related-0.11
http://search.cpan.org/~karman/Rose-HTMLx-Form-Related-0.11/
RHTMLO forms, living together
----
String-RewritePrefix-0.003
http://search.cpan.org/~rjbs/String-RewritePrefix-0.003/
rewrite strings based on a set of known prefixes
----
Template-Toolkit-Simple-0.03
http://search.cpan.org/~ingy/Template-Toolkit-Simple-0.03/
A Simple Interface to Template Toolkit
----
Test-Aggregate-0.35
http://search.cpan.org/~ovid/Test-Aggregate-0.35/
Aggregate *.t tests to make them run faster.
----
Test-WWW-Mechanize-Catalyst-0.44
http://search.cpan.org/~lbrocard/Test-WWW-Mechanize-Catalyst-0.44/
Test::WWW::Mechanize for Catalyst
----
UML-Class-Simple-0.17
http://search.cpan.org/~agent/UML-Class-Simple-0.17/
Render simple UML class diagrams, by loading the code
----
WWW-Contact-0.07
http://search.cpan.org/~fayland/WWW-Contact-0.07/
Get contacts/addressbook from Web
----
WWW-Contact-0.08
http://search.cpan.org/~sachinjsk/WWW-Contact-0.08/
Get contacts/addressbook from Web
----
WWW-Contact-0.09
http://search.cpan.org/~fayland/WWW-Contact-0.09/
Get contacts/addressbook from Web
----
WWW-Contact-0.10
http://search.cpan.org/~fayland/WWW-Contact-0.10/
Get contacts/addressbook from Web
----
WWW-Contact-0.11
http://search.cpan.org/~fayland/WWW-Contact-0.11/
Get contacts/addressbook from Web
----
WWW-Contact-0.12
http://search.cpan.org/~sachinjsk/WWW-Contact-0.12/
Get contacts/addressbook from Web
----
WWW-Mechanize-1.50
http://search.cpan.org/~petdance/WWW-Mechanize-1.50/
Handy web browsing in a Perl object
----
WWW-Myspace-Data-0.18
http://search.cpan.org/~oalders/WWW-Myspace-Data-0.18/
WWW::Myspace database interaction
----
WebService-Cath-FuncNet-0.02
http://search.cpan.org/~isillitoe/WebService-Cath-FuncNet-0.02/
Interface to the CATH FuncNet webservice
----
genpass-0.09
http://search.cpan.org/~xsawyerx/genpass-0.09/
Quickly create secure passwords
----
github_creator-0.13
http://search.cpan.org/~bdfoy/github_creator-0.13/
----
perl-ldap-0.39
http://search.cpan.org/~gbarr/perl-ldap-0.39/
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/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
------------------------------
Date: Tue, 28 Oct 2008 07:20:17 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <R2zNk.1500$%11.5@flpi144.ffdc.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, 27 Oct 2008 21:40:57 +0000 (UTC)
From: kj <socyl@987jk.com.invalid>
Subject: subversion introspection
Message-Id: <ge5ch9$8t7$1@reader1.panix.com>
I have a script that uses several home-grown modules.
These modules live in the directory "$FindBin::RealBin/lib" (here
$FindBin::RealBin stands for the parent directory of the script).
The script and all the modules are under revision control, via
Subversion.
OK, now I'd like a good way to cause the script to fail if it
detects that it (i.e. the copy of the software that is executing)
is not the most recently committed version.
Before I roll my own, I thought I'd ask around if there's already
a good way to do this.
TIA!
Kynn
--
NOTE: In my address everything before the first period is backwards;
and the last period, and everything after it, should be discarded.
------------------------------
Date: 27 Oct 2008 22:21:46 GMT
From: John Bokma <john@castleamber.com>
Subject: Re: subversion introspection
Message-Id: <Xns9B44A6745520castleamber@130.133.1.4>
kj <socyl@987jk.com.invalid> wrote:
> I have a script that uses several home-grown modules.
>
> These modules live in the directory "$FindBin::RealBin/lib" (here
> $FindBin::RealBin stands for the parent directory of the script).
>
> The script and all the modules are under revision control, via
> Subversion.
>
> OK, now I'd like a good way to cause the script to fail if it
> detects that it (i.e. the copy of the software that is executing)
> is not the most recently committed version.
You want your script to "see" if all modules are the latest version(s)?
Maybe using the keywords property and put the version in a scalar, and
check this version in your script for all modules?
See:
http://johnbokma.com/mexit/2008/09/30/
--
John http://johnbokma.com/ - Hacking & Hiking in Mexico
Perl help in exchange for a gift:
http://johnbokma.com/perl/help-in-exchange-for-a-gift.html
------------------------------
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 1948
***************************************
