[24706] in Perl-Users-Digest
Perl-Users Digest, Issue: 6863 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Aug 13 06:05:50 2004
Date: Fri, 13 Aug 2004 03:05:08 -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, 13 Aug 2004 Volume: 10 Number: 6863
Today's topics:
Counting text area <wayne.sargent@tiscali.fr>
Re: Counting text area <tore@aursand.no>
Re: Counting text area <spamtrap@dot-app.org>
Re: data comprised of regexs (while loop weirdness) <bowsayge@nomail.afraid.org>
Re: data comprised of regexs (while loop weirdness) <gnari@simnet.is>
freeing the memory used by a hash <ec_au_ravi2000@yahoo.com>
Re: freeing the memory used by a hash <tore@aursand.no>
Re: How to catch CTRL-C in Windows NT cmd.exe??? <kalinaubears@iinet.net.au>
Re: Match inner quotes ? <abigail@abigail.nl>
Re: Match inner quotes ? <eam@7ka.mipt.ru>
Re: Match inner quotes ? <gnari@simnet.is>
Re: Match inner quotes ? (Anno Siegel)
Re: Match inner quotes ? <matrix_calling@yahoo.dot.com>
Re: Module to print out all package variables...? (alex)
Re: Perl PDF modules - help please (Anno Siegel)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Reading next line, finding missing number in sequen <bowsayge@nomail.afraid.org>
Splitting paragraph into array. <mr@sandman.net>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 13 Aug 2004 10:26:56 +0200
From: "Davidd Sargent" <wayne.sargent@tiscali.fr>
Subject: Counting text area
Message-Id: <cfhtvj$16h$1@news.tiscali.fr>
Hi Everybody,
I'm new to this group.
I am trying to make a script but have a slight problem so I turned to you
guys.
I have a textarea which the user types there subdomain in to and then click
submit.
What I want is on the results page for it to count the number of subdomains
(each domain will be seperated by \n (a newline)).
Thanks in Advance
Kind Regards
Dave
------------------------------
Date: Fri, 13 Aug 2004 10:48:02 +0200
From: Tore Aursand <tore@aursand.no>
Subject: Re: Counting text area
Message-Id: <pan.2004.08.13.08.48.02.412737@aursand.no>
On Fri, 13 Aug 2004 10:26:56 +0200, Davidd Sargent wrote:
> What I want is on the results page for it to count the number of
> subdomains (each domain will be seperated by \n (a newline)).
1. Read the FORM data by using CGI.pm.
2. Get the lines by splitting on "\n"
3. Process each line, discard those which doesn't meet your "subdomain
requirements".
4. Present the result for the user.
--
Tore Aursand <tore@aursand.no>
"Poor management can increase software costs more rapidly than any
other factor." (Barry Boehm)
------------------------------
Date: Fri, 13 Aug 2004 04:53:59 -0400
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: Counting text area
Message-Id: <PaKdnZ6e8Os6HIHcRVn-tQ@adelphia.com>
Davidd Sargent wrote:
> I have a textarea which the user types there subdomain in to and then click
> submit.
> What I want is on the results page
Textarea? Submit? Results page? That doesn't sound like Perl to me. (I'm
not just saying that to be snippy - precisely defining a problem is the
first step towards solving it.)
> for it to count the number of subdomains
> (each domain will be seperated by \n (a newline)).
So your Perl problem is, you have a block of text in a scalar, and you
want to count the lines in it.
Use split() to split the text into an array of lines. Then use that
array in scalar context to count the number of elements in it.
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Fri, 13 Aug 2004 08:58:52 GMT
From: bowsayge <bowsayge@nomail.afraid.org>
Subject: Re: data comprised of regexs (while loop weirdness)
Message-Id: <gp%Sc.15072$nx2.5060@newsread2.news.atl.earthlink.net>
Scott W Gifford said to us:
[...]
> regular expressions can contain code, so if
> somebody can write to that file they'll have the ability to cause your
> script to execute code of their choice.
How can this feature be disabled?
--
my (@str) = split //,'l.wbtn t esirpneaoe ehuJr';
my (@ndx, @arr) = qw(16 24 20 21 3 6 12 8 4 19 2 22 11
13 18 10 5 7 23 17 14 9 1 0 15);
$arr[$ndx[$_]] = $str[$_] for (@ndx); print @arr, "\n";
------------------------------
Date: Fri, 13 Aug 2004 09:46:44 -0000
From: "gnari" <gnari@simnet.is>
Subject: Re: data comprised of regexs (while loop weirdness)
Message-Id: <cfi2i5$bla$1@news.simnet.is>
"Scott W Gifford" <gifford@umich.edu> wrote in message
news:qszy8kkw0tp.fsf@mspacman.gpcc.itd.umich.edu...
> #!/usr/bin/perl -w
>
> use strict;
>
> my $request = shift @ARGV;
>
> my @data = <DATA>;
> for(@data)
> {
> chomp;
> print "'$request' ?~ /$_/: ";
> if ($request =~ /$_/) {print 'yes';}
> print "\n";
> }
> __DATA__
> test1
> test2
> test3
> ...
> I assume that the contents of the file you're reading from is under
> your control, BTW; regular expressions can contain code, so if
> somebody can write to that file they'll have the ability to cause your
> script to execute code of their choice.
please provide an example.
there is no eval() or /e in the code showed.
(?{}) is not interpolated.
what are you talking about?
gnari
------------------------------
Date: 13 Aug 2004 00:31:12 -0700
From: "ravi" <ec_au_ravi2000@yahoo.com>
Subject: freeing the memory used by a hash
Message-Id: <cfhqo0$ant@odak26.prod.google.com>
which is a best way to free the all the memory used by a hash explain
in the context of complicated data structures like hash of hashes
undef %hash;
delete %hash;
%hash =();
What is the difference between these three
------------------------------
Date: Fri, 13 Aug 2004 10:46:06 +0200
From: Tore Aursand <tore@aursand.no>
Subject: Re: freeing the memory used by a hash
Message-Id: <pan.2004.08.13.08.46.05.77112@aursand.no>
On Fri, 13 Aug 2004 00:31:12 -0700, ravi wrote:
> which is a best way to free the all the memory used by a hash explain in
> the context of complicated data structures like hash of hashes
>
> undef %hash;
> delete %hash;
> %hash =();
>
> What is the difference between these three
What happened when you read the documentation, specifically:
perldoc -f undef
perldoc -f delete
You might also want to read these:
perldoc -q memory
perldoc -q shrinks
--
Tore Aursand <tore@aursand.no>
"Why shouldn't truth be stranger than fiction? Fiction, after all, has
to make sense." (Mark Twain)
------------------------------
Date: Fri, 13 Aug 2004 18:41:47 +1000
From: Sisyphus <kalinaubears@iinet.net.au>
Subject: Re: How to catch CTRL-C in Windows NT cmd.exe???
Message-Id: <411c7fff$0$16333$5a62ac22@per-qv1-newsreader-01.iinet.net.au>
Solo wrote:
>>
>>It works fine for me in a cmd.exe shell on Windows 2000, and displays
>>the print message. Is that a copy'n'paste of the actual program that's
>>failing on NT ?
>>
>>Cheers,
>>Rob
>
>
>
> Yes, it's an actual cut'n'paste.....
So much for that idea then ...... :-)
What does 'perl -V' report ?
Faik, the difference might be that you are running NT and I'm running
2000 - but, I've not come across such a difference between the 2
operating systems in the past.
Cheers,
Rob
--
To reply by email u have to take out the u in kalinaubears.
------------------------------
Date: 13 Aug 2004 07:40:30 GMT
From: Abigail <abigail@abigail.nl>
Subject: Re: Match inner quotes ?
Message-Id: <slrnchos3e.ohj.abigail@alexandra.abigail.nl>
Abhinav (matrix_calling@yahoo.dot.com) wrote on September MCMXCIII in
<URL:news:oIZSc.1$u23.40@news.oracle.com>:
-- Hi,
--
-- I posted this on comp.editors earlier, so I apologize for this multi-post.
-- However, I thought it would be great if I knew how to perform the following
-- using Perl :
--
-- I have a file with a number of lines like this :
--
-- push @xmlParams,"<?xml version="1.0"?>";
-- ^ ^
-- ^ ^
-- I need to escape the inner quotes i.e, change " to \" - however number of
-- times the quotes may appear.
-- (They will always be balanced, though).
--
-- Any pointers on how to do this ?
That's impossible. If you have a string looking like this:
...."......"....."...."....."...."....
Then they quotes can "balance" in more than one way:
...."......"....."...."....."...."....
1 1 2 2 3 3
...."......\".....\"...."....."...."....
1 1 2 2
...."......\".....\"....\".....\"...."....
1 1
...."......"....."....\".....\"...."....
1 1 2 2
Abigail
--
@_=map{[$!++,$_^$/]}split$²,"\@\x7Fy~*kde~box*Zoxf*Bkiaox";$\="\r";
$|=++$*;do{($#,$=)=(rand@_,rand@_);@_[$#,$=]=@_[$=,$#]}for($*..@_);
for$:($|..@_-$|){for($|..@_-$:){@_[$_-$|,$_]=@_[$_=>$_-$*]if$_[$_][
$¼]<$_[$_-$*][$®];print+map{$_->[$|]}@_;select$·,$°,$½,0.1}}print$/
------------------------------
Date: Fri, 13 Aug 2004 10:45:49 +0300
From: "Eugene Mikheyev" <eam@7ka.mipt.ru>
Subject: Re: Match inner quotes ?
Message-Id: <cfhrkv$1i85$1@news.univ.kiev.ua>
I think he means the following:
"........"........."............"........"........."........".........."
|........1.........1...........2.......2........3.......3..........|
outer outer
But this is going to be very simple
------------------------------
Date: Fri, 13 Aug 2004 08:53:35 -0000
From: "gnari" <gnari@simnet.is>
Subject: Re: Match inner quotes ?
Message-Id: <cfhvef$b9n$1@news.simnet.is>
"Abhinav" <matrix_calling@yahoo.dot.com> wrote in message
news:OQZSc.2$u23.36@news.oracle.com...
>
> perl -npi -e 's/"/\\"/g; s/(.+)(\n*)/ push \@xmlParams,"${1}";${2}/g'
> template.xml
>
> So that I already have the "s escaped properly after the 1st statement.
>
> Ugly, but works .. Would appreciate Other Ways to do it .. especially in a
> single regexp, as my OP required :)
why not: (untested)
perl -pi -e 's/(.+)/ push \@xmlParams,qq(${1});/' template.xml
gnari
------------------------------
Date: 13 Aug 2004 09:28:18 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Match inner quotes ?
Message-Id: <cfi1ji$oks$1@mamenchi.zrz.TU-Berlin.DE>
Abhinav <matrix_calling@yahoo.dot.com> wrote in comp.lang.perl.misc:
> Hi,
>
> I posted this on comp.editors earlier, so I apologize for this multi-post.
> However, I thought it would be great if I knew how to perform the following
> using Perl :
>
> I have a file with a number of lines like this :
>
> push @xmlParams,"<?xml version="1.0"?>";
> ^ ^
> ^ ^
> I need to escape the inner quotes i.e, change " to \" - however number of
> times the quotes may appear.
> (They will always be balanced, though).
>
> Any pointers on how to do this ?
As Abigail has pointed out, the nesting of quotes is ambiguous.
If we re-state the problem as "escape all quotes in a string except
the first and the last one", here is one way:
substr( $x, $+[ 1], $-[ 2] - $+[ 1]) =~ s/"/\\"/g if $x =~ /(").*(")/;
Anno
------------------------------
Date: Fri, 13 Aug 2004 15:33:24 +0530
From: Abhinav <matrix_calling@yahoo.dot.com>
Subject: Re: Match inner quotes ?
Message-Id: <Ns0Tc.10$u23.79@news.oracle.com>
Anno Siegel wrote:
> Abhinav <matrix_calling@yahoo.dot.com> wrote in comp.lang.perl.misc:
>
>>Hi,
>>
>>I posted this on comp.editors earlier, so I apologize for this multi-post.
>>However, I thought it would be great if I knew how to perform the following
>>using Perl :
>>
>>I have a file with a number of lines like this :
>>
>> push @xmlParams,"<?xml version="1.0"?>";
>> ^ ^
>> ^ ^
>>I need to escape the inner quotes i.e, change " to \" - however number of
>>times the quotes may appear.
>>(They will always be balanced, though).
>>
>>Any pointers on how to do this ?
>
>
> As Abigail has pointed out, the nesting of quotes is ambiguous.
Indeed :( Will take care to be accurate and comprehensible in the future.
> If we re-state the problem as "escape all quotes in a string except
> the first and the last one", here is one way:
>
> substr( $x, $+[ 1], $-[ 2] - $+[ 1]) =~ s/"/\\"/g if $x =~ /(").*(")/;
>
Thanks ! Although my problem was solved (and Gnari mentioned the qq
operator which I should have used in the the first place), this will give
me a lot to learn during the coming weeknd :)
------------------------------
Date: 13 Aug 2004 00:50:53 -0700
From: alex522@mailinator.com (alex)
Subject: Re: Module to print out all package variables...?
Message-Id: <90030f0e.0408122350.5fa505f0@posting.google.com>
Douglas Hunter <dug@plusthree.com> wrote in message news:<slrnchn962.1u5.dug@plusthree.com>...
> On 2004-08-12, alex <alex522@mailinator.com> wrote:
> > I'm looking for a module to dump out all (or as much
> > as possible :-) the package variables.
> > ie. something like:
> >
> > Data::Dumper->Dump([ \%:: ], ['\%::']) # Dump the main symbol table
> >
> > ...but which then recursively follows the package name globs's.
> >
> > I couldn't find anything on CPAN, but then i may not
> > have been looking in the right place :-\
>
> Does Devel::Symdump do what you want?
>
Yes! Just what i needed.
Many thanks.
> -- Douglas Hunter
------------------------------
Date: 13 Aug 2004 08:29:12 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Perl PDF modules - help please
Message-Id: <cfhu4o$lro$1@mamenchi.zrz.TU-Berlin.DE>
Andrew DeFaria <Andrew@DeFaria.com> wrote in comp.lang.perl.misc:
> Matt Garrish wrote:
>
> > Please bear in mind that the people you're insulting will never need
> > *your* help with Perl.
>
> How do you know that?
We've seen you perform.
Anno
------------------------------
Date: Fri, 13 Aug 2004 02:22:32 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <0umdnYckjpul8YHcRVn-uA@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.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: Fri, 13 Aug 2004 08:58:54 GMT
From: bowsayge <bowsayge@nomail.afraid.org>
Subject: Re: Reading next line, finding missing number in sequence
Message-Id: <ip%Sc.15073$nx2.7132@newsread2.news.atl.earthlink.net>
Anno Siegel said to us:
[...]
> Arrays use substantially less storage and are a little faster than
> hashes. You may find it instructive to re-write your code to use
> an array.
Yes, it works with an array too.
> Going a step farther in storage conservation, a bit vector could be
> used.
[...]
>
> my $set = '';
> vec( $set, $_, 1) = 1 for @numbers;
> my @missing = grep !vec( $set, $_, 1), $min .. $max;
>
> Again, there isn't much change from your code to this variant.
>
> Anno
Thanks, the vector works like a charm too.
------------------------------
Date: Fri, 13 Aug 2004 11:56:30 +0200
From: Sandman <mr@sandman.net>
Subject: Splitting paragraph into array.
Message-Id: <mr-9AA95B.11563013082004@individual.net>
I am splitting a text block into paragraphs, to be able to add images and stuff
like that to a specific paragraph in a content management system.
Well, right now I'm splittin on two or more newlines, so this text block
(indentation added for clarity):
Hello, my nickname is Sandman and I am coding
some Perl
Call me
Would be split into two parts, with "Call me" being the second one.
My problem now is that if I have a text block like below:
Hello, my nickname is Sandman and I am coding
some Perl. Here is an example:
<code>
print "Hello World!";
print "Foo";
</code>
Call me
The above would, given the rules I use now, yield four parts, as such:
---------------------------------------------
Hello, my nickname is Sandman and I am coding
some Perl. Here is an example:
---------------------------------------------
<code>
print "Hello World!";
---------------------------------------------
print "Foo";
</code>
---------------------------------------------
Call me
---------------------------------------------
But I would want it to end up in three parts, as such:
---------------------------------------------
Hello, my nickname is Sandman and I am coding
some Perl. Here is an example:
---------------------------------------------
<code>
print "Hello World!";
print "Foo";
</code>
---------------------------------------------
Call me
---------------------------------------------
So, basically, what I want to do is to split the text block up with the
delimiter "\n{2,}" but not when it is inside an *unclosed* html tag. Some
examples:
<div class='quote'>
Hello, my nickname is Sandman and I am coding
some Perl. Here is an example:
<code>
print "Hello World!";
print "Foo";
</code>
Call me
</div>
Ends up in:
---------------------------------------------
<div class='quote'>
Hello, my nickname is Sandman and I am coding
some Perl. Here is an example:
<code>
print "Hello World!";
print "Foo";
</code>
Call me
</div>
---------------------------------------------
And
<div class='quote'>
Hello, my nickname is Sandman and I am coding
some Perl. Here is an example:
<code>
print "Hello World!";
print "Foo";
</code>
</div>
Call me
Ends up in:
---------------------------------------------
<div class='quote'>
Hello, my nickname is Sandman and I am coding
some Perl. Here is an example:
<code>
print "Hello World!";
print "Foo";
</code>
</div>
---------------------------------------------
Call me
---------------------------------------------
Hopefully you get the idea.
Any ideas on how to solve it?
--
Sandman[.net]
------------------------------
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 6863
***************************************
