Yes, this is what I was referring to. Hotswapping is sort of there for the jvm. When I use Eclipse, it tries to hotswap. Sometimes it fails. Sometimes it doesn't. But, referring the criteria in my reply to Ron's email, would loosing guaranteed hotswapping cause Squeak to "lose it's soul?" I dunnknow. I'm a newbie. And I don't write Squeak for a living.
But in a Java environment I can tell you it isn't that bad. And it's downsides could be mitigated so long as Squeak/JVM could provide some runtime mechanism to register some services to begin at startup(like Commanche, etc). Maybe this would be a tolerable compromose to most Squeak developers if it provides more opportunities to use Squeak in the wider world and enlarges it's user base.
But I don't have a clue about #become. What does it do?
On 11/8/06, Klaus D. Witzel klaus.witzel@cobss.com wrote:
Hi Mike,
if by "more message oriented opcode" you mean Gilad Bracha's Invokedynamic opcode
this is not sufficient for full Smalltalk/Squeak. Though it may be sufficient for scripting languages (languages in which, usually, types are unknown at compile-time).
What is also needed is full "hotswapping"
and support for Smalltalk's #become: ...
But, perhaps, you had something else in mind?
/Klaus
On Wed, 08 Nov 2006 16:55:50 +0100, Michael Kohout wrote:
I suppose this is more of a pie in the sky type question, but with the changes coming to the Java virtual machine in version 7, where the jvm itself provides a more message oriented opcode, has any consideration gone into perhaps porting squeak to run on the jvm?
I'm aware of talks2 but it seems as if development on that effort(based on the public releases/news) is at a standstill.
thanks Mike Kohout
Beginners mailing list Beginners@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/beginners