The `meta` module continues its experimentation. The documentation does
say "it's experimental", but likely it needs some actual runtime
warnings adding to that effect.
It seems the usual style would be for various functions and initial
access points to print warnings in some category that can be silenced,
allowing the developer to accept the experimental nature of it.
The question becomes: What should that warning category be? Two obvious
thoughts come to mind:
* It could be `meta::experimental`, as its own module:
use meta;
no warnings 'meta::experimental';
...
* It could borrow an area of core and be `experimental::meta`
use meta;
no warnings 'experimental::meta';
In this latter idea, it would casually lead users to think that they
could combine the whole lot by perhaps doing
use experimental 'meta';
However, as experimental.pm currently stands, that would not work. It
would have to be modified to recognise that "meta" is the name of a
brand new module that it ought to load first, to then disable the
warning category. I'm not entirely sure about the feel of this, as it
starts to conflate the idea of simple named features (as per
`use feature ...`) and entire new modules - which in any case for older
perls would just be installed from CPAN in the usual manner for
external modules.
Likely the first idea is best.
Does anyone have any thoughts here?
--
Paul "LeoNerd" Evans
leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/
say "it's experimental", but likely it needs some actual runtime
warnings adding to that effect.
It seems the usual style would be for various functions and initial
access points to print warnings in some category that can be silenced,
allowing the developer to accept the experimental nature of it.
The question becomes: What should that warning category be? Two obvious
thoughts come to mind:
* It could be `meta::experimental`, as its own module:
use meta;
no warnings 'meta::experimental';
...
* It could borrow an area of core and be `experimental::meta`
use meta;
no warnings 'experimental::meta';
In this latter idea, it would casually lead users to think that they
could combine the whole lot by perhaps doing
use experimental 'meta';
However, as experimental.pm currently stands, that would not work. It
would have to be modified to recognise that "meta" is the name of a
brand new module that it ought to load first, to then disable the
warning category. I'm not entirely sure about the feel of this, as it
starts to conflate the idea of simple named features (as per
`use feature ...`) and entire new modules - which in any case for older
perls would just be installed from CPAN in the usual manner for
external modules.
Likely the first idea is best.
Does anyone have any thoughts here?
--
Paul "LeoNerd" Evans
leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS
http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/