David Golden said:
On Thu, Oct 26, 2017 at 11:29 AM, Chad Granum <exodi...@gmail.com> wrote:
I have a small objection to putting an alt module in a namespace other
than alt: It is less obvious. If I see Alt::Thing I will simply know it
will replace Thing.
Consider, too, if someone else wants to another alternative Thing.
Alt::Thing2 -- is that a second Alt::Thing? Or an alternative of Thing2?
Possibly namespacing like Thing::Alt::Boring would then allow
Thing::Alt::Spiffy, etc. But I don't want to have explicit rules about
this. I think intent is more important.
Would adding a field to the META spec about API conformance solve some this?
api_conforms_to:
module: CPAN::Thing
version: 2.61
- Salve (possibly opening a can of worms here)
--
#!/usr/bin/env perl
sub AUTOLOAD{$AUTOLOAD=~/.*::(\d+)/;seek(DATA,$1,0);print# Salve Joshua Nilsen
getc DATA}$"="'};&{'";@_=unpack("C*",unpack("u*",':50,$'.# <s...@foo.no>
'3!=0"59,6!`%%P\0!1)46%!F.Q`%01,`'."\n"));eval "&{'@_'}"; __END__ is near! :)
