To digress slightly: what I've been daydreaming about is having the
Read-Eval-Print loop implemented in a Smalltalk process. That way, you
could substitute another method of interaction (like, say, something
listening on a port), kill the REP, and restart the image with the new
interface only. At the moment, you have to supply a script to the image
that will suspend the REP.
Don't daydream. :-)
Instead, what we should do is to provide a small C interface to readline
-- all that's needed actually (at least to start) is the functions
readline() and add_history(), or a wrapper that does both -- so that the
REP loop could use a ReadlineStream, a StdinStream, an
EmacsInteractionStream, and so on...
I'm increasingly thinking that a Smalltalk image is most similar to a
database instance.
I agree with the parallel (but it's the weakness as much as the strength
of Smalltalk...)
Paolo
_______________________________________________
help-smalltalk mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-smalltalk
