[27817] in Perl-Users-Digest
Perl-Users Digest, Issue: 9181 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Apr 20 14:05:47 2006
Date: Thu, 20 Apr 2006 11:05:07 -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 Thu, 20 Apr 2006 Volume: 10 Number: 9181
Today's topics:
Re: clpmisc posting guidelines question <tadmc@augustmail.com>
Re: How to find uploaded data size from content-length <sherm@dot-app.org>
Re: How to find uploaded data size from content-length <sherm@dot-app.org>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 20 Apr 2006 10:15:42 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: clpmisc posting guidelines question
Message-Id: <slrne4f9cu.ais.tadmc@magna.augustmail.com>
Nico Coetzee <blabla@yourguess.com> wrote:
>
> Recently ("autoincrement hex numbers" thread) an argument was started
> between what to use first as a solution to a problem: a Perl built-in or
> a CPAN module.
>
> Yet, in FAQ 4.45 (as an example, because it was posted recently) a
> simple solution is provided by using the CPAN module first, then
> explaining how to do it in "pure" Perl.
>
> Now I am curious... What do we actually use first when giving advice? Do
> we need to explain "why" we actually prefer a certain piece of advice
> above another? Is it necessary to "defend" an option, or should we not
> rather just make another suggestion (not putting it forward as "better")?
>
> Sorry in advance if this was covered before - I have read
> http://www.catb.org/~esr/faqs/smart-questions.html and
> http://www.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.text but I
> must admit I did not really find the answers to the above questions, but
> if I'm wrong please correct me.
I'm having having trouble identifying what your "posting guidelines question"
is. As its maintainer, I feel a responsibility to see that the question
gets addressed, but I can't figure out what the question is.
Are you asking if something about builtin vs module should be added
to the guidelines?
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Thu, 20 Apr 2006 12:46:44 -0400
From: Sherm Pendley <sherm@dot-app.org>
Subject: Re: How to find uploaded data size from content-length
Message-Id: <m2bquww5xn.fsf@Sherm-Pendleys-Computer.local>
Asterbing <no@thanks.com> writes:
> In article <m21wvt5mxl.fsf@Sherm-Pendleys-Computer.local>, sherm@dot-
> app.org says...
>> Don't read from stdin. Read from the filehandle you get from CGI.pm.
>>
> I don't use CGI.pm
Why on earth not? Do you enjoy pain?
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: Thu, 20 Apr 2006 12:59:25 -0400
From: Sherm Pendley <sherm@dot-app.org>
Subject: Re: How to find uploaded data size from content-length
Message-Id: <m2y7y0uqs2.fsf@Sherm-Pendleys-Computer.local>
Asterbing <no@thanks.com> writes:
> I've seen and rewritten my own. A matter of courtesy to not 'copy' : in
> my mind, two ways only : I use a module or I just take a look of their
> algorithm (idea), but never copy (steal)
I suppose you rewrote perl too, using a C compiler you rewrote? What about
the web server, and the operating system? You wouldn't want to "steal" those
either, now would you?
Idiot.
*plonk*
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
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 9181
***************************************
