[22705] in Perl-Users-Digest
Perl-Users Digest, Issue: 4926 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri May 2 09:05:51 2003
Date: Fri, 2 May 2003 06:05:09 -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, 2 May 2003 Volume: 10 Number: 4926
Today's topics:
Re: built in function 'map' examples? <REMOVEsdnCAPS@comcast.net>
Re: built in function 'map' examples? (Sam Holden)
Re: DBD-Pg issue (Bryan Castillo)
Re: Equivalent for ksh select? <simon.oliver@nospam.umist.ac.uk>
Re: Forms structure (Sam Holden)
Re: Forms structure <tassilo.parseval@rwth-aachen.de>
Re: Help: Save Search Terms in an Array? (Tad McClellan)
Hep serving Gif please <spamsucks@noemail.com>
Re: how to disable Lingua::EN::NameParse print to stdou (Anno Siegel)
Memory leak with perl_parse() <rajiyer@persistent.co.in>
Re: Newbie Problem: Cannot see result of .pl (Helgi Briem)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: quotemeta matching problem (Lars)
Using system("xx") to call a binary. How to answer its <SeeMessageBody@nospam.com>
Re: What is the best software to run for an aspiring Pe <mgjv@tradingpost.com.au>
Re: What is the best software to run for an aspiring Pe (Helgi Briem)
Re: What is the best software to run for an aspiring Pe (Anno Siegel)
Re: Why Lisp sucks ( Re: Announcement: The regex coach <bobx@linuxmail.org>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 02 May 2003 04:48:01 -0500
From: "Eric J. Roode" <REMOVEsdnCAPS@comcast.net>
Subject: Re: built in function 'map' examples?
Message-Id: <Xns936F3AFDC6B87sdn.comcast@216.166.71.239>
-----BEGIN xxx SIGNED MESSAGE-----
Hash: SHA1
sholden@flexal.cs.usyd.edu.au (Sam Holden) wrote in
news:slrnbb2bv4.nc5.sholden@flexal.cs.usyd.edu.au:
> On Thu, 1 May 2003 08:02:58 -0500,
> Barry Kimelman <barryk2@SPAM-KILLER.mts.net> wrote:
>> The following line of code uses "map" to find the length of the
>> longest element in an array :
>>
>> $maxlen = (reverse sort { $a <=> $b} map { length $_ } @lines)[0];
>
> $maxlen=undef;
> for (@lines) {$maxlen=length if !defined $maxlen || $maxlen < length}
Why make the conditional more complex than it needs to be?
my $maxlen;
for (@lines) {$maxlen = length if $maxlen < length};
- --
Eric
print scalar reverse sort qw p ekca lre reh
ts uJ p, $/.r, map $_.$", qw e p h tona e;
-----BEGIN xxx SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32) - WinPT 0.5.13
iD8DBQE+sj7IY96i4h5M0egRAq05AKD8AfuEHi12ILNmNP3ZLZXUjQidTgCeN0uT
mwe6Rs7Zleb27Nvt8gCW+b8=
=8E5H
-----END PGP SIGNATURE-----
------------------------------
Date: 2 May 2003 09:54:07 GMT
From: sholden@flexal.cs.usyd.edu.au (Sam Holden)
Subject: Re: built in function 'map' examples?
Message-Id: <slrnbb4g1v.5b0.sholden@flexal.cs.usyd.edu.au>
On Fri, 02 May 2003 04:48:01 -0500,
Eric J. Roode <REMOVEsdnCAPS@comcast.net> wrote:
> -----BEGIN xxx SIGNED MESSAGE-----
> Hash: SHA1
>
> sholden@flexal.cs.usyd.edu.au (Sam Holden) wrote in
> news:slrnbb2bv4.nc5.sholden@flexal.cs.usyd.edu.au:
>
>> On Thu, 1 May 2003 08:02:58 -0500,
>> Barry Kimelman <barryk2@SPAM-KILLER.mts.net> wrote:
>>> The following line of code uses "map" to find the length of the
>>> longest element in an array :
>>>
>>> $maxlen = (reverse sort { $a <=> $b} map { length $_ } @lines)[0];
>>
>> $maxlen=undef;
>> for (@lines) {$maxlen=length if !defined $maxlen || $maxlen < length}
>
> Why make the conditional more complex than it needs to be?
>
> my $maxlen;
> for (@lines) {$maxlen = length if $maxlen < length};
Because I was originally doing minimum before I actually read the original
example and changed it :)
--
Sam Holden
------------------------------
Date: 2 May 2003 00:51:37 -0700
From: rook_5150@yahoo.com (Bryan Castillo)
Subject: Re: DBD-Pg issue
Message-Id: <1bff1830.0305012351.66a83066@posting.google.com>
> > am struggling with the DBD-Pg installation almost 3 weeks. Please
> > somebody out there could help me. Thank you in advance.
> >
> > I have installed the following on WINDOWS XP:
> > CYGWIN
> > POSTGRESQL 7.3.1
> > APACHE 2.0.43
> > ACTIVESTATE PERL 5.8
^
|
You have Active State Perl (5.8) installed?
> > DBI 1.35 (Installed using cygwin)
> > DBD-Pg 1.22 (Installed using cygwin perl makefile.pl, make, make test,
> > and make install)
^
|
And you have perl for cygwin installed?
> >
> > I have no problem in running the following script in CYGWIN:
> >
> > #!/perl/bin/perl -w
> > BEGIN {
> > push(@INC, 'C:/cygwin/lib/perl5/site_perl/5.6.1/cygwin-multi');
Trying to force ActiveState Perl 5.8 to use your
modules built under cygwin?
> > }
> > use DBI;
> > use DBD::Pg;
> > print "Content-type: text/html\n\n";
> > print "hi";
> >
> > However, I cannot run this using the browser. I get the following
> > error.
> >
> > Can't load 'C:/cygwin/lib/perl5/site_perl/5.6.1/cygwin-multi/auto/DBD/Pg/Pg.dll'
This is a binary file compiled for cygwin using perl 5.6.1
> > for module DBD::Pg:load_file:The specified module could not be found
> > at C:/Perl/lib/DynaLoader.pm line 229.
This Dynaloader is from ActiveState version 5.8
> >
> > What am I doing wrong? Why this works in CYGWIN but not in browser?
I think you are mixing stuff you shouldn't be. It works in cygwin,
because you are using the correct version of perl for the correct
DBD::Pg module. Under the web server you are using ActiveStates perl
(a different version too).
Try setting the top line of your script to:
#!C:/cygwin/bin/perl.exe
Or you might install DBD::PgPP under ActiveStates 5.8 using ppm.
------------------------------
Date: Fri, 02 May 2003 08:13:49 +0100
From: Simon Oliver <simon.oliver@nospam.umist.ac.uk>
Subject: Re: Equivalent for ksh select?
Message-Id: <3EB21AAD.5070406@nospam.umist.ac.uk>
Gregg Dameron wrote:
> "Simon Oliver" <simon.oliver@nospam.umist.ac.uk> wrote
>
> Speaking of width: I'm hoping to get this tool running on both Solaris
> (xterm) and Win2K (in a command prompt window). I know a couple of ways to
> get the xterm's width, but I'm clueless in Win2K. How would I determine the
> terminal width there? I found Win32::Console in CPAN - is that the best
> place to start?
Yes, either use the Window() method for screen coordinates or the Size()
method for the buffer size.
use Win32::Console;
my $c = Win32::Console->new(STD_OUTPUT_HANDLE);
printf "Left:%d Top:%d Right:%D Bottom:%d\n", $c->Window;
printf "Buffer Size: x:%d y:%d\n", $c->Size;
--
Simon Oliver
------------------------------
Date: 2 May 2003 06:46:35 GMT
From: sholden@flexal.cs.usyd.edu.au (Sam Holden)
Subject: Re: Forms structure
Message-Id: <slrnbb452b.2v2.sholden@flexal.cs.usyd.edu.au>
On 2 May 2003 06:15:19 GMT,
Tassilo v. Parseval <tassilo.parseval@rwth-aachen.de> wrote:
> Also sprach Sam Jesse:
>
>> and what is the differnet between CGI and GUI?
>
> The former stands for 'common gateway interface'. It is a convention how
> two (or possibly more) networked computers interact with each other.
> Most commonly this is a client machine with a webbrowser on one side and
> the webserver on the other.
No it isn't.
CGI defines the interface between two processes. Essentially it defines
the values of some environment variables, the command line of the process,
and the formatting/content of standard input and output for the process.
In practice CGI is the interface used between a web server and a cgi script,
the web browser has no part in CGI (all it uses is HTTP with the web server).
--
Sam Holden
------------------------------
Date: 2 May 2003 12:19:17 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: Forms structure
Message-Id: <b8tno5$345$1@nets3.rz.RWTH-Aachen.DE>
Also sprach Sam Holden:
> On 2 May 2003 06:15:19 GMT,
> Tassilo v. Parseval <tassilo.parseval@rwth-aachen.de> wrote:
>> Also sprach Sam Jesse:
>>
>>> and what is the differnet between CGI and GUI?
>>
>> The former stands for 'common gateway interface'. It is a convention how
>> two (or possibly more) networked computers interact with each other.
>> Most commonly this is a client machine with a webbrowser on one side and
>> the webserver on the other.
>
> No it isn't.
>
> CGI defines the interface between two processes. Essentially it defines
> the values of some environment variables, the command line of the process,
> and the formatting/content of standard input and output for the process.
There is no contradiction between your and my explanation (so far).
Anything that works for a network will also work locally between
processes. A process is not much different from a program so if two
programs (or processes) agree on using the CGI specs for communication,
they are free to do so.
> In practice CGI is the interface used between a web server and a cgi script,
> the web browser has no part in CGI (all it uses is HTTP with the web server).
Yet the CGI specifications make references to parts of the HTTP protocol
so that is where the client comes in. In theory CGI could also use a
protocol other than HTTP (of course, that would be impractical).
Anyway, I am not arguing. CGI is happening server-wise with the client
often not even knowing that CGI-actions take place so you are right.
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, 2 May 2003 07:32:23 -0500
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: Help: Save Search Terms in an Array?
Message-Id: <slrnbb4pan.3e8.tadmc@magna.augustmail.com>
entropy123 <email_entropy123@yahoo.com> wrote:
> if ($line =~ /\s(Fred)\s/) {
That will not match when
$line = 'Fred Flintstone';
You probably should be using a word boundary instead:
if ($line =~ /\b(Fred)\b/) {
> while (<>) {
> $line = $_;
If you want the line in $line, then put the line in $line:
while ( $line = <> ) {
but if you are a clever Perl programmer then you'll probably
need this instead:
while ( my $line = <> ) {
> foreach (@name) {
> if ($line =~ /\s($name[$i])\s/) {
foreach has put the names into $_ for you, but you never use $_.
foreach gives you the _values_, not the indexes:
if ($line =~ /\b($_)\b/) {
Look Ma! No explicit indexing!
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Fri, 02 May 2003 12:40:29 GMT
From: "Topspin" <spamsucks@noemail.com>
Subject: Hep serving Gif please
Message-Id: <0Htsa.1927$q_6.325@news.randori.com>
I'm running the latest ActiveState Perl on Windows 98 running an Apache 2.0
server.
I'm calling a Perl script via the browser and passing it the filename of a
gif I want it to retrieve. At first, nothing was returned, then upon
someone's recommendation, I added binmode to my code. This appears to be an
improvement, but the gifs are still not completing. I get about 10% of the
top of the gif. The next few lines of the gif are distorted, then the rest
is blank. Using the same code but changing the line:
print "Content-type: image/gif\n\n";
to...
print "Content-type: application/pdf\n\n";
I attempted to serve a PDF. Adobe Reader declares that the PDF has been
damaged and can not be repaired. Both the gif and pdf are just fine as I
have viewed them many times natively. Here is the problematic code. This
code works fine on Unix; I just can't get it to work on Windows.
open (CODE, "$file.gif") || ¬found;
print "Content-type: image/gif\n\n";
binmode CODE;
print <CODE>;
close (CODE);
exit;
------------------------------
Date: 2 May 2003 11:34:57 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: how to disable Lingua::EN::NameParse print to stdout?
Message-Id: <b8tl51$61q$1@mamenchi.zrz.TU-Berlin.DE>
Bing Du Test <bing-du@tamu.edu> wrote in comp.lang.perl.misc:
> This is perl, v5.6.1 built for sun4-solaris.
> Lingua::EN::NameParse version 1.18.
>
> Lingua::EN::NameParse has 'print' in it. It spits the following stuff
> when the module is called in my script.
>
> Assembling with: <blah blah>
> Name = <Lingua::EN::NameParse=HASH(0x3e5f4)>, input_string = < blah
> blah>
>
> I don't want to modify Lingua::EN::NameParse.pm itself. Anyway to
> disable the above module outputs?
How are you calling it? Neither Lingua::EN::NameParse.pm nor
NameGrammar.pm contain any obvious print() or warn() statements, nor
does Parse::RecDescent (which is used by Lingua::EN::NameParse).
Anno
------------------------------
Date: Fri, 2 May 2003 15:54:38 +0530
From: "Rajalakshmi Iyer" <rajiyer@persistent.co.in>
Subject: Memory leak with perl_parse()
Message-Id: <b8tgo8$d886n$1@ID-191561.news.dfncis.de>
Hi,
This question is regarding embedded perl. (Calling Perl functions from C++
Code).
Is there a memory leak associated with the perl_parse call?
I read that by default, perl does not take care of explicitly cleaning up
all the memory it has allocated (such as global memory arenas). Setting
PERL_DESTRUCT_LEVEL to a non-zero value tells perl to do the complete
cleanup.
However, when I do that, the program crashes with the error " Attempt to
free non-existent shared string at (null) line 10 during a global
destruction".
Can anybody help with this?
Regards,
Rajalakshmi Iyer
------------------------------
Date: Fri, 02 May 2003 10:56:06 GMT
From: helgi@decode.is (Helgi Briem)
Subject: Re: Newbie Problem: Cannot see result of .pl
Message-Id: <3eb24eb6.1886626625@news.cis.dfn.de>
On Thu, 01 May 2003 18:28:32 -0700, Michael Eric Battle
<you.gotta@be.kidding.com> wrote:
>Top posted. (Though you did put some stuff at the bottom as well.)
>Quoted a loooong message which has no relevance to your post.
>
>So my sweeping generalization stands:
>Outrage lusers _always_ top post above a quote
>of the _entire_ message that they're responding to.
>
>And I'll ask you, if you're annoyed by it:
>Does Outrage _require_ this, or not?
Not.
--
Regards, Helgi Briem
helgi DOT briem AT decode DOT is
------------------------------
Date: Fri, 02 May 2003 02:22:20 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <dmCdneYgYdoxgS-jXTWcoA@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: 2 May 2003 05:15:02 -0700
From: rispalt@yahoo.se (Lars)
Subject: Re: quotemeta matching problem
Message-Id: <7787ec4b.0305020415.3284a79c@posting.google.com>
Works!
Thanks!!!
------------------------------
Date: Fri, 02 May 2003 07:18:04 GMT
From: "John" <SeeMessageBody@nospam.com>
Subject: Using system("xx") to call a binary. How to answer its prompt with y or n?
Message-Id: <MYosa.49880$ey1.4619019@newsread1.prod.itd.earthlink.net>
My Perl program runs from a command line prompt (on Windows, using Active
Perl). I am using system() to call another program (binary) that prompts
for y/n. ('y' is always the proper reply.)
Is there a way to get my Perl script to reply to the prompt (so I don't have
to) and just keep on running?
--
------------------------------------------------
Feel free to mail me: workingstiff19
...and that's at hotmail.
------------------------------
Date: Fri, 02 May 2003 07:06:51 GMT
From: Martien Verbruggen <mgjv@tradingpost.com.au>
Subject: Re: What is the best software to run for an aspiring Perl programer?
Message-Id: <slrnbb468b.3gj.mgjv@verbruggen.comdyn.com.au>
On Thu, 01 May 2003 19:33:45 GMT,
Thaddeus L. Olczyk <olczyk@interaccess.com> wrote:
> On 1 May 2003 05:57:16 -0700, dalgould@hotmail.com (dalgould) wrote:
>
>>>
>>> Ok. My best advice is stopaspiring. Not just on Perl
>>> but on programming altogether. You just don't have
>>> the intelligence.
>>>
>>
>>Why does someone always have to be a smartass? Your posting shows
>>more of a lack of intelligence. Everyone has to have a starting point
>>on another programming language. Your 15 minutes worth really shows.
>>
>
> My 15 minutes will get people started on the problem.
>
> Why do stupid people always try to be programmers?
Why do people who know too little to realise they don't know much,
always act like they know everything?
> You don't have
> basic problem solving skills you shouldn't be a programmer. If stupid
> people didn't try to be programmers, then there would be less buggy
> software written and mangers wouldn't be moving programming shops
> to India and China.
If lazy people who can't be arsed to write robust code didn't try to
be programmers, then there would be less buggy software written.
I'm not even going to dignify the rest of your ridiculous rant with a
response.
Martien
--
|
Martien Verbruggen |
Trading Post Australia | Curiouser and curiouser, said Alice.
|
------------------------------
Date: Fri, 02 May 2003 09:09:21 GMT
From: helgi@decode.is (Helgi Briem)
Subject: Re: What is the best software to run for an aspiring Perl programer?
Message-Id: <3eb235a6.1880209989@news.cis.dfn.de>
On Thu, 01 May 2003 05:54:15 GMT, olczyk@interaccess.com
(Thaddeus L. Olczyk) wrote:
>Ok. My best advice is stopaspiring. Not just on Perl
>but on programming altogether. You just don't have
>the intelligence.
What an arrogant little monkey you are.
*PLONK*
--
Regards, Helgi Briem
helgi DOT briem AT decode DOT is
------------------------------
Date: 2 May 2003 12:49:49 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: What is the best software to run for an aspiring Perl programer?
Message-Id: <b8tphd$61q$2@mamenchi.zrz.TU-Berlin.DE>
Thaddeus L. Olczyk <olczyk@interaccess.com> wrote in comp.lang.perl.misc:
> On Thu, 1 May 2003 06:22:26 -0500, tadmc@augustmail.com (Tad
> McClellan) wrote:
>
> >> You just don't have
> >> the intelligence.
> >
> >
> >Bullshit.
> >
> >Ignorance does not imply a lack of intelligence.
[retort snipped]
(It would have been more convincing if you hadn't misspelled "ignorange"
and "intellegent".)
> >> open OUTPUT,">testscript.sh";
> >
> >
> >You should always, yes *always*, check the return value from open():
> >
> > open OUTPUT, '>testscript.sh' or die "could not open 'testscript.sh' $!";
> >
> >most especially when you aspire to instructing others on how to do it.
> >
> This makes me wonder about you.
>
> The first ( and obvious ) question is if you should *always* check the
> return value from open(), then why doesn't open require that you do
> so? It would be easy for the implementors to make it so that the
> language requires it: open HANDLE,FILENAME,DIESTATEMENT
> . They don't, so it is not something that you should *always* check
> for.
For someone so proud of his intelligence you rely much on the authority
of others.
Also, you fail to realize that "checking" doesn't necessarily mean
"dying on failure". There are more ways to react on a failed open().
[rest of rant snipped]
Anno
------------------------------
Date: Fri, 02 May 2003 09:57:46 GMT
From: "Bob X" <bobx@linuxmail.org>
Subject: Re: Why Lisp sucks ( Re: Announcement: The regex coach )
Message-Id: <uirsa.7434$hT2.4184417@news2.news.adelphia.net>
"Edi Weitz" <edi@agharta.de> wrote in message
news:87ade6e504.fsf@bird.agharta.de...
> olczyk@interaccess.com (Thaddeus L. Olczyk) writes:
>
<snp>
> Sure. Where else would you want me to post it? alt.asshole-factory?
> rec.pets.ferrets? talk.bizarre?
>
Hey leave the ferrets out! ; )
------------------------------
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 4926
***************************************
