Front page | perl.perl5.porters |
Postings from December 2016
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 CGI.pm 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, aaron@priven.com, www.priven.com/aaron > On Dec 5, 2016, at 9:10 AM, Aristotle Pagaltzis <pagaltzis@gmx.de> 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