App::Prove plugins, options, etc

[Eric Wilhelm]

# from David Golden
# on Thursday 04 October 2007 12:20:

>On 10/4/07, Andy Armstrong <n at rciss.us> wrote:
>> a small namespace and the potential for collisions is great. What is
>> the objection to using the same syntax Perl uses? :
>>
>> $ prove -MSome::Extension=colour,pink -rb
>
>Or just a generic "define" option that plugs key/value pairs into a
>hash.  Plugins should try not to overload existing plugins keywords,
>but there's nothing mandated -- it's up to the user to ensure plugins
>play well together
>
>$ prove -MSome::Plugin -MSome::Other::Plugin -D archive_file=foo.txt
>-D color=yes

Ow!  My eyes, head, and fingers ache just looking at it.

Yes, there's a potential for collision, but I hope we can resolve it 
without inflicting *that* much pain on the user.

Perhaps extensions need to register their switches upon installation.

Maybe we simply disallow short options for plugins (or throw-out all 
conflicting ones.)

We can certainly do better than "anything requiring the user to type a 
colon."

--Eric
-- 
As an old bass player friend of mine used to say: throw money, don't 
clap.
--Tony Parisi
---------------------------------------------------
    http://scratchcomputing.com
---------------------------------------------------