[23050] in Perl-Users-Digest
Perl-Users Digest, Issue: 5271 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jul 25 06:05:50 2003
Date: Fri, 25 Jul 2003 03:05: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 Fri, 25 Jul 2003 Volume: 10 Number: 5271
Today's topics:
Re: Can one control swap in Perl? news@roaima.freeserve.co.uk
Re: delete directory files from a list. Help Please <krahnj@acm.org>
Re: delete directory files from a list. Help Please <mbudash@sonic.net>
Re: document ID tracking <REMOVEsdnCAPS@comcast.net>
How do I return to the top of a file without closing an <jandellis@hotmail.com>
Re: How do I return to the top of a file without closin <tassilo.parseval@rwth-aachen.de>
Re: Install Perl Bin on Win32 Using Mingw (GCC) <kalinabears@iinet.net.au>
Re: Lookup Country by IP Address <njh@despammed.com>
Newbie: Problems with a CPAN installation (Francesco Moi)
Re: Newbie: Problems with a CPAN installation <kalinabears@iinet.net.au>
Re: Non-Core Module Inclusion (Sam Holden)
Re: Non-Core Module Inclusion <abigail@abigail.nl>
Re: Non-Core Module Inclusion <noreply@gunnar.cc>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: regl expression <john.thetenant-s@moving-picture.com>
Tracking Number (Jeff Mott)
Re: Tracking Number <mgjv@tradingpost.com.au>
Re: <bwalton@rochester.rr.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 25 Jul 2003 09:56:01 +0100
From: news@roaima.freeserve.co.uk
Subject: Re: Can one control swap in Perl?
Message-Id: <1u77v-3as.ln1@moldev.cmagroup.co.uk>
Irving Kimura <irving_kimura@lycos.com> wrote:
> Is there any way that I can designate a
> variable in a Perl script so that it will never be swapped out to
> disk?
Some platforms provide the mlock() and munlock() system calls to do
just this (POSIX.1b and SVr4, apparently - which probably means most
UNIX/Linux systems). One could conceivably write a module to provide
these to a perl process. Bear in mind, though, that your program would
need to run as a privileged process to be able to use these calls.
Chris
--
@s=split(//,"Je,\nhn ersloak rcet thuarP");$k=$l=@s;for(;$k;$k--){$i=($i+1)%$l
until$s[$i];$c=$s[$i];print$c;undef$s[$i];$i=($i+(ord$c))%$l}
------------------------------
Date: Fri, 25 Jul 2003 06:58:29 GMT
From: "John W. Krahn" <krahnj@acm.org>
Subject: Re: delete directory files from a list. Help Please
Message-Id: <3F20D548.2FEFCC46@acm.org>
DieSpammersDie wrote:
>
> Here is my problem. I want to delete the files contained in a directory
> from a list contained in a file. Here is an example:
>
> The input file is a regular text file in the following format (call it
> myfile.txt);
>
> item1
> item2
> item3
> item4
> ...
>
> What I want to do is look in a directory and delete any file in the
> directory that contains any item on the list. For example, lets say the
> contents of the directory looks like this:
>
> 07/24/2003 01:27 AM 3,812 heresanitem1
> 07/24/2003 10:42 PM 912,126 heretoitem2
> 07/14/2003 12:19 AM 234 item3ishere
> 06/12/2003 10:25 PM 34,049 leavemealone
> 06/12/2003 10:25 PM 16,683 leavemealonetoo
> 07/22/2003 11:36 PM 1,825 yupitem4yup
> ...
>
> I would like to read each line of the file from "myfile.txt" [getline() I
> suppose] and then delete the files that have ANY MATCHING information from
> the input file. So if the input file has "item1" it will delete the file
> "heresanitem1" as well as "alsoitem1aswell" from the directory. So when I
> run the script the sample directory above will look like this:
>
> 06/12/2003 10:25 PM 34,049 leavemealone
> 06/12/2003 10:25 PM 16,683 leavemealonetoo
> ...
>
> This problem has been tough for me. I have read everything I can get my
> hands on concerning unlink but I cannot get this problem solved. Any help
> appreciated.
my $file = 'myfile.txt';
my $dir = '/home/DieSpammersDie/something';
open my $fh, $file or die "Cannot open $file: $!";
my $files = join ' ', map "$dir/*$_*", map split, <$fh>;
unlink or warn "Cannot unlink $_: $!" for <$files>;
John
--
use Perl;
program
fulfillment
------------------------------
Date: Fri, 25 Jul 2003 06:56:34 GMT
From: Michael Budash <mbudash@sonic.net>
Subject: Re: delete directory files from a list. Help Please
Message-Id: <mbudash-8EC90B.23563424072003@typhoon.sonic.net>
In article
<YW50aWdvbmU=.ed819e6f4d9b2320e91bb3828d498735@1059104300.cotse.net>,
"DieSpammersDie" <DieSpammersDie-no-spam@antigone.cotse.net> wrote:
> Here is my problem. I want to delete the files contained in a directory
> from a list contained in a file. Here is an example:
>
> The input file is a regular text file in the following format (call it
> myfile.txt);
>
> item1
> item2
> item3
> item4
> ...
>
> What I want to do is look in a directory and delete any file in the
> directory that contains any item on the list. For example, lets say the
> contents of the directory looks like this:
>
> 07/24/2003 01:27 AM 3,812 heresanitem1
> 07/24/2003 10:42 PM 912,126 heretoitem2
> 07/14/2003 12:19 AM 234 item3ishere
> 06/12/2003 10:25 PM 34,049 leavemealone
> 06/12/2003 10:25 PM 16,683 leavemealonetoo
> 07/22/2003 11:36 PM 1,825 yupitem4yup
> ...
>
> I would like to read each line of the file from "myfile.txt" [getline() I
> suppose] and then delete the files that have ANY MATCHING information from
> the input file. So if the input file has "item1" it will delete the file
> "heresanitem1" as well as "alsoitem1aswell" from the directory. So when I
> run the script the sample directory above will look like this:
>
> 06/12/2003 10:25 PM 34,049 leavemealone
> 06/12/2003 10:25 PM 16,683 leavemealonetoo
> ...
>
> This problem has been tough for me. I have read everything I can get my
> hands on concerning unlink but I cannot get this problem solved. Any help
> appreciated.
>
perldoc -f opendir
perldoc -f readdir
perldoc perlre
perldoc -f unlink
etc.
hope this helps... come on back if it doesn't...
--
Michael Budash
------------------------------
Date: Fri, 25 Jul 2003 05:02:36 -0500
From: "Eric J. Roode" <REMOVEsdnCAPS@comcast.net>
Subject: Re: document ID tracking
Message-Id: <Xns93C33D640AD40sdn.comcast@206.127.4.25>
-----BEGIN xxx SIGNED MESSAGE-----
Hash: SHA1
"A. Sinan Unur" <asu1@c-o-r-n-e-l-l.edu> wrote in
news:Xns93C2A80F838A4asu1cornelledu@132.236.56.8:
> if(exists $word_to_files{$word}) {
> unless(grep /$ARGV/, @{$word_to_files{$word}}) {
> push @{$word_to_files{$word}}, ($ARGV);
> }
> } else {
> $word_to_files{$word} = [$ARGV];
> }
Why use an array as the second-level data structure -- why not a hash?
$word_to_files{$word}{$ARGV} = 1;
- --
Eric
$_ = reverse sort qw p ekca lre Js reh ts
p, $/.r, map $_.$", qw e p h tona e; print
-----BEGIN xxx SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBPyEAG2PeouIeTNHoEQL8tQCcDqV7RIXQpkLdixd/fX8I6mS3TKQAnRUK
IYK6PGqSuEmL6krOv6gj+mI0
=7lDc
-----END PGP SIGNATURE-----
------------------------------
Date: Fri, 25 Jul 2003 05:22:48 GMT
From: Joseph Ellis <jandellis@hotmail.com>
Subject: How do I return to the top of a file without closing and reopening?
Message-Id: <vfe1ivss8ra0hcgrsi9pubnfm7t45k2r20@4ax.com>
Hello all.
I am currently writing a program that opens a file, searches for and
records a few lines into an array, then processes the lines in the
array in preparation for output.
However, some of the information that may be encountered in this array
may require the program to go back to the top of the file, and begin
searching for this new information.
Quick example:
open (FILE, "textfile.txt");
my $found;
while (<FILE>) {
if (/desiredinfo/) {
$found = 1;
push ($_, @array);
next;
}
if ($found and /nomoredesiredinfo/) {
last;
}
}
foreach (@array) {
if (/ineedtolookthroughtheFILEagain/) {
while(<FILE>) {
# Resumes reading through the FILE
# at the point where it left off at
# the end of the while loop, but
# I'd like to return to top of file
# instead.
if (/newinformation/) {
do_whatever();
}
}
}
}
close FILE;
Does this make sense? I'd like to return to TOF without having to
close and reopen the file for every element in @array that warrants
it.
I've read through perlfaq5 and ran every keyword I could think of
through perldoc -q. I presume that closing the file and reopening it
would have the desired effect, but wouldn't that be rather slow and
cumbersome?
Thanks for any suggestions.
Joseph
------------------------------
Date: 25 Jul 2003 05:44:28 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: How do I return to the top of a file without closing and reopening?
Message-Id: <bfqg3s$okl$1@nets3.rz.RWTH-Aachen.DE>
Also sprach Joseph Ellis:
> I am currently writing a program that opens a file, searches for and
> records a few lines into an array, then processes the lines in the
> array in preparation for output.
>
> However, some of the information that may be encountered in this array
> may require the program to go back to the top of the file, and begin
> searching for this new information.
>
> Quick example:
>
> open (FILE, "textfile.txt");
> my $found;
>
> while (<FILE>) {
> if (/desiredinfo/) {
> $found = 1;
> push ($_, @array);
> next;
> }
> if ($found and /nomoredesiredinfo/) {
> last;
> }
> }
>
> foreach (@array) {
> if (/ineedtolookthroughtheFILEagain/) {
> while(<FILE>) {
> # Resumes reading through the FILE
> # at the point where it left off at
> # the end of the while loop, but
> # I'd like to return to top of file
> # instead.
> if (/newinformation/) {
> do_whatever();
> }
> }
> }
> }
>
> close FILE;
>
> Does this make sense? I'd like to return to TOF without having to
> close and reopen the file for every element in @array that warrants
> it.
Use seek() and the appropriate constants from the Fcntl module for
portability:
use Fcntl qw/:seek/;
...
seek FILE, 0, SEEK_SET;
> I've read through perlfaq5 and ran every keyword I could think of
> through perldoc -q. I presume that closing the file and reopening it
> would have the desired effect, but wouldn't that be rather slow and
> cumbersome?
Yes, so use seek(). See 'perldoc -f seek'.
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: Fri, 25 Jul 2003 15:52:10 +1000
From: "Sisyphus" <kalinabears@iinet.net.au>
Subject: Re: Install Perl Bin on Win32 Using Mingw (GCC)
Message-Id: <3f20c697$0$23595$5a62ac22@freenews.iinet.net.au>
"Matthew Ogan" <mattogan@verizon.net> wrote in message
news:6H1Ua.65209$EZ2.36273@nwrddc01.gnilink.net...
> I found the answer after having posted the question. You use g++ instead
of
> gcc for linking (as directed in makefile.mk).
I didn't invoke g++ at any stage ...... maybe I don't understand something
about what you're doing.
Anyway, hey, if it's working as you'd like then I'm not gunna complain or
criticise :-)
Cheers,
Rob
------------------------------
Date: Fri, 25 Jul 2003 10:27:12 +0100
From: Nigel Horne <njh@despammed.com>
Subject: Re: Lookup Country by IP Address
Message-Id: <bfqt5o$35h$1$830fa78d@news.demon.co.uk>
143.182.124.4 [Shameer Balasingam] wrote:
>
> There is a database to lookup all IP address space to country. Pretty
> cool...
Alternatively try this at the shell prompt:
whois 207.46.134.190 | fgrep -i country
------------------------------
Date: 25 Jul 2003 01:52:03 -0700
From: francescomoi@europe.com (Francesco Moi)
Subject: Newbie: Problems with a CPAN installation
Message-Id: <5b829932.0307250052.49f5267a@posting.google.com>
Hello.
I'm trying to install 'LWP:Simple' module on my Linux machine.
# perl -MCPAN -e shell
cpan> install LWP:Simple
Going to read /root/.cpan/sources/modules/03modlist.data.gz
Warning: Cannot install LWP:Simple, don't know what it is.
Try the command
i /LWP:Simple/
to find objects with similar identifiers.
I don't have any idea about this error. Any suggestion?
On the other hand, I would like to install this module manually
(by using tar.gz, make, make install ...), but I don't find
the sources of 'LWP:Simple' (lwp-simple.tar.gz or something
similar).
I would be extremely obliged of anybody could help me. Thank you
very much.
------------------------------
Date: Fri, 25 Jul 2003 19:51:26 +1000
From: "Sisyphus" <kalinabears@iinet.net.au>
Subject: Re: Newbie: Problems with a CPAN installation
Message-Id: <3f20feab$0$23612$5a62ac22@freenews.iinet.net.au>
"Francesco Moi" <francescomoi@europe.com> wrote in message
>
> On the other hand, I would like to install this module manually
> (by using tar.gz, make, make install ...), but I don't find
> the sources of 'LWP:Simple' (lwp-simple.tar.gz or something
> similar).
>
It, and other LWP modules, are part of libwww-perl.
http://search.cpan.org/author/GAAS/libwww-perl-5.69/
Cheers,
Rob
------------------------------
Date: 25 Jul 2003 04:17:12 GMT
From: sholden@flexal.cs.usyd.edu.au (Sam Holden)
Subject: Re: Non-Core Module Inclusion
Message-Id: <slrnbi1bq8.1cb.sholden@flexal.cs.usyd.edu.au>
On Fri, 25 Jul 2003 05:38:56 +0200,
Gunnar Hjalmarsson <noreply@gunnar.cc> wrote:
> Jeff Mott wrote:
>> If your program/module uses modules not within the core
>> distribution, is it acceptable practice to package with it a copy
>> of that module? Particularly in the case of XS extensions. Is an XS
>> module built on one system the same as any another? Or should I
>> just inform the user which modules they must install?
>
> I read Martien's reply to your question, and it appeared to be good
> advise. But only sometimes. I'd say it depends on which kind of
> program it is, and the target audience for it.
>
> I have a CGI program, where I include a few non-core (not XS
> extensions, though) modules from CPAN. The users of my program are
> typically on shared web accounts, most often without shell access.
> Accordingly, they simply upload the modules via FTP to a program
> specific Perl library.
[snip details]
>
> Now, would the just described method be bad practice? Personally I
> can't see why.
Since the main problem is in XS extensions, and you simply don't have
those, then of course it's a reasonable solution. Of course it does
place some burden on you to keep track of those modules and make sure
you release a new install of your software whenever they are updated for
security reasons. And you also have to deal with meeting the distribution
requirements of those modules.
--
Sam Holden
------------------------------
Date: 25 Jul 2003 08:32:50 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: Non-Core Module Inclusion
Message-Id: <slrnbi1qpi.tem.abigail@alexandra.abigail.nl>
Tad McClellan (tadmc@augustmail.com) wrote on MMMDCXV September MCMXCIII
in <URL:news:slrnbi162r.9j6.tadmc@magna.augustmail.com>:
%% Jeff Mott <mjeff1@twcny.rr.com> wrote:
%%
%% > Is an XS module built on
%% > one system the same as any another?
%%
%% No.
%%
%% Compiling C depends on the libraries that the compiler uses.
%%
%% Different systems may have different libraries.
And not only that, even on the same system with the same libraries,
different Configure options will give you non-binary compatible
XS modules. Different versions of Perl as well.
Abigail
--
echo "==== ======= ==== ======"|perl -pes/=/J/|perl -pes/==/us/|perl -pes/=/t/\
|perl -pes/=/A/|perl -pes/=/n/|perl -pes/=/o/|perl -pes/==/th/|perl -pes/=/e/\
|perl -pes/=/r/|perl -pes/=/P/|perl -pes/=/e/|perl -pes/==/rl/|perl -pes/=/H/\
|perl -pes/=/a/|perl -pes/=/c/|perl -pes/=/k/|perl -pes/==/er/|perl -pes/=/./;
------------------------------
Date: Fri, 25 Jul 2003 11:12:11 +0200
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: Non-Core Module Inclusion
Message-Id: <bfqs8i$hmpmd$1@ID-184292.news.uni-berlin.de>
Sam Holden wrote:
> On Fri, 25 Jul 2003 05:38:56 +0200, Gunnar Hjalmarsson
> <noreply@gunnar.cc> wrote:
>> I have a CGI program, where I include a few non-core (not XS
>> extensions, though) modules from CPAN. The users of my program
>> are typically on shared web accounts, most often without shell
>> access. Accordingly, they simply upload the modules via FTP to a
>> program specific Perl library.
<snip>
> Since the main problem is in XS extensions, and you simply don't
> have those, then of course it's a reasonable solution. Of course it
> does place some burden on you to keep track of those modules and
> make sure you release a new install of your software whenever they
> are updated for security reasons.
That's true, but I don't feel it's a big burden. Those modules are
important for my program, and I keep posted on their development for
other reasons as well.
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Fri, 25 Jul 2003 02:22:52 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <SNecnftwl6JRR72iU-KYvw@august.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
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.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://mail.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"Jeopardy" (because the answer comes before the question), or
"TOFU".
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Fri, 25 Jul 2003 09:22:28 +0100
From: John Strauss <john.thetenant-s@moving-picture.com>
Subject: Re: regl expression
Message-Id: <20030725092228.56b366b1.john.thetenant-s@moving-picture.com>
On Sat, 19 Jul 2003 14:36:37 +0200
"bruno_storz" <bruno_storz@gmx.de> wrote:
>
> Hi there,
>
> I wonder, why this reg. expression does not replace this:
>
> $line = "<title><!-- HTML_titel --></title>";
> $html{'titel'} = "my Titel";
> $line =~ s/<!-- HTML_([a-z]+) -->/$htmlref->{$1}/gix;
>
> Any ideas?
>
> Regards
> Bruno
>
>
>
first idea: i've got no idea what's in %$htmlref,
though i have some idea what's in %html.
second idea: unless you've given us an incomplete
or typo'd snippet, you've not used the warnings and
strict pragmas-- which would have caught the first
problem before you even posted.
third idea: you need either to drop the '/x' modifier
on your pattern matching, or escape the whitespace in
your regexp. if this makes no sense to you, read
"perldoc perlre" (the bit about "The `/x' modifier
itself needs a little more explanation.")
fourth idea: you are replacing all of your search
pattern "<!-- HTML_([a-z]+) -->" with "my Titel".
which may be what you actually want, but you haven't
told us what you expect $line to contain when you're
done with it. if i'm right, try
$line =~ s/(<!-- HTML_)([a-z]+)( -->)/$1$htmlref->{$2}$3/gi;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drop the .thetenant to get me via mail
------------------------------
Date: 24 Jul 2003 22:29:34 -0700
From: mjeff1@twcny.rr.com (Jeff Mott)
Subject: Tracking Number
Message-Id: <970676ed.0307240949.3f57e1ae@posting.google.com>
I'm not really sure what group would be good to post this in, but
since I'm coding it in Perl I figured I'd drop it in here.
I need to know what formats the tracking numbers for UPS, FEDEX,
Airborne Express, etc. come in. I think I may have found some info on
UPS's, but I'm not sure how reliable it is, nor have I found anything
for the others. Does anyone know where I can find info on this?
------------------------------
Date: 25 Jul 2003 05:43:04 GMT
From: Martien Verbruggen <mgjv@tradingpost.com.au>
Subject: Re: Tracking Number
Message-Id: <slrnbi1grb.d0q.mgjv@verbruggen.comdyn.com.au>
On 24 Jul 2003 22:29:34 -0700,
Jeff Mott <mjeff1@twcny.rr.com> wrote:
> I'm not really sure what group would be good to post this in, but
> since I'm coding it in Perl I figured I'd drop it in here.
>
> I need to know what formats the tracking numbers for UPS, FEDEX,
> Airborne Express, etc. come in. I think I may have found some info on
> UPS's, but I'm not sure how reliable it is, nor have I found anything
> for the others. Does anyone know where I can find info on this?
It has really nothing to do with Perl at all, but it turns out someone
has already done a lot of this work. Go to search.cpan.org, and look
for modules with Fedex and UPS in the name.
Martien
--
|
Martien Verbruggen | +++ Out of Cheese Error +++ Reinstall
Trading Post Australia | Universe and Reboot +++
|
------------------------------
Date: Sat, 19 Jul 2003 01:59:56 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re:
Message-Id: <3F18A600.3040306@rochester.rr.com>
Ron wrote:
> Tried this code get a server 500 error.
>
> Anyone know what's wrong with it?
>
> if $DayName eq "Select a Day" or $RouteName eq "Select A Route") {
(---^
> dienice("Please use the back button on your browser to fill out the Day
> & Route fields.");
> }
...
> Ron
...
--
Bob Walton
------------------------------
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.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
To request back copies (available for a week or so), send your request
to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
where x is the volume number and y is the issue number.
For other requests pertaining to the digest, send mail to
perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
sending perl questions to the -request address, I don't have time to
answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 5271
***************************************
