[32229] in Perl-Users-Digest
Perl-Users Digest, Issue: 3494 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Sep 9 11:09:23 2011
Date: Fri, 9 Sep 2011 08:09:04 -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, 9 Sep 2011 Volume: 11 Number: 3494
Today's topics:
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: R and Perl <dsfqsdf@poupidoup.com>
Re: R and Perl <jondk@FAKE.EMAIL.net>
Re: What to return in scalar context ? <nospam-abuse@ilyaz.org>
Re: What to return in scalar context ? (Randal L. Schwartz)
Re: Where is man page for the types and function used i <rweikusat@mssgmbh.com>
Re: Why does sort return undef in scalar context ? <tzz@lifelogs.com>
Re: Why does sort return undef in scalar context ? <nospam-abuse@ilyaz.org>
Re: Why does sort return undef in scalar context ? <rweikusat@mssgmbh.com>
Re: Why does sort return undef in scalar context ? <nospam-abuse@ilyaz.org>
Re: Why does sort return undef in scalar context ? <rweikusat@mssgmbh.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 09 Sep 2011 02:21:24 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <0v2dneKCZ6fpI_TTnZ2dnUVZ5qOdnZ2d@giganews.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.9 $)
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_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.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Thu, 08 Sep 2011 08:40:52 +0200
From: azrazer <dsfqsdf@poupidoup.com>
Subject: Re: R and Perl
Message-Id: <j49o1j$86t$1@speranza.aioe.org>
Le 08/09/2011 00:26, ccc31807 a écrit :
> On Sep 6, 3:03 am, azrazer<dsfq...@poupidoup.com> wrote:
>> Could you be a bit more precise about what you want to do.
>
> I have multiple data files that I will retrieve from a database query.
> These will be on the order of 150K rows, and an indeterminate number
> of columns. The columns will include both dates and status codes, and
> I will need to build a data structure containing the cumulative count
> of status codes over several months, day by day. Then, I need to build
> graphical files with line charts.
Well yes, this is easily done using R, you just have to aggregate data
(don't you ?). (using aggregate/ddply)
>
> This is currently done by hand in Excel, and I have been tasked with
> automating the process.
>
> Munging the data and getting the cumulative count per status code per
> day is a snap in Perl, and while I've generated charts in Perl using
> GD::Graph, using R is certainly a lot easier, and besides, I am
> motivated to learn R.
Yes, don't worry this will be a piece of cake too, once your data is
well organised.
>
>> AFAIK, from experience, the best thing to do would be to format your
>> data using Perl without making any modification on your data
>
> The raw data needs to be processed. The 'data' that I will use will be
> contained in hashes, the keys will be status codes, the sub keys will
> be dates, and the values will be integers, sort of like this:
>
> $hash{S}{20110601} => 10
> $hash{S}{20110602} => 13
> $hash{S}{20110603} => 21
> $hash{S}{20110604} => 19
> $hash{S}{20110605} => 25
> $hash{S}{20110606} => 29
> $hash{S}{20110607} => 28
>
> So, I can print out the hash in an R compatible data frame and use it
> directly to generate a PDF.
Yup, just generate a CSV file that will be loaded by R and that will be
it, don't you think ?
>
>> Could you be more precise about why you cannot use perl to generate the
>> input data for R ? --and if so, why calling system() is a problem
>
> I will use Perl to munge the data and produce as output an input file
> for R. I want to be able to push a button and have the computer do all
> the work.
Looks like a decent way of doing things => let the computer work ! :)
have fun,
>
> Thanks for your reply, CC.
------------------------------
Date: Fri, 09 Sep 2011 02:27:27 -0400
From: Jon Du Kim <jondk@FAKE.EMAIL.net>
Subject: Re: R and Perl
Message-Id: <c6be5$4e69b1d0$ad30ae40$9779@news.eurofeeds.com>
If you have existing R code that you would like to
interface with than some sort of perl/R bridge makes sense.
But, you do know that perl has a fantastically awesome
set of libraries known as Perl Data Language (PDL)?
http://pdl.perl.org/
I have used the PDL Stats modules and they work well
for what I was up to. Check them out too.
http://pdl-stats.sourceforge.net/
Not sure what you are using R for but you can keep it
all Perl if you want to...
On 9/2/11 6:26 PM, ccc31807 wrote:
> Has anyone used R with Perl for statistical programming?
>
> Has anyone used R with Perl to output graphical files?
>
> Is it any more complicated than writing R scripts and calling the R
> interpreter using system() or the like?
>
> I'm about to embark on a major project with R, and really, really need
> Perl to munge my data files. I would like to automate the entire
> thing, but if I can't I can use Perl to generate the input data for R
> and manually generate the output files.
>
> Thanks, CC.
------------------------------
Date: Thu, 8 Sep 2011 15:24:48 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: What to return in scalar context ?
Message-Id: <slrnj6hni0.bot.nospam-abuse@panda.math.berkeley.edu>
On 2011-09-05, Keith Thompson <kst-u@mib.org> wrote:
> merlyn@stonehenge.com (Randal L. Schwartz) writes:
>>>>>>> "Ilya" == Ilya Zakharevich <nospam-abuse@ilyaz.org> writes:
>> Ilya> If there are SEVERAL things which may be all EXPECTED to be
>> Ilya> "logically deducible" (possibly by DIFFERENT PEOPLE) - it was
>> Ilya> decided to be an "unwanted situation". This is called "the
>> Ilya> principle of least surprise".
>>
>> The actual answer is "whatever was most logical *to Larry*". Any other
>> answer isn't paying attention to history.
Then your recollections of history are very different from mine.
Larry did not have much (practically any?) DIRECT influence on what
has happened after some moment - I think about 1996. (Of course, his
legacy had - in particular "this principle of least surprise".)
And Perl of today has very little resemblance to what it was in 1996.
(Enough to say that in 1996 most of my Perl programming time was spent
fighting bugs in Perl.)
I suspect the return value of sort() in scalar context was discussed
many times on p5p after that "cut-off". The current situation has very
little to do with Larry's decisions (although the end result may
coincide with what it was in Perl 4).
Sorry for my fuzzy memory,
Ilya
------------------------------
Date: Fri, 09 Sep 2011 06:28:38 -0700
From: merlyn@stonehenge.com (Randal L. Schwartz)
Subject: Re: What to return in scalar context ?
Message-Id: <868vpxalq1.fsf@red.stonehenge.com>
>>>>> "Ilya" == Ilya Zakharevich <nospam-abuse@ilyaz.org> writes:
Ilya> Then your recollections of history are very different from mine.
Ilya> Larry did not have much (practically any?) DIRECT influence on what
Ilya> has happened after some moment - I think about 1996. (Of course, his
Ilya> legacy had - in particular "this principle of least surprise".)
sort in a scalar context was established from the moment sort was added
to Perl... and I seem to recall it being in Perl version 1.
Ilya> And Perl of today has very little resemblance to what it was in 1996.
Ilya> (Enough to say that in 1996 most of my Perl programming time was spent
Ilya> fighting bugs in Perl.)
Ilya> I suspect the return value of sort() in scalar context was discussed
Ilya> many times on p5p after that "cut-off". The current situation has very
Ilya> little to do with Larry's decisions (although the end result may
Ilya> coincide with what it was in Perl 4).
Agreed, but that's only because there wasn't any strong consensus, and I
bet if anyone really cared, Larry would still have been consulted.
--
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.posterous.com/ for Smalltalk discussion
------------------------------
Date: Thu, 08 Sep 2011 20:26:46 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Where is man page for the types and function used in perlembed?
Message-Id: <87vct2q1hl.fsf@sapphire.mobileactivedefense.com>
Peng Yu <pengyu.ut@gmail.com> writes:
> I want to learn details on how to embed perl in C or C++. But I don't
> see the man pages for the types and function used in perlembed? Does
> anybody know?
Try perlguts, perlapi and perlintern.
------------------------------
Date: Thu, 08 Sep 2011 07:04:11 -0500
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Why does sort return undef in scalar context ?
Message-Id: <87ipp3me9w.fsf@lifelogs.com>
On Sun, 4 Sep 2011 15:09:58 +0000 (UTC) Willem <willem@toad.stack.nl> wrote:
W> Ted Zlatanov wrote:
W> ) Specifically there is *no way* to get the sort-p information (boolean or
W> ) float) without calling sort(), which is either stupid or wasteful
W> ) depending on your point of view. sort-p is useful on its own and
W> ) merging it with the sort() scalar context is what I don't want. So I
W> ) think it's worth putting it in Perl 5 or 6 if that's not too difficult.
W> Can't you create it with the reduce() function in List::Util ?
I guess, but that's not much better because it still involves a lot of
Perl. I'm talking about a built-in at the C level that can amortize
what the interpreter knows about the list (e.g. inserting an element out
of order in a sorted list decreases the "sortedness" while inserting it
in the right place maintains it).
Ted
------------------------------
Date: Thu, 8 Sep 2011 15:28:21 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: Why does sort return undef in scalar context ?
Message-Id: <slrnj6hnok.bot.nospam-abuse@panda.math.berkeley.edu>
On 2011-09-04, Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
> Similar to these 'tiny functions', a single XS routine supposed to
> demonstrate a specific property of perl hardly warrants creating a
> complete extension module,
Why? Especially if creating this module takes one very short line of
code (and testing it another line), and your instructions take pages...
> especially not when it is supposed to be
> part of a USENET posting as this would be rather unwieldy.
I posted exactly because I found YOUR post unwieldy.
Hope this helps,
Ilya
------------------------------
Date: Thu, 08 Sep 2011 20:25:42 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Why does sort return undef in scalar context ?
Message-Id: <87zkieq1jd.fsf@sapphire.mobileactivedefense.com>
Ilya Zakharevich <nospam-abuse@ilyaz.org> writes:
> On 2011-09-04, Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>> Similar to these 'tiny functions', a single XS routine supposed to
>> demonstrate a specific property of perl hardly warrants creating a
>> complete extension module,
>
> Why? Especially if creating this module takes one very short line of
> code (and testing it another line), and your instructions take
> pages...
>
>> especially not when it is supposed to be
>> part of a USENET posting as this would be rather unwieldy.
>
> I posted exactly because I found YOUR post unwieldy.
So, do you think I should have posted a tar-file of the directory tree
created by h2xs, complete with detailed documentation enabling
someone who doesn't already know his way about that to understand what
is where for which reason inside there, instead, and after these pages
of unrelevant code and meta-information and unrelevant explanation of
that, finally gotten to 'assuming you manged to follow me up to here,
you can now add these six lines here and that three lines there so you
can see what I was trying to show you'?
In this case, I'd say your definition of 'unwieldy' is rather
strange.
------------------------------
Date: Fri, 9 Sep 2011 00:08:33 +0000 (UTC)
From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
Subject: Re: Why does sort return undef in scalar context ?
Message-Id: <slrnj6im81.cfs.nospam-abuse@panda.math.berkeley.edu>
On 2011-09-08, Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>> I posted exactly because I found YOUR post unwieldy.
>
> So, do you think I should have posted a tar-file of the directory tree
> created by h2xs, complete with detailed documentation enabling
> someone who doesn't already know his way about that to understand what
> is where for which reason inside there, instead, and after these pages
> of unrelevant code and meta-information and unrelevant explanation of
> that, finally gotten to 'assuming you manged to follow me up to here,
> you can now add these six lines here and that three lines there so you
> can see what I was trying to show you'?
Of course not. Just replace 90% of YOUR pages of instructions by two lines
h2xs OPTIONS
and
perl Makefile.PL && make test
Ilya
------------------------------
Date: Fri, 09 Sep 2011 01:28:55 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Why does sort return undef in scalar context ?
Message-Id: <8739g64kzc.fsf@sapphire.mobileactivedefense.com>
Ilya Zakharevich <nospam-abuse@ilyaz.org> writes:
> On 2011-09-08, Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
>>> I posted exactly because I found YOUR post unwieldy.
>>
>> So, do you think I should have posted a tar-file of the directory tree
>> created by h2xs, complete with detailed documentation enabling
>> someone who doesn't already know his way about that to understand what
>> is where for which reason inside there, instead, and after these pages
>> of unrelevant code and meta-information and unrelevant explanation of
>> that, finally gotten to 'assuming you manged to follow me up to here,
>> you can now add these six lines here and that three lines there so you
>> can see what I was trying to show you'?
>
> Of course not. Just replace 90% of YOUR pages of instructions by two lines
>
> h2xs OPTIONS
>
> and
>
> perl Makefile.PL && make test
I'm somewhat tempted to post the output generated by trying to execute
these two commands as they stand there :->. And I can even shorten
this somewhat: Instead of giving a complete set of instructions how to
reproduce what I had been doing, (hopefully) including enough detail
information to enable someone who read them to understand what
precisely was supposed to be going on there and why it was supposed to
going on there, I could just have resorted to Uri's "I know
better. Don't ask why or how".
But that wasn't what I was trying to do.
------------------------------
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:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#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 3494
***************************************
