[30855] in Perl-Users-Digest
Perl-Users Digest, Issue: 2100 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Jan 6 06:09:41 2009
Date: Tue, 6 Jan 2009 03:09:05 -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, 6 Jan 2009 Volume: 11 Number: 2100
Today's topics:
Re: -1 ** 0 == -1 ??? <RedGrittyBrick@spamweary.invalid>
Re: Autoflush and new/read-line not working as expected xhoster@gmail.com
Re: Autoflush and new/read-line not working as expected <jimktrains@gmail.com>
Re: hash table usage questions <ced@blv-sam-01.ca.boeing.com>
new CPAN modules on Tue Jan 6 2009 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Why my Strawberry Perl act strangely under MSYS? <WaterLin1999@gmail.com>
Re: Why my Strawberry Perl act strangely under MSYS? <WaterLin1999@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 06 Jan 2009 10:05:35 +0000
From: RedGrittyBrick <RedGrittyBrick@spamweary.invalid>
Subject: Re: -1 ** 0 == -1 ???
Message-Id: <49632cf2$0$30297$da0feed9@news.zen.co.uk>
kj wrote:
>
> kj wrote:
>
>> I can't think of even the faintest justification for this:
>>
>> % perl -le 'print( -1 ** 0 )'
>> -1
>
>> Absolutely horrible! Perl just showed itself wholly unsuitable
>> for any programming that involves numerical computation...
>
>> Still in shock...
>
> OK, egg on my face. I see.
> Sorry,
When startled, I try *not* to jump to the conclusion that whatever
language I am using is wholly unsuitable for any programming that
involves numerical computation.
I have done this for so long that it no longer requires much effort on
my part.
I assume that any programming language older than a few months with
widespread usage is suitable for numeric computation and that any odd
effects I am seeing are due to my own ignorance, stupidity or
foolishness - this has proved to be a good initial assumption. I commend
it to you :-)
--
RGB
------------------------------
Date: 06 Jan 2009 02:15:55 GMT
From: xhoster@gmail.com
Subject: Re: Autoflush and new/read-line not working as expected/documented?
Message-Id: <20090105211648.798$RD@newsreader.com>
jk <jimktrains@gmail.com> wrote:
> Hello, I am trying to write a client-server program. Without going
> into details, I'm simply reading the terminal on the server and
> sending the contents to the client. I'm having an issue where neither
> the client nor server are autoflushing their sockets by default, and
> the client won't readlines from the server, they come as a big chunk
> only after the server fails.
>
> I have the same issue on Mac OS 10.5 (perl: 5.8.8) and Ubuntu (kernel
> 2.6.27) (perl: 5.10.0)
>
>
> socket(SERVER, PF_INET, SOCK_STREAM, getprotobyname('tcp')) or die
> "socket: $!";
I'd recommend using IO::Select, or at least using lexical file handles.
....
>
> If the first autoflush is removed (in the server) no text appears on
> the client if the server is killed. If the autodlush in the client is
> removed, no text appears on the server. Ok, so that's not what the
> docs say (sockets should autoflush, right?)
The only place I know of where the docs say that is in IO::Socket. You
are not using IO::Socket. You are bypassing IO::Socket by invoking
the low-level functions directly instead, so you do not get the behavior
of IO::Socket when you are not using it.
> The other problem is that the print <SOCKET> in the client prints both
> lines, and blocks until the connection is lost. The $line = <CLIENT>
> line in the server correctly returns the first line sent from the
> client, immediately and solely. Why doesn't the client correctly read
> lines from the server, and instead block until the connection is lost.
print imposes a list context on the thing expression it is to print. In
a list context, <SOCKET> will return *all* the lines on the handle, not
just the next one. In order to do that, it will block until it gets an
eof.
Perhaps you meant:
print scalar <SOCKET>;
Xho
--
-------------------- http://NewsReader.Com/ --------------------
The costs of publication of this article were defrayed in part by the
payment of page charges. This article must therefore be hereby marked
advertisement in accordance with 18 U.S.C. Section 1734 solely to indicate
this fact.
------------------------------
Date: Mon, 5 Jan 2009 22:02:24 -0800 (PST)
From: jk <jimktrains@gmail.com>
Subject: Re: Autoflush and new/read-line not working as expected/documented?
Message-Id: <8664dd59-53ff-44fc-8e85-c669686c5358@l38g2000vba.googlegroups.com>
Well, that worked. ::face-palm:: sorry it was a stupid issue.
I misread the IO::Socket page:-\ I should prob switch this over to be
more OO once it works, huh?
Thanks so much,
Jim
------------------------------
Date: Tue, 6 Jan 2009 00:51:35 -0800 (PST)
From: "C.DeRykus" <ced@blv-sam-01.ca.boeing.com>
Subject: Re: hash table usage questions
Message-Id: <2c7f4b64-ba8b-46f6-b7a1-8db41c993c32@o40g2000prn.googlegroups.com>
On Jan 2, 2:45 pm, Uri Guttman <u...@stemsystems.com> wrote:
> >>>>> "x" == xhoster <xhos...@gmail.com> writes:
>
> >> delete @h{ grep !/\.cc$/, keys %h } ;
> >>
> >> that's a bit simpler IMO and definitely should be faster. it also uses
> >> delete with a hash slice which is a combo that should be more well
> >> known.
>
> x> If the OP's worry about size is justified, I'd go with this:
>
> x> /.cc$/ and delete $h{$_} while defined ($_=each %h);
>
> x> As your method builds two in-memory lists, one with all keys and one with
> x> all keys meeting the criteria.
>
> sure that could be faster but it may not be as you think. you make N
> calls to delete and calls to each in a loop. perl ops are the major
> bottleneck in perl speed. if the slice lists are short enough (and they
> could still be pretty long), IMO my solution should be faster. but only
> benchmarking can tell for sure. my method does use more ram but ram is
> cheaper than speed. :)
>
I don't how meaningful just a raw opcode count is but the hash-slice-
delete does have fewer:
perl -MO=Concise -e 'delete @h{ grep !/\.cc$/, keys %h }'|wc -l
17
perl -MO=Concise -e ' /.cc$/ and delete $h{$_} while defined ($_=each
%h);'
25
"Perl Hacks" (#82) cites B::COP timing info to see how long the
opcodes are taking.
--
Charles DeRykus
------------------------------
Date: Tue, 6 Jan 2009 05:42:25 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Tue Jan 6 2009
Message-Id: <KD1Bup.tqn@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Acme-State-0.01
http://search.cpan.org/~swalters/Acme-State-0.01/
Save application state on exit and restores state on startup
----
Acme-State-0.02
http://search.cpan.org/~swalters/Acme-State-0.02/
Save application state on exit and restores state on startup
----
AnyEvent-CouchDB-1.08
http://search.cpan.org/~beppu/AnyEvent-CouchDB-1.08/
a non-blocking CouchDB client based on jquery.couch.js
----
Apache-SWIT-Security-0.09
http://search.cpan.org/~bosu/Apache-SWIT-Security-0.09/
security subsystem for Apache::SWIT
----
Apache2-ASP-2.10
http://search.cpan.org/~johnd/Apache2-ASP-2.10/
ASP for Perl, reloaded.
----
Apache2-AuthEnv-1.2
http://search.cpan.org/~arif/Apache2-AuthEnv-1.2/
Perl Authentication and Authorisation via Environment Variables.
----
App-PPBuild-0.13
http://search.cpan.org/~exodist/App-PPBuild-0.13/
Perl Project Build System, The low-learning curve simple build system.
----
Audio-MPD-0.19.5
http://search.cpan.org/~jquelin/Audio-MPD-0.19.5/
class to talk to MPD (Music Player Daemon) servers
----
AutoLoader-5.68
http://search.cpan.org/~smueller/AutoLoader-5.68/
load subroutines only on demand
----
Catalyst-Plugin-ConfigLoader-0.22
http://search.cpan.org/~bricas/Catalyst-Plugin-ConfigLoader-0.22/
Load config files of various types
----
Catalyst-Plugin-Mode-0.02
http://search.cpan.org/~plcgi/Catalyst-Plugin-Mode-0.02/
select config values depends in your development process
----
Catalyst-View-Seamstress-2.1_01
http://search.cpan.org/~draxil/Catalyst-View-Seamstress-2.1_01/
HTML::Seamstress View Class for Catalyst
----
Class-DBI-Lite-0.018
http://search.cpan.org/~johnd/Class-DBI-Lite-0.018/
Lightweight ORM for Perl
----
ClearPress-295
http://search.cpan.org/~rpettett/ClearPress-295/
Simple, fresh & fruity MVC framework
----
Config-Model-CursesUI-1.102
http://search.cpan.org/~ddumont/Config-Model-CursesUI-1.102/
Curses interface to edit config data
----
Dansguardian-0.1
http://search.cpan.org/~mogaal/Dansguardian-0.1/
Simple module for administer dansguardian's control files.
----
Data-ParseBinary-0.13
http://search.cpan.org/~semuelf/Data-ParseBinary-0.13/
Yet Another parser for binary structures
----
DateTime-Format-Atom-v1.0.0
http://search.cpan.org/~ikegami/DateTime-Format-Atom-v1.0.0/
Parse and format Atom datetime strings
----
DateTime-Format-RFC3339-v1.0.0
http://search.cpan.org/~ikegami/DateTime-Format-RFC3339-v1.0.0/
Parse and format RFC3339 datetime strings
----
Devel-NYTProf-2.07_91
http://search.cpan.org/~timb/Devel-NYTProf-2.07_91/
Powerful feature-rich perl source code profiler
----
Devel-PerlySense-0.0175
http://search.cpan.org/~johanl/Devel-PerlySense-0.0175/
Perl IDE backend with Emacs frontend
----
ExtUtils-Command-1.16
http://search.cpan.org/~rkobes/ExtUtils-Command-1.16/
utilities to replace common UNIX commands in Makefiles etc.
----
ExtUtils-Manifest-1.56
http://search.cpan.org/~rkobes/ExtUtils-Manifest-1.56/
utilities to write and check a MANIFEST file
----
Finance-OFX-Parse-Simple-0.01
http://search.cpan.org/~jjones/Finance-OFX-Parse-Simple-0.01/
Parse a simple OFX file or scalar
----
Finance-PremiumBonds-0.04
http://search.cpan.org/~bigpresh/Finance-PremiumBonds-0.04/
Perl extension to check Premium Bond holder's numbers
----
FramesReady-1.020
http://search.cpan.org/~derhaag/FramesReady-1.020/
a frames-capable version of LWP::UserAgent
----
Graph-ChainBuilder-v0.0.1
http://search.cpan.org/~ewilhelm/Graph-ChainBuilder-v0.0.1/
build directed 2-regular cyclic graphs
----
Graph-ChainBuilder-v0.0.2
http://search.cpan.org/~ewilhelm/Graph-ChainBuilder-v0.0.2/
build directed 2-regular cyclic graphs
----
Gtk2-Ex-Entry-Pango-0.04
http://search.cpan.org/~potyl/Gtk2-Ex-Entry-Pango-0.04/
Gtk2 Entry that accepts Pango markup.
----
Heap-MinMax-0.04
http://search.cpan.org/~mbeebe/Heap-MinMax-0.04/
Perl implementation of a Min-Max Heap
----
Hyper-0.04_01
http://search.cpan.org/~steffenw/Hyper-0.04_01/
The global Hyper Workflow Interface
----
Log-Detect-1.423
http://search.cpan.org/~wsnyder/Log-Detect-1.423/
Read logfiles to detect error and warning messages
----
MP3-Tag-0.9714
http://search.cpan.org/~ilyaz/MP3-Tag-0.9714/
Module for reading tags of MP3 audio files
----
Mac-iTunes-Library-0.3
http://search.cpan.org/~dinomite/Mac-iTunes-Library-0.3/
Perl extension for representing an iTunes library
----
Make-Cache-1.050
http://search.cpan.org/~wsnyder/Make-Cache-1.050/
Caching of object and test run information
----
Math-Cephes-0.47
http://search.cpan.org/~rkobes/Math-Cephes-0.47/
perl interface to the cephes math library
----
Module-Starter-Plugin-CGIApp-0.07
http://search.cpan.org/~jaldhar/Module-Starter-Plugin-CGIApp-0.07/
template based module starter for CGI apps.
----
Nagios-Plugin-0.31
http://search.cpan.org/~tonvoon/Nagios-Plugin-0.31/
A family of perl modules to streamline writing Nagios plugins
----
Net-BitTorrent-0.049
http://search.cpan.org/~sanko/Net-BitTorrent-0.049/
BitTorrent peer-to-peer protocol class
----
POE-Component-Server-SimpleSMTP-1.38
http://search.cpan.org/~bingos/POE-Component-Server-SimpleSMTP-1.38/
A simple to use POE SMTP Server.
----
POE-Component-Server-SimpleSMTP-1.40
http://search.cpan.org/~bingos/POE-Component-Server-SimpleSMTP-1.40/
A simple to use POE SMTP Server.
----
POE-Component-Server-Twirc-0.03
http://search.cpan.org/~mmims/POE-Component-Server-Twirc-0.03/
Twitter/IRC gateway
----
Padre-Plugin-Encode-0.1.1
http://search.cpan.org/~keedi/Padre-Plugin-Encode-0.1.1/
convert file to different encoding in Padre
----
Padre-Plugin-Encode-0.1.2
http://search.cpan.org/~keedi/Padre-Plugin-Encode-0.1.2/
convert file to different encoding in Padre
----
Padre-Plugin-Perl6-0.022
http://search.cpan.org/~azawawi/Padre-Plugin-Perl6-0.022/
Padre plugin for Perl6
----
Parse-Method-Signatures-1
http://search.cpan.org/~ash/Parse-Method-Signatures-1/
Perl6 like method signature parser
----
Queue-Q4M-0.00015
http://search.cpan.org/~dmaki/Queue-Q4M-0.00015/
Simple Interface To q4m
----
Spreadsheet-XLSX-0.08
http://search.cpan.org/~dmow/Spreadsheet-XLSX-0.08/
Perl extension for reading MS Excel 2007 files;
----
Syntax-Highlight-Perl6-0.0297
http://search.cpan.org/~azawawi/Syntax-Highlight-Perl6-0.0297/
Perl 6 Syntax Highlighter
----
SystemC-Vregs-1.461
http://search.cpan.org/~wsnyder/SystemC-Vregs-1.461/
Utility routines used by vregs
----
Test-MockCommand-0.02
http://search.cpan.org/~kyz/Test-MockCommand-0.02/
provide mock results for external commands
----
Tree-AVL-0.05
http://search.cpan.org/~mbeebe/Tree-AVL-0.05/
An AVL (balanced binary) tree for time efficient storage and retrieval of comparable objects
----
Verilog-Readmem-0.04
http://search.cpan.org/~gsullivan/Verilog-Readmem-0.04/
Parse Verilog $readmemh or $readmemb text file
----
WWW-Search-News-1.078
http://search.cpan.org/~mthurn/WWW-Search-News-1.078/
WWW::Search backend for news searches
----
WWW-Tumblr-3.01
http://search.cpan.org/~damog/WWW-Tumblr-3.01/
Perl interface for the Tumblr API
----
Xacobeo-0.05
http://search.cpan.org/~potyl/Xacobeo-0.05/
XPath (XML Path Language) visualizer.
----
ZConf-Runner-0.0.0
http://search.cpan.org/~vvelox/ZConf-Runner-0.0.0/
Run a file using a choosen methode, desktop entry or mimetype.
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
------------------------------
Date: Tue, 06 Jan 2009 08:12:55 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <boE8l.13437$c45.11635@nlpi065.nbdc.sbc.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Mon, 5 Jan 2009 20:53:52 -0800 (PST)
From: Water Lin <WaterLin1999@gmail.com>
Subject: Re: Why my Strawberry Perl act strangely under MSYS?
Message-Id: <e4aa9a68-eb51-49c6-a892-21206cd43936@s9g2000prg.googlegroups.com>
On Jan 6, 12:12=A0am, Bart Lateur <bart.lat...@pandora.be> wrote:
> Water Lin wrote:
> >For there is a script test.pl, the content is:
> >-------------------------------------------------------------
> >print "The steps you can do by this auto-tool:\n";
>
> >$want_test =3D <STDIN>;
> >-------------------------------------------------------------
>
> >If I run this script in Windows cmd or Cygwin, it will print the text
> >"The steps you can do by this auto-tool:".
>
> >But when I try to run this script under MSYS, the console show
> >something like this:
> >-------------------------------------------------------------
> >$ perl test.pl
> >a
> >The steps you can do by this auto-tool:
> >-------------------------------------------------------------
>
> >After run comand "perl test.pl", the console ask me to input
> >immediately. After I input "a", the text is printed.
>
> >It is very strange. The script did right things but just asked me to
> >input something first!
>
> >Who has any idea about this?
>
> Google for "suffering from buffering".
>
> Likely adding this to the top of your script will fix it:
>
> =A0 =A0 =A0 =A0 $| =3D 1;
>
> --
> =A0 =A0 =A0 =A0 Bart.
It's fixed. Thanks
------------------------------
Date: Mon, 5 Jan 2009 22:21:41 -0800 (PST)
From: Water Lin <WaterLin1999@gmail.com>
Subject: Re: Why my Strawberry Perl act strangely under MSYS?
Message-Id: <05231453-c2d5-4129-8854-b1ab434a8b1f@v39g2000pro.googlegroups.com>
On Jan 6, 12:12=A0am, Bart Lateur <bart.lat...@pandora.be> wrote:
> Water Lin wrote:
> >For there is a script test.pl, the content is:
> >-------------------------------------------------------------
> >print "The steps you can do by this auto-tool:\n";
>
> >$want_test =3D <STDIN>;
> >-------------------------------------------------------------
>
> >If I run this script in Windows cmd or Cygwin, it will print the text
> >"The steps you can do by this auto-tool:".
>
> >But when I try to run this script under MSYS, the console show
> >something like this:
> >-------------------------------------------------------------
> >$ perl test.pl
> >a
> >The steps you can do by this auto-tool:
> >-------------------------------------------------------------
>
> >After run comand "perl test.pl", the console ask me to input
> >immediately. After I input "a", the text is printed.
>
> >It is very strange. The script did right things but just asked me to
> >input something first!
>
> >Who has any idea about this?
>
> Google for "suffering from buffering".
>
> Likely adding this to the top of your script will fix it:
>
> =A0 =A0 =A0 =A0 $| =3D 1;
>
> --
> =A0 =A0 =A0 =A0 Bart.
I also want a way if I don't need to add $| =3D 1 at the beginning of
script.
Is it possible to fix it without modify script?
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 2100
***************************************
