[25538] in Perl-Users-Digest
Perl-Users Digest, Issue: 7782 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Feb 15 06:05:24 2005
Date: Tue, 15 Feb 2005 03:05:10 -0800 (PST)
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, 15 Feb 2005 Volume: 10 Number: 7782
Today's topics:
[perl-python] problem: reducing comparison <xah@xahlee.org>
Re: Directory search <someone@example.com>
Re: editing pdf files with perl <lambik@kieffer.nl>
Re: editing pdf files with perl <segraves_f13@mindspring.com>
Re: Feeding false an App <hackeras@gmail.com>
Re: Modification of a read-only value attempted <g-preston1@ti.com>
passing hash and another arg to a sub (mike)
Re: passing hash and another arg to a sub <noreply@gunnar.cc>
Re: passing hash and another arg to a sub <amead@comcast.net>
Re: Perl script question rajasekaran.natarajan@gmail.com
Re: Perl script question <someone@example.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Regular expression to match particular lines betwee <someone@example.com>
Re: vi "power tools" for Perl coding? <sholden@flexal.cs.usyd.edu.au>
Re: vi "power tools" for Perl coding? <tassilo.von.parseval@rwth-aachen.de>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 14 Feb 2005 22:52:28 -0800
From: "Xah Lee" <xah@xahlee.org>
Subject: [perl-python] problem: reducing comparison
Message-Id: <1108450348.253772.158120@z14g2000cwz.googlegroups.com>
here's a interesting real-world algoritm to have fun with.
attached below is the Perl documentation that i wrote for a function
called "reduce", which is really the heart of a larger software.
The implementation is really simple, but the key is to understand what
the function should be. I'll post Perl and Python codes tomorrow for
those interested. If you are a perl programer, try to code it in
Python. (it's easy.)
This is brought to you by the Perl-Python a-day community. To
subscribe, see
http://xahlee.org/perl-python/python.html
Xah
xah@xahlee.org
http://xahlee.org/PageTwo_dir/more.html
-------------------------------
=pod
e.g. reduce( $pairings, $a_pair) retured the first argument with some
pairs deleted.
Detail:
we have n things, represented by numbers 1 to n. Some of these are
identical. We want to partition the range of numbers 1 to n so that
identical ones are grouped together.
To begin comparison, we generate a list of pairings that's all
possible parings of numbers 1 to n. (of course order does not matter,
and the pairing does not contain repeations) This is the first
argument to reduce.
We'll go thru this pairings list one by one and do comparisons, remove
the pair once it has been compared. However, more pairs can be removed
if a we find a pair identical.
For example, suppose we know that 2 and 4 are identical, and if the
pairing list contains (2,3) and (4,3), one of them can be deleted
because now 2 and 4 are the same thing.
(We do this because we expect the comparison operation will be
expensive.)
reduce( $pairings, $a_pair) returns a reduced $pairings knowing that
$a_pair are identical.
The first argument $pairings must be in the form of a hash. e.g.
{'1,5' => [1,5],'3,5' => [3,5],'2,4' => [2,4],'4,5' => [4,5],'1,3' =>
[1,3],'2,5' => [2,5],'1,2' => [1,2],'3,4' => [3,4],'2,3' =>
[2,3],'1,4' => [1,4]}
(Note that keys are strings of the pairs separated by a comma.)
$a_pair is a reference to a list of the form [$a,$b].
(different pairs may be deleted if the hash's pairs are given in
different order. i.e. 3,4 instead of 4,3)
The return value is a reference to a hash.
The program is deterministic but exactly which pairs are deleted is
unspecified. If the input is all possible pairs of 2 things out of n,
maximum reduction is guaranteed.
=cut
------------------------------
Date: Tue, 15 Feb 2005 10:59:50 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: Directory search
Message-Id: <GCkQd.47739$gA4.40140@edtnps89>
eyal.susser@gmail.com wrote:
>
> I'm working on a Fedora Core 3 machine. I am also a perl newbie. I
> would like to write a script that iterates through directories and
> finds files with specific attributes.
> I wrote a subroutine called scan:
>
> sub scan
> {
> $dirname = shift;
> open(DIRAHNDLE , $filename);
You have a typo, DIRAHNDLE should be DIRHANDLE and besides, open() uses
filehandles not directory handles. You open the file in $filename but you
don't do anything with it, which is OK in this case because you don't test
whether the filehandle is valid or not.
perldoc -f open
perldoc -f opendir
> @contents = <$dirname . "/*">
You are using a file glob to match the contents of $dirname followed by the
file '.' followed by all the files in the root directory?
perldoc -f glob
perldoc File::Glob
> close(DIRHANDLE);
>
> foreach $member (@contents)
> {
> if(-d $member)
> print("Dir: " . $dirname . "/" . $member);
Since the contents of $dirname are included in $member you are printing it
twice.
> else
> print("File: " . $member);
> }
> }
>
> This was just for testing. I ran it on /home/username, and have
> several problems:
> 1. I get a result like /home/username/home/username, probably because
> of the . directory
> 2. I get a list of all the files and directories under / ! Why is
> that?
> 3. So how do I write a script that does what I want? I wanted to use
> recursion, but with these wacky results, it would lead to an infinite
> loop!
perldoc File::Find
John
--
use Perl;
program
fulfillment
------------------------------
Date: Tue, 15 Feb 2005 09:45:53 +0100
From: Lambik <lambik@kieffer.nl>
Subject: Re: editing pdf files with perl
Message-Id: <37dr0kF5b99haU1@individual.net>
aditya2507@gmail.com wrote:
>
> Hi,
>
> I have a collection of PDF files which are stored in a directory. These
> PDF files follow a particular format. Each one of these files has some
> fields in the first page which are left blank. I need to fill those
> fields based on the input given by the user(s).
> I CANNOT overwrite these PDF files since the data contained in them is
> not elsewhere. I simply need to be able to edit and update the first
> page of these PDF files.
>
> Is there any way I can do this with Perl?
>
> Thanks in advance :)
>
> Aditya
PDF::Reuse???
#Make a new temp-file
prFile('$date.pdf');
#import the templet
prDoc ( { file => $documentName,
first => $firstPage,
last => $lastPage } );
#assign a value to an interactive field
prField ( $fieldName, $value )
------------------------------
Date: Tue, 15 Feb 2005 05:07:26 GMT
From: "Bill Segraves" <segraves_f13@mindspring.com>
Subject: Re: editing pdf files with perl
Message-Id: <isfQd.2363$VI5.577@newsread3.news.atl.earthlink.net>
"pikus" <hacker.poet@gmail.com> wrote in message
news:1108438561.091781.264040@o13g2000cwo.googlegroups.com...
<snip>
> So why does this not qualify as an appropriate question for this group?
> It certainly looks like a miscellaneous perl question to me...
Just my opinion. Others may not agree.
One favored method of entering form data into a PDF form with fillable
fields is to use an FDF file or its equivalent. Since an FDF can be written
by a script in any language, e.g., I prefer Perl, but have used PHP, as well
as shell scripts, while others use un-named (here) M$ languages.
The fact that it looks like a "miscellaneous perl" question does not make it
appropriate for this newsgroup (See the posting guidelines).
OTHO, also IMO, if the OP had provided a Perl script to accomplish his
objective, with which he was having trouble, the posting might have been
more appropriate for this newsgroup.
>Plus I
> want to know the answer but I'm lazy enough not to go to comp.text.pdf
> to get it. :-) Thanks. - pikus
>
You're very welcome. If you'd like to read the answer that's already over
there in comp.text.pdf, you'll just have to muster up enough "get up and go"
to get up and go there. ;-)
Cheers.
--
Bill Segraves
------------------------------
Date: Tue, 15 Feb 2005 10:48:33 +0000 (UTC)
From: Richard Anderson <hackeras@gmail.com>
Subject: Re: Feeding false an App
Message-Id: <Xns95FE8294BC490hackerasgmailcom@194.177.210.210>
Sherm Pendley <spamtrap@dot-app.org> wrote in
news:VYidnV2V4MVNQ43fRVn-qw@adelphia.com:
>> Well the cpu id request is issued by an online chess game server my
>> friend has running from his 24/7 connected pc and because the online
>> chess server directly connectz to his chess client app that i happen
>> to run on my pc
>
> We're finally getting somewhere. There's probably not much point in
> trying to reverse-engineer the app. Even if you could figure out how
> it's getting CPU info from Windows, it would be really hard to feed it
> misinformation that way.
>
> A better approach would be to intercept the incoming network request,
> and redirect it to an app of your own. To do that, you need to figure
> out two things:
>
> 1. What port the app listens on.
> 2. What protocol it speaks.
>
> Google for "port scanner" and "packet sniffer" for tools to help
> figure those two things out. Once you know the port, you can easily
> configure your firewall to redirect incoming requests on that port to
> a port that your app is listening on. And once you know the protocol,
> you'll be able to write your app to respond to those requests.
>
> Once you're ready to write your app, go to <http://search.cpan.org>,
> and search for "network server", and/or the protocol you want to
> implement.
>
> It's a lot of work, and it might not seem worth it just to cheat at
> chess and/or win a bet. But it's a good learning exercise - accurately
> defining a problem, and then breaking it down into manageable pieces,
> is a vital skill for any programmer to have.
Here's a slightly simpler modification to that plan: make a proxy server
that watches the data going out from this program and which will modify
the outgoing CPU ID. Essentially it will be like this:
My program <==> My proxy server <==internet==> His server
(Sees CPU ID) (Modifies CPU ID) (Sees fake CPU ID)
I won't need to do any "packet sniffing" or anything like that,
because i will be able to simply record the data that passes through
my perl proxy server. Once i find a way to recognize when my CPU ID is
sent, then i can just add some code to it to modify the CPU ID when it
sees it.
Technically i won't be fooling his program on my PC, but i will
still be spoofing my CPU ID to any other computer i'am talking to.
I think that thius alternative is evne better but then again i'am having
trouble implementing it.
Maybe you could help me with a sample perl script thats act like this to
get a clue on how its done?
------------------------------
Date: Mon, 14 Feb 2005 23:40:13 -0600
From: "Jerry Preston" <g-preston1@ti.com>
Subject: Re: Modification of a read-only value attempted
Message-Id: <cus1vu$amh$1@home.itg.ti.com>
I not sure what the deal is, but my code is working like it should for no
reason that I can see!
Regards,
Jerry
"Jerry Preston" <g-preston1@ti.com> wrote in message
news:curt44$7j6$1@home.itg.ti.com...
> I do not understand this at all:
>
> local( *FI );
> open( FI, $file ) || die "cannot open input file $file: ";
> while(<FI>) { # I get "Modification of a read-only value attempted
at
> $file this line"
>
> I have done this countless number of times. What is going on?
>
> Thanks,
>
> Jerry
>
>
>
>
------------------------------
Date: 14 Feb 2005 22:13:05 -0800
From: s99999999s2003@yahoo.com (mike)
Subject: passing hash and another arg to a sub
Message-Id: <dfd17ef4.0502142213.629da1f7@posting.google.com>
hi
i have something like this
%names = (1=>['TEST','12345','testuser'],
2=>['TEST USER','12345','testuser1']);
do_something(%names,'ABC');
sub do_something {
my (%hash,$abc) = @_;
print "abc = $abc";
while ( my ($keys,$val) = each(%hash) )
{
print "key = $keys, value = $val\n";
}
}
i got the output
abc =
key = ABC, value =
key = 1, value = ARRAY(0x1abeff4)
key = 2, value = ARRAY(0x1abf0fc)
why does 'ABC' become a key inside the hash?? I think there's someting
wrong with passing the @_.
thanks for any help
------------------------------
Date: Tue, 15 Feb 2005 07:20:54 +0100
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: passing hash and another arg to a sub
Message-Id: <37dj6cF5asn67U1@individual.net>
mike wrote:
> i have something like this
> %names = (1=>['TEST','12345','testuser'],
> 2=>['TEST USER','12345','testuser1']);
>
> do_something(%names,'ABC');
<snip>
You asked a FAQ.
perldoc -q pass/return
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Tue, 15 Feb 2005 00:30:47 -0600
From: Alan Mead <amead@comcast.net>
Subject: Re: passing hash and another arg to a sub
Message-Id: <pan.2005.02.15.06.30.46.653834@comcast.net>
On Mon, 14 Feb 2005 22:13:05 -0800, mike wrote:
> hi
>
> i have something like this
> %names = (1=>['TEST','12345','testuser'],
> 2=>['TEST USER','12345','testuser1']);
>
> do_something(%names,'ABC');
>
>
> sub do_something {
> my (%hash,$abc) = @_;
> print "abc = $abc";
>
> while ( my ($keys,$val) = each(%hash) )
> {
> print "key = $keys, value = $val\n";
> }
>
> }
You need to pass a reference to the hash:
do_something(\%names,'ABC');
...
sub do_something {
my($hash,$abc) = @_;
print join(', ',keys %$hash);
$$hash{'my new key'} = 'this will change %hash in the calling scope!';
...
There are some great documents related to references that come with perl.
Type 'man perl' and look for "reference". The data structures cookbook
is also thrilling reading.
-Alan
--
Help out our research and get a free
personality profile:
http://www.web-data-collection.org
------------------------------
Date: 14 Feb 2005 21:20:11 -0800
From: rajasekaran.natarajan@gmail.com
Subject: Re: Perl script question
Message-Id: <1108444811.194015.50770@c13g2000cwb.googlegroups.com>
Hi
If I have similar need I would try to use only perl without awk and
egrep
some dirty code may be like this
#!/usr/sbin/perl -w
$LOG = "m.log";
$SIG{"INT"} = "clean_exit";
$SIG{"TERM"} = "clean_exit";
$word = "ERR";
open(FILE, $LOG) || die "Can not open file $LOG";
open(OUT, ">out.log") || die "Can not open file $LOG";
my $count = 0;
while ($line = <FILE>) {
if($line =~ m/$word/) {
@a=split(" ",$line);
$count++;
print OUT "$count:$a[0]\n";
}
else {
$count++;
}
}
close(OUT);
close(FILE);
it wrties the output to out.log for the future comparision. But I am
not aware how to get only last line.
------------------------------
Date: Tue, 15 Feb 2005 10:29:02 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: Perl script question
Message-Id: <O9kQd.47734$gA4.45025@edtnps89>
Jürgen Exner wrote:
> George Monappallil wrote:
>
>>Hi Guys:
>>Below is my code.
>
> You may not believe it, but a namesake of yours just posted exactly the same
> question to CLP.
There is no such news group. Maybe that's why he posted here? :-)
John
--
use Perl;
program
fulfillment
------------------------------
Date: 15 Feb 2005 08:22:09 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <4211b130$0$23563$8b463f8a@news.nationwide.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
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://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
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Tue, 15 Feb 2005 10:40:49 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: Regular expression to match particular lines between markers
Message-Id: <RkkQd.380$%y.137@clgrps12>
MENTAT wrote:
>
> I am trying to write a regular expression that extracts all the
> comment lines between two specified markers in a text. An example
> snippet is given below. (comments start with ";")
>
> [MRCP_SERVER] ;MRCP server format:
> <Server_IP_Address>:<Server_Port>
> ; <Server_Port> is 554 for Nuance, 4900 for
> Speechworks
> ; Each server should be specified on a separate
> line
> ;123.123.123.1:554 ; server1
> tadlir01:4900 ; comment 1
> tadlir02:4900 ; comment 2
>
> [DisableVAD] ; Disables VAD in the TX streamer
>
> I want the output to look like:
>
> [MRCP_SERVER] ;MRCP server format:
> <Server_IP_Address>:<Server_Port>
> ; <Server_Port> is 554 for Nuance, 4900 for
> Speechworks
> ; Each server should be specified on a separate
> line
> ;123.123.123.1:554 ; server1
>
> [DisableVAD] ; Disables VAD in the TX streamer
>
> basically, everything between [MRCP_SERVER] and [DisableVAD] that
> starts on a line beginning with ";"
According to your examples you probably want something like this:
# UNTESTED
while ( <FILEHANDLE> ) {
if ( /^\[MRCP_SERVER]/ .. /^\[DisableVAD]/ ) {
$_ = '' if /^[^;]+;/;
}
print;
}
# UNTESTED
John
--
use Perl;
program
fulfillment
------------------------------
Date: 15 Feb 2005 06:19:19 GMT
From: Sam Holden <sholden@flexal.cs.usyd.edu.au>
Subject: Re: vi "power tools" for Perl coding?
Message-Id: <slrnd13537.9pd.sholden@flexal.cs.usyd.edu.au>
On 14 Feb 2005 22:54:54 GMT, Abigail <abigail@abigail.nl> wrote:
> J Krugman (jkrugman345@yahbitoo.com) wrote on MMMMCLXXXV September
> MCMXCIII in <URL:news:cup47s$ldl$1@reader2.panix.com>:
>
> But who cares? If you like emacs, and its cperl mode works for you,
> then keep using that.
>
>
> [] So I decided to add the following to my .emacs file (probably
> [] re-inventing a thoroughly invented wheel):
>
> [ 19 line macro ]
>
> A similar macro for my editor:
>
> 3 store-macro
> save-file
> shell-command &cat "perl -c " $cfilname
> ~endm
Can I play editor wars to? :)
#!/bin/sh
Put
wperl -c "$w"
>
> [] (add-hook 'cperl-mode-hook (lambda ()
> [] (local-set-key [(f12)] 'check-perl)
> [] ))
>
>
> bind-key execute-macro-3 ^A-c
My editor doesn't do that, you just put the name of the file somewhere.
--
Sam Holden
------------------------------
Date: Mon, 14 Feb 2005 08:33:11 +0100
From: "Tassilo v. Parseval" <tassilo.von.parseval@rwth-aachen.de>
Subject: Re: vi "power tools" for Perl coding?
Message-Id: <slrnd10l1n.ps.tassilo.von.parseval@localhost.localdomain>
Also sprach Abigail:
> J Krugman (jkrugman345@yahbitoo.com) wrote on MMMMCLXXXV September
> MCMXCIII in <URL:news:cup47s$ldl$1@reader2.panix.com>:
> [] So I decided to add the following to my .emacs file (probably
> [] re-inventing a thoroughly invented wheel):
>
> [ 19 line macro ]
>
> A similar macro for my editor:
>
> 3 store-macro
> save-file
> shell-command &cat "perl -c " $cfilname
> ~endm
Ah, that is not going to win you a vim golfing contest. For checking the
syntax of a script or running it, I have in my vimrc:
map ü :!perl -w % <CR>
map ö :!perl -wc % <CR>
Tassilo
--
use bigint;
$n=71423350343770280161397026330337371139054411854220053437565440;
$m=-8,;;$_=$n&(0xff)<<$m,,$_>>=$m,,print+chr,,while(($m+=8)<=200);
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 7782
***************************************
