It's a result of a vision/capability mismatch within Parrot.
The vision is that parrot is a stable, mature product that is ready to
release, and all changes are small, incremental enhancements. Thus,
there's this deprecation policy that hangs like a boat anchor on various
bits, and requires that no changes be introduced that might cause
Parrot's support for vital languages like brainfuck and lolcode to falter.
Since nqp-rx has substantially different semantics than nqp (there's a
wiki page that lists some of the differences on parrot.org) patrick
would either be stuck trying to shoe-horn both sets of semantics into
the same language, or be stuck trying to implement some kind of
backwards compatibility mode. Unless he made "nqp" and "nqp-rx" separate
things. Even then, if any other changes to nqp-rx occur there's still
the dread boat-anchor to fear.
Unless nqp-rx is an external project. In which case there's no
deprecation boat-anchor, and he can safely be encouraged to make
positive useful changes with whatever extremely limited time he has. At
the cost of maintaining a separate code repository, of course. :-)
=Austin
Gerd Pokorra wrote:
Why lives 'nqp-rx' at ext/nqp-rx in the parrot sources and on github at
http://github.com/perl6/nqp-rx?
It looks like a main PCT so I think it should only be placed and
maintained in the parrot sources.
-- Gerd
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
