|
From: | Paolo Bonzini |
Subject: | Re: [Help-smalltalk] Including files |
Date: | Tue, 05 Sep 2006 09:18:00 +0200 |
User-agent: | Thunderbird 1.5.0.5 (Macintosh/20060719) |
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 agree with the parallel (but it's the weakness as much as the strength of Smalltalk...)I'm increasingly thinking that a Smalltalk image is most similar to a database instance.
Paolo
[Prev in Thread] | Current Thread | [Next in Thread] |