[32263] in Perl-Users-Digest
Perl-Users Digest, Issue: 3530 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Oct 28 14:09:27 2011
Date: Fri, 28 Oct 2011 11:09: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 Fri, 28 Oct 2011 Volume: 11 Number: 3530
Today's topics:
Re: Does plack work with perlbal? <gavcomedy@gmail.com>
Re: Does plack work with perlbal? <ben@morrow.me.uk>
graphing with annotations <eric@fruitcom.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
using module <ela@yantai.org>
Re: using module <tadmc@seesig.invalid>
Re: using module <rweikusat@mssgmbh.com>
Re: using module <ben@morrow.me.uk>
Re: using module <rweikusat@mssgmbh.com>
Re: using module <rweikusat@mssgmbh.com>
Re: using module <ben@morrow.me.uk>
Re: using module <ben@morrow.me.uk>
Re: using module <rweikusat@mssgmbh.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 28 Oct 2011 03:56:50 -0700 (PDT)
From: gavino <gavcomedy@gmail.com>
Subject: Re: Does plack work with perlbal?
Message-Id: <11097508.1093.1319799410406.JavaMail.geo-discussion-forums@prlk36>
ok so perlbal will load balance to starman? ok
------------------------------
Date: Fri, 28 Oct 2011 09:30:49 -0500
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: Does plack work with perlbal?
Message-Id: <j6KdncrCHrIEITfTnZ2dnUVZ8rCdnZ2d@bt.com>
[This is Usenet, not some Web forum. Please quote properly, and please
learn to write in sentences, with capitals and punctuation.]
Quoth gavino <gavcomedy@gmail.com>:
> ok so perlbal will load balance to starman? ok
Well, of *course* it will. Starman is just an HTTP server like any
other.
Ben
------------------------------
Date: 28 Oct 2011 15:45:10 GMT
From: Eric smith <eric@fruitcom.com>
Subject: graphing with annotations
Message-Id: <slrnjaljga.ip5.eric@pepper.fruitcom.com>
Hi
Are there any perl modules or interfaces that allow arbitrary
annotations and timestamping of line graphs like the google API's
do?
I have tried the gnuplot interface, Chart::Clicker and SVG::Graph so far and
cannot find this functionality.
Any suggestions where I can find the most modern functionality in perl graphing?
Thanks
--
Eric Smith
------------------------------
Date: Fri, 28 Oct 2011 02:28:25 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <gtGdnYTAJ6IExDfTnZ2dnUVZ5hidnZ2d@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: Fri, 28 Oct 2011 18:54:37 +0800
From: "ela" <ela@yantai.org>
Subject: using module
Message-Id: <j8e1lc$d94$1@ijustice.itsc.cuhk.edu.hk>
Somebody has already written a module called abc.pm wherein subroutine def
is to invoke from my main program.
I'd appreciate an example of the necessary lines because errors like "method
cannot be found" keep appearing...
in abc.pm, do I need "require Export"?
in main.pl, should I write "use abc" and then "abc::def"?
------------------------------
Date: Fri, 28 Oct 2011 07:49:37 -0500
From: Tad McClellan <tadmc@seesig.invalid>
Subject: Re: using module
Message-Id: <slrnjal84f.u6e.tadmc@tadbox.sbcglobal.net>
ela <ela@yantai.org> wrote:
> Somebody has already written a module called abc.pm
Somebody should change the name of their module.
Lowercase module names are reserved by convention for pragmas.
> wherein subroutine def
> is to invoke from my main program.
>
> I'd appreciate an example of the necessary lines
That depends on how abc.pm was written.
Since we cannot see how abc.pm was written, we cannot help.
> because errors like
You should copy and paste the *actual* error message.
Have you seen the Posting Guidelines that are posted here frequently?
> "method
> cannot be found" keep appearing...
I cannot find that message in perldiag.pod,
so it is not coming from perl.
> in abc.pm, do I need "require Export"?
That depends on how abc.pm was written.
Since we cannot see how abc.pm was written, we cannot help.
> in main.pl, should I write "use abc" and then "abc::def"?
What happened when you tried it?
--
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: Fri, 28 Oct 2011 13:55:58 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: using module
Message-Id: <877h3pjmw1.fsf@sapphire.mobileactivedefense.com>
"ela" <ela@yantai.org> writes:
> Somebody has already written a module called abc.pm wherein subroutine def
> is to invoke from my main program.
>
> I'd appreciate an example of the necessary lines because errors like "method
> cannot be found" keep appearing...
If it is really 'method', that would mean that you are trying to
invoke a subroutine via 'OO syntax', CLASS->method() or $obj->method()
and this method doesn't exist.
> in abc.pm, do I need "require Export"?
>
> in main.pl, should I write "use abc" and then "abc::def"?
The standard boilerplate (ignoring any attempts at covering the
mechanics of the Perl object model with "syntactic molasses" because it
looks so .... DIFFERENT !!1 [*]).
in the module (assuming it is not supposed to be used as a class)
package abc;
require Exporter; # ensure that Exporter is there
our @ISA = qw(Exporter); # declare that it's a superclass
our @EXPORT_OK = qw(sub1 sub2 sub2) # list exportable subroutines
in the 'other file using it':
use abc qw(sub2 sub3); # list of actually imported subs
[*] This is actually one of these rare strokes of genius, as nicely
exemplified by the fact that about everyone and his dog has been able
to hush it up in order to make his favority pet language look better in
comparison in a different way for more than a decade.
------------------------------
Date: Fri, 28 Oct 2011 09:24:24 -0500
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: using module
Message-Id: <j6KdncvCHrKFJjfTnZ2dnUVZ8rCdnZ2d@bt.com>
[Please wrap your articles at 72 characters. Tabs are 8 columns wide,
and best avoided altogether in Usenet posts.]
Quoth Rainer Weikusat <rweikusat@mssgmbh.com>:
>
> require Exporter; # ensure that Exporter is there
> our @ISA = qw(Exporter); # declare that it's a superclass
Inheriting from Exporter is no longer best practice. Non-ancient
versions of Exporter (5.57, with perl 5.8.3) will export 'import', so
you can say
use Exporter "import";
instead and avoid inheriting a whole lot of random internal Exporter
methods you didn't want.
> [*] This is actually one of these rare strokes of genius, as nicely
> exemplified by the fact that about everyone and his dog has been able
> to hush it up in order to make his favority pet language look better in
> comparison in a different way for more than a decade.
There are often sound reasons for setting up inheritance at compile
time, which is rather ugly if using @ISA directly. Modern code should
use 'parent' rather than 'base' for this, since base.pm does a lot of
heavy stuff to make fields.pm work (which you shouldn't be using any
more either).
It's also worth pointing out that it's not a good idea to mess around
with @ISA too much. There's a lot of rather ponderous magic attached to
it, which can get awfully slow if you keep pulling classes in and out of
the list, and in at least some versions of perl some important method-
resolution bugs that don't happen if you only set @ISA once. (Sorry for
being vague, but I can't remember the details. Search p5p if you're
interested: IIRC it was something to do with mro_method_changed_in, not
terribly long after the release of 5.10.)
Ben
------------------------------
Date: Fri, 28 Oct 2011 15:52:51 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: using module
Message-Id: <87mxcl2mnw.fsf@sapphire.mobileactivedefense.com>
Ben Morrow <ben@morrow.me.uk> writes:
> Quoth Rainer Weikusat <rweikusat@mssgmbh.com>:
>>
>> require Exporter; # ensure that Exporter is there
>> our @ISA = qw(Exporter); # declare that it's a superclass
>
> Inheriting from Exporter is no longer best practice.
> Non-ancient versions of Exporter (5.57, with perl 5.8.3) will export
> 'import', so you can say
>
> use Exporter "import";
>
> instead and avoid inheriting a whole lot of random internal Exporter
> methods you didn't want.
This would be more appropriately reworded as "I [meaning, you] (and
presumably some set of other people [who summarily confused enough
that they think that 'modern', whose actual meaning is 'currently
fashionable', would be 'surely positive enough' to make any actual
argument in favor of such an opinion redundant]) happen to be of the
opinion that this shouldn't be done".
And my reply to that would be: It's documented and it works and I've
been using it in this way since the times of perl 5.003. So what's the
compelling reason to change it?
>> [*] This is actually one of these rare strokes of genius, as nicely
>> exemplified by the fact that about everyone and his dog has been able
>> to hush it up in order to make his favority pet language look better in
>> comparison in a different way for more than a decade.
>
> There are often sound reasons for setting up inheritance at compile
> time,
Should I encounter one in code I write, I will consider doing so. But
this hasn't happened in the past sixteen odd years. OTOH, something
I've done fairly often is defining a set of related classes in a
single file, moving some or all of them to different files as the
code evolved and the classes became more complex. Or loading all
modules from some top-level file because of more complex
interdepedencies among them and just declaring inheritance
relationships in the modules.
------------------------------
Date: Fri, 28 Oct 2011 15:57:09 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: using module
Message-Id: <87ipn92mgq.fsf@sapphire.mobileactivedefense.com>
Rainer Weikusat <rweikusat@mssgmbh.com> writes:
[...]
> I've been using it in this way since the times of perl 5.003. So
> what's the compelling reason to change it?
Loosely related remark: I'm a content use of the Perl programming
language. I'm not the least of a fan of "download stuff from the
internet to get shit done fast" since I don't do "shit".
------------------------------
Date: Fri, 28 Oct 2011 10:31:57 -0500
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: using module
Message-Id: <_uKdnZBaKrlwVzfTnZ2dnUVZ7rKdnZ2d@bt.com>
Quoth Rainer Weikusat <rweikusat@mssgmbh.com>:
> Ben Morrow <ben@morrow.me.uk> writes:
> > Quoth Rainer Weikusat <rweikusat@mssgmbh.com>:
> >>
> >> require Exporter; # ensure that Exporter is there
> >> our @ISA = qw(Exporter); # declare that it's a superclass
> >
> > Inheriting from Exporter is no longer best practice.
> > Non-ancient versions of Exporter (5.57, with perl 5.8.3) will export
> > 'import', so you can say
> >
> > use Exporter "import";
> >
> > instead and avoid inheriting a whole lot of random internal Exporter
> > methods you didn't want.
>
> This would be more appropriately reworded as "I [meaning, you] (and
> presumably some set of other people [who summarily confused enough
^^ are
And I don't think you can use 'summarily' like that.
> that they think that 'modern', whose actual meaning is 'currently
> fashionable',
The 'actual meaning' (insofar as that term has any actual meaning when
dealing with linguistics) of 'modern' is 'Now existing; of or pertaining
to the present and recent times; originating in the current age or
period'. Nothing whatever to do with 'fashionable'.
I am inclined to agree that I find chromatic et al.'s use of 'Modern
Perl' to mean 'Perl written according to current best practices; more
generally Perl treated as a serious programming language rather than a
quick hack' a bit trite, but there we are. The ideas they are attempting
to promote are good ones, so the terminology is not really important.
> would be 'surely positive enough' to make any actual
> argument in favor of such an opinion redundant]) happen to be of the
> opinion that this shouldn't be done".
>
> And my reply to that would be: It's documented and it works and I've
> been using it in this way since the times of perl 5.003. So what's the
> compelling reason to change it?
I gave a good reason: inheriting from Exporter causes you to also
inherit a whole lot of other methods which you don't want and shouldn't
call. *You* may not happen to find it compelling, but if I had been
writing solely for your benefit I would have written a private email.
Another reason, less good, is that the amount of work perl has to do
when you change @ISA is affected by the number of subs defined in that
package, so setting it early is more efficient.
> >> [*] This is actually one of these rare strokes of genius, as nicely
> >> exemplified by the fact that about everyone and his dog has been able
> >> to hush it up in order to make his favority pet language look better in
> >> comparison in a different way for more than a decade.
> >
> > There are often sound reasons for setting up inheritance at compile
> > time,
>
> Should I encounter one in code I write, I will consider doing so. But
> this hasn't happened in the past sixteen odd years.
Fair enough, but that's no reason to be disparaging about the tools that
are useful when it *is* necessary. You should also bear in mind that,
while it isn't always *necessary* to set up inheritance at compile time,
it's very rarely *harmful*, so making a habit of it would not be a bad
idea.
I had a bug in a program just the other day caused by not setting up
inheritance at compile timei. It was a Catalyst app, and Cat's method
attributes don't work properly if the inheritance isn't set up yet.
> OTOH, something
> I've done fairly often is defining a set of related classes in a
> single file, moving some or all of them to different files as the
> code evolved and the classes became more complex. Or loading all
> modules from some top-level file because of more complex
> interdepedencies among them and just declaring inheritance
> relationships in the modules.
parent.pm has a -norequire option for exactly this situation, though
I've never had reason to use it. In any case: there's nothing wrong with
setting @ISA directly when that's a helpful thing to do. There *is*
something wrong with encouraging people to belive that helpers like
parent.pm are in some way superflous or harmful.
Ben
------------------------------
Date: Fri, 28 Oct 2011 10:37:39 -0500
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: using module
Message-Id: <_uKdnZNaKrneUTfTnZ2dnUVZ7rKdnZ2d@bt.com>
Quoth Rainer Weikusat <rweikusat@mssgmbh.com>:
> Rainer Weikusat <rweikusat@mssgmbh.com> writes:
>
[use Exporter "import" vs inheriting]
>
> > I've been using it in this way since the times of perl 5.003. So
> > what's the compelling reason to change it?
>
> Loosely related remark: I'm a content use of the Perl programming
ed ^^ ^^ r
> language. I'm not the least of a fan of "download stuff from the
> internet to get shit done fast" since I don't do "shit".
How *entirely* fascinating.
What does that have to do with Exporter?
Ben
------------------------------
Date: Fri, 28 Oct 2011 16:59:48 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: using module
Message-Id: <87bot12jkb.fsf@sapphire.mobileactivedefense.com>
Ben Morrow <ben@morrow.me.uk> writes:
> Quoth Rainer Weikusat <rweikusat@mssgmbh.com>:
[...]
> I am inclined to agree that I find chromatic et al.'s use of 'Modern
> Perl' to mean 'Perl written according to current best practices; more
> generally Perl treated as a serious programming language rather than a
> quick hack' a bit trite,
And what I find more than 'a bit trite' is this 'opinion
marketing'. "Serious" and "how I would have done it" are two very much
different things.
I'm going to ignore the rest of this since you are just repeating
yourself.
------------------------------
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 3530
***************************************
