Maybe Pharo 2.0 could be refactored like this, enough to do to get to V 1.0 though ;-)
Regards, Gary ----- Original Message ----- From: "Michael Rueger" <[email protected]> To: <[email protected]> Sent: Wednesday, May 27, 2009 5:42 PM Subject: Re: [Pharo-project] Pharo-min? > [email protected] wrote: > >> I'm interested in building a minimum image from a Pharo-core base. This >> image would have: >> >> - no GUI/mouse/keyboard. The only interface would be via network >> connections. >> >> - no processes/interrupts. The network send/receive would be synchronous >> via a plugin. >> >> - no timer. The date/time would be via a plugin on demand. >> >> - no fallback debugger. Any error fallback would log a message and abort >> via a plugin. >> >> - possibly a minimal interpreter that didn't include any support for >> those unavailable features. (The only value in this would be smaller >> size and hopefully something more comprehensible for code auditing >> purposes.) > > Part of this is already covered by Pavel's minimal morphic/image work. > > - no timer > there is a difference between date/time and the delay/timing framework > in the VM. Removing the latter could be "interesting" > > Everything else you could basically do by creating new Socket classes, > changing default error handling etc. > Although I'm not quite sure what you would gain from not using the green > threads in Squeak/Pharo? > > > Michael > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
