develooper Front page | perl.perl5.porters | Postings from December 2016

Re: Should we bring in Module::Runtime into core?

Thread Previous | Thread Next
Aaron Priven
December 6, 2016 15:50
Re: Should we bring in Module::Runtime into core?
Message ID:
It seems to me there’s a difference between bringing something into core that deals with a wart in the language, and a whole new facility like or Moose. Module::Runtime is basically just a way of getting around the syntax of the “require” function, right? You can specify a module as a bareword or a file as a string, but there’s no way to specify a module as a regular string. It’s easy to imagine a better interface for “require” that would make Module::Runtime unnecessary, were it not for backwards compatibility.  Given that, it seems reasonable to bring in Module::Runtime (and justify bringing in things like Scalar-List-Utils) without opening up the core to every new framework.

Aaron Priven,,

> On Dec 5, 2016, at 9:10 AM, Aristotle Pagaltzis <> wrote:
> A few years back there was an oft-cited sort-of rule (but maybe more of
> an aspiration) that we should only have modules in core that are needed
> to build perl itself or to install modules from CPAN.

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About