> If you're programming a high level language that is compiled into
bytecode,
> thats not what I'm talking about - that still seperates the actual running
> processes from the coder (with a write/compile cycle). I'm thinking of a
> system where you edit the machine code as it's running. In most sensible
> situations this would only ever result in crashes :)
While working on my system I did allow you to edit while executing, but you
are right,
it just lead to lots of crashes and other wierd effects..
for instance..
i am typing 10 Mov 20
but while i am typing it gets executed at
10 Mov 2
oops ! we get a valid execution but an unintentional process..
this started to get really silly with commands like
10 Mov 100
if executed at
10 Mov 10
and so on...
So now it only commits the line when you press return..
otherwise you find yourself racing to type before the execution point comes
around again!!
fun though!
Tom
---------------------------------------------
http://www.nullpointer.co.uk
http://www.r4nd.org
http://www.q-q-q.net
----- Original Message -----
From: "Dave Griffiths" <dave_at_pawfal.org>
To: <livecode_at_slab.org>
Sent: Friday, September 10, 2004 3:17 PM
Subject: Re: [livecode] Hello (& chaos)
> On Fri, 10 Sep 2004 09:54:06 -0400, Ge Wang wrote
> > >> Something I'd like to research is changing code on the machine level
> > >> live.
> >
> > Perry and I are doing this with ChucK.
> >
> > http://chuck.cs.princeton.edu/
> >
> > ChucK runs on a VM with special virtual instructions (many for
> > dealing with time), and is type-checked and compiled down to these
> > instructions.
>
>
> Just friday afternoon waffle...
>
> dave
>
>
>
Received on Fri Sep 10 2004 - 14:34:16 BST