[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: the yearly flurry of email messages...
- To: Hans-Martin Mosner <hmm2@xxxxxxx>
- Subject: Re: the yearly flurry of email messages...
- From: John Ohno <john.ohno@xxxxxxxxx>
- Date: Fri, 11 Feb 2011 13:26:32 -0500
- Cc: Hans-Martin Mosner <hmm@xxxxxxx>, udanax@xxxxxxxxxx
- In-reply-to: <qxnwecr8vj41x64bcr5o1u1v.1297405665288@xxxxxxxxxxxxxxxxx>
- References: <qxnwecr8vj41x64bcr5o1u1v.1297405665288@xxxxxxxxxxxxxxxxx>
Are you planning to translate the code in X to proper squeak, and then
rewrite the C++ pieces?
On Fri, Feb 11, 2011 at 1:27 AM, Hans-Martin Mosner <hmm2@xxxxxxx> wrote:
> My current plan is to extract the objects from the gold image and graft them onto a squeak image. As of today, I can read objects from the various regions of the image file. My code does not handle oldSpace/newSpace #become: yet, but that will be done later today.
> I don't know for sure which way I will go from there - my hope is that I can recompile the methods to Squeak's bytecode and "just run" the code. The devil is in the details :-)
> roger gregory <roger@xxxxxxxxxx> schrieb:
>>Sounds great, Âone proviso, I haven't seen an emulator for the sparc1 that includes everything necessary, especially the display.
>>On Feb 10, 2011, at 12:54 AM, Craig Latta wrote:
>>> Hi Hans-Martin!
>>> Â Â I'm delighted to contribute to the flurry. :)
>>> Â Â I have all the extant bits and pieces from back in the day (and
>>> even the SPARCstation hardware it ran on)... but... yes, the ParcPlace
>>> stuff is the sticking point. Udanax Gold runs on ParcPlace Objectworks
>>> Smalltalk circa 1988, and the nominal latest-and-greatest version I got
>>> from Roger Gregory crashes the Objectworks virtual machine.
>>> Â Â I need the virtual machine sources so I can debug. I had a
>>> conversation going about it with James Robertson and Georg Heeg several
>>> years ago, but it fizzled out. Perhaps you could revive that part of
>>> things. :) ÂOf course, this would be with the current appropriate people
>>> (if any :). James has since left what-used-to-be-ParcPlace for greener
>>> (golder?) pastures.
>>> Â Â Some background for those who are not familiar, or forgot, or have
>>> blotted it out... ;) ÂI first heard about Ted and the Xanadu team when I
>>> was working at ParcPlace in 1992, when Ted came to Stanford to give a
>>> talk. I read Gary Wolf's infamous Wired article on the project in
>>> 1995. In 1999, when I was at Interval Research, I met Ted, Roger,
>>> Mark, and Andrew at the O'Reilly Open Source Conference in Monterey,
>>> where they announced Udanax Green and Gold.
>>> Â Â I contacted Roger after that to see about getting Gold running
>>> again. I came over to his place and we spelunked his garage for old disk
>>> drives, CPUs, memory, etc. I got as far as watching Objectworks crash on
>>> a SPARCstation 10 on my dining room table, then joined in the grand
>>> tradition of Waiting For The Next Victim. :) ÂCurse you, day jobs!
>>> Â Â I live in Amsterdam now. The hardware is in a storage space in
>>> California, so not terribly convenient, but the bits are all right here.
>>> If Roger (or whomever) doesn't mind I'm happy to share them. Hopefully
>>> we don't really need the hardware anymore, because there are emulators
>>> which run a hundred times as fast and don't complicate the situation?
>>> (Ha ha ha :)
>>> Â Â I've been a Smalltalk hacker since 1991 at UC Berkeley, first with
>>> Objectworks 2.5, then with the first few releases of VisualWorks while
>>> at ParcPlace, then to Squeak in 1996 and thereafter. I've served on the
>>> Squeak board since... oh, god. ;) ÂI'm preparing a release for the 20th
>>> of next month, a Squeak distribution called Spoon[2,3]. It features a
>>> minimal object memory and virtual machine (the better to learn and
>>> understand the system), and a live module system (the better to
>>> collaborate and distribute changes). The module system works with other
>>> Smalltalks, too (in particular, with VisualWorks). Yes, I know, severe
>>> error 33 risk, but I'd suggest that error 34 (being so afraid of
>>> error 33 that you don't do anything) is even worse. :)
>>> Â Â Oh, and I'm available for work. :)
>>>  http://www.wired.com/wired/archive/3.06/xanadu.html
>>>  http://netjam.org/spoon (main site)
>>>  http://thiscontext.wordpress.com (blog)
>>>  http://en.wikipedia.org/wiki/Error_33
>>> Craig Latta
>>> + 31 Â06 2757 7177
>>> + Â1 415 Â287 3547