[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Portable Self?
- To: self-interest@self.smli.com
- Subject: Portable Self?
- From: "ian (i.r.) woollard" <wolfe@nortel.ca>
- Date: Tue, 30 Jul 1996 13:06:00 -0400
- Sender: "ian (i.r.) woollard" <wolfe@nortel.ca>
- X400-content-type: P2-1984 (2)
- X400-mts-identifier: [/PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/;bcars520.b.345:30.06.96.17.06.36]
- X400-originator: /dd.id=1750136/g=ian/i=ir/s=woollard/@bnr.ca
- X400-received: by mta bnr.ca in /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 30 Jul 1996 13:10:13 -0400
- X400-received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 30 Jul 1996 13:06:36 -0400
- X400-received: by /PRMD=BNR/ADMD=TELECOM.CANADA/C=CA/; Relayed; Tue, 30 Jul 1996 13:06:00 -0400
I've just started playing with Java actually.
I notice that when you want to execute Java you have to translate the
Java code into byte codes so that they can be executed. However,
there's nothing very special about the bytecodes that Java produces;
in theory they could be written in any language.
So I was thinking: Self could do with the portability that byte codes
have. What's to stop someone producing a Self -> java bytecode
compiler?
The advantages are:
- great portability
- great availability
- okish speed (will get much better as the byte code interpreters
improve)
- making the typeless style of programming more popular
The problems I see are:
- interfacing to libraries (presumably not too hard)
- actually writing the compiler (presumably Jecels version of self is
closest to what you want)
- the dynamic nature of self code (e.g. potentially changing
constants/code on the fly-don't know whether Java allows this sort of
self modifying code!)