unrepl

discussing specification of an edn-based repl and its implementations.
richiardiandrea 2017-05-26T04:36:01.922637Z

Nice, so I am thinking it now in terms of pipable repl exposing to the world only two streams, one in and one out. Each one is responsible for evaluating its part of the stream without exposing parser and eval, and the terminal of this exhaust system is stdout 😀

richiardiandrea 2017-05-26T04:37:25.931405Z

I mean no rocket science here I know 😀 However there are fewer things to add to the unrepl protocol if the only communication medium between repls are pipes

richiardiandrea 2017-05-26T04:38:30.938310Z

I probably now get in full what you had in mind all along 😅

cgrand 2017-05-26T16:47:42.915003Z

Yeah maybe. And upgrading a repl is just the matter of sending a specific input.

richiardiandrea 2017-05-26T17:10:32.362540Z

yep the protocol stays the same, the "engine" can just pipe the streams when an upgrade is requested

cgrand 2017-05-26T17:14:00.428366Z

All this upgrade stuff vaguely reminds me of Alan Kay and alien "objects".

cgrand 2017-05-26T20:16:37.718674Z

Ah. I may have found a way to solve the "async eval" problem without committing to a dynvars impl. Yet another indirection:-)

1👍21