On Wed, May 31, 2017 at 09:33:59AM -0400, Brock Wilcox wrote:
> One of my dreams is to adopt a client/server + middleware model from nREPL
> (clojure) which I think works really well, and likely to do that in
> userspace as a regular module. Moving everything into REPL.pm (perl6
> instead of nqp)
> Do you have something specific in mind?
I don't know enough about the internals to have any particular suggestions.
Keeping functions properly local is just one of those "motherhood and
apple pie" principles that is much easier to follow if it is done
consistently from the start.
Some progress on this has already been made, which is how it got as close
to standalone as it is now -- previously the REPL was more NQP than Rakudo.
Do you have something specific in mind?
One of my dreams is to adopt a client/server + middleware model from nREPL
(clojure) which I think works
I was not proposing that the REPL was to be invoked in any other way
than at present. By "reducing the coupling", I mean arranging
functions and interfaces in a way that prevents a change in one
function affecting the other. Essentially, implementing standard
interfaces between complete functions.
Please do not weaken the link between REPL and perl6 !
The ability to test perl6 snippets very quickly is something I find very
useful. And to get this I type 'perl6'. Easy to remember.
(I have been following perl6 since the very beginning, and installed
'pug'. Since perl6 has been
