>>There are other advantages to this as well in terms >>of future expansion. Because we'd be using the gcc >>bytecodes our stacks could be natively compiled on >>that platform with no interpreter needed. The "do" >>command is a bit tricky, but not unsolvable. > >I imagine we'd have to make it do a callback to the interpreter. Could get >messy, but should be doable. I wanna Dynamic Linked Library! Runtimes are obselete, DLL's rule (except in windblows)
- OODL: Java VM and bytecodes as models Alain Farmer
- Re: OODL: Java VM and bytecodes as models Michael Fair
- Re: OODL: Java VM and bytecodes as models DeRobertis
- Re: OODL: Java VM and bytecodes as models M. Uli Kusterer
- Re: OODL: Java VM and bytecodes as models DeRobertis
- Re: OODL: Java VM and bytecodes as models M. Uli Kusterer
- Re: OODL: Java VM and bytecodes as models DeRobertis
- Re: OODL: Java VM and bytecodes as m... M. Uli Kusterer
- Re: OODL: Java VM and bytecodes ... DeRobertis
- Re: OODL: Java VM and bytecodes as m... Michael Fair
- Re: OODL: Java VM and bytecodes as models MP0werd
- Re: OODL: Java VM and bytecodes as models Alain Farmer
- Re: OODL: Java VM and bytecodes as models Michael Fair
- Re: OODL: Java VM and bytecodes as models DeRobertis
- Re: OODL: Java VM and bytecodes as models Michael Fair
- Re: OODL: Java VM and bytecodes as models DeRobertis
- Re: OODL: Java VM and bytecodes as models Michael Fair
- Re: OODL: Java VM and bytecodes as models M. Uli Kusterer
