Re: MOO into C

• Date: Wed, 24 Jul 1996 08:10:17 PDT
• From:
  dg@dcs.st-and.ac.uk
• Content-Type: text/plain; charset=us-ascii
• In-Reply-To: cadams@msgate.litc.lockheed.com's message of Wed, 24 Jul 96 07:37:00 -0700. <31F63579@msgate.litc.lockheed.com>

>I'm ambivalent here, I can live without them.  But this reminded me of 
>something else, something I'd really like to see the server correct.  The 
>following:
>
>foo = {@foo, bar}
[...]
>The only downside is that optimized code wouldn't decompile back into MOO 
>source code.  This could be worked around by giving programmers some 
>facility to save the un-optimized bytecodes (perhaps as a binary string?) 
>before optimizing.

It never is decompiled. The verb source is stored seperately from the 
byte-compiled version, in text form. Try disassembling some byte-compiled code 
one day and try decompiling it... it's just not possible (easily).


-- 
------------------- http://www-hons-cs.cs.st-and.ac.uk/~dg --------------------
   If you're up against someone more intelligent than you are, do something
    totally insane and let him think himself to death.  --- Pyanfar Chanur
---------------- Sun-Earther David Daton Given of Lochcarron ------------------

• Re: MOO into C
• From: Nick Ingolia <ningolia@neon.ci.lexington.ma.us>
• Re: MOO into C
• From: Brandon Gillespie <brandon@tombstone.sunrem.com>
• Re: MOO into C
• From: Pavel Curtis <pavel@parc.xerox.com>

• MOO into C
• From: "Adams, Charles" <cadams@msgate.litc.lockheed.com>

• Prev: MOO into C
• Next: Re: MOO into C
• Index: MOO-cows
• Thread: MOO-cows