develooper Front page | perl.perl5.porters | Postings from October 2012

Re: What happened to the whole "small core" idea?

Thread Previous | Thread Next
Leon Timmermans
October 30, 2012 08:06
Re: What happened to the whole "small core" idea?
Message ID:
On Tue, Oct 30, 2012 at 3:34 AM, Ricardo Signes
<> wrote:
>> ...the brilliant strategy championed by Obra (Jesse Vincent)...
> I am at least in part on board with Aristotle's reading of that strategy.  It
> was all about stopping the growth of the language, but about modularizing what
> existed and allowing the language to grow safely, and to be ported to new
> runtimes.

Me too.

>> No new syntax unless there is a massive benefit in adding it, and even then
>> only if it can not be done via a CPAN-distributed extension.
> Those stand in opposition.  :-)  I agree more or less with the second.
> "Massive" is a relative term, and I think the question is its awesomenss mass
> relative to its suck mass.  I love the stuffing out of s///r, and while I
> might not call it a massive benefit, I think it is a huge improvement.  I think
> `package NAME VERSION` was right to add.  Etc.

For me, new core syntax has some simple criteria for inclusion: «they
are small and simple features that make daily programming easier»[1].
say, // and s///r satisfy that for me (smartmatch obviously fails the
small and simple part). I would support signatures in core precisely
because it's something I'd use in any non-trivial program, and because
it's something I can easily explain to a newbie (more so than the
current system).

That doesn't say anything about how it should be implemented. I think
we should always use some kind of hooks when possible, extendability
is the most awesome thing since the invention of the if statement. I
think nowadays say could have been implemented as a keyword plugin. We
don't have pluggable operators yet, but I can imagine them in some
future so features such as // could be developed on CPAN. And given
that we now demand a break between a regexp's modifiers and the
following operator we might actually get away with making parsing
those pluggable too (though I'm not sure that one is really worth the

The future is bright, we just need a can of volunteers to make it to happen ;-)



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