[prev] [thread] [next] [lurker] [Date index for 2003/04/01]
On Mon, Mar 31, 2003 at 02:16:01PM +0100, Richard Clamp said:
>
> =head2 decide what to do about $Plugin::DESCRIPTION;
>
> it's a bit of a sore thumb now that everything else is very OO, maybe
> provide it as $class->description, or part of $class->options (maybe
> with a rename to $class->options)
I think putting it in $class->options is a bad idea because you're
arbitarily preventing a plugin from having an option called description.
Not a big deal but it's just messy.
I think $class->description();
Now whether we do it by automatically looking for $DESCRIPTION or just
forcing them to write
sub description { "My description here" }
is left up to the list to decide.
> $class->require;
>
> which seems at little clearer
Forgive my addled brain (I curse you Insomnius, Evil Lord of NoSleep)
but does this still require (no pun intended) an eval
eval {
$class->require;
};
etc etc
Simon
--
it's a short link to a dead king
Generated at 13:56 on 01 Jul 2004 by mariachi 0.52