Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!apple!agate!stew.ssl.berkeley.edu!ericco
From: ericco@stew.ssl.berkeley.edu (Eric C. Olson)
Newsgroups: comp.sys.atari.st
Subject: Re: Self-Modifying Code
Message-ID: <1989Oct28.001548.20290@agate.berkeley.edu>
Date: 28 Oct 89 00:15:48 GMT
References: <8910270333.AA14741@cscwam.UMD.EDU> <0927891128429423@thelake.UUCP>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Organization: University of California, Berkeley
Lines: 22

Really Self-Modifying Data

Lisp systems typically have a 'dumplisp' function which dump an image
of itself to disk.  Thus, invoking the dumped lisp, returns you to the
exact environment you dumped.  This is easier to do in lisp since it
treats its source code as data.

Although modify the executable file seems bad to me, I think that modifying
the resource file is completely reasonable solution (and simple).  By
parsing the structure of the resource file, your program can quickly
determine which parameter (object) needs to be modified.  In fact, if
your program uses text, then you should put the text in the resource file
as well.  This is how the resource file is supposed to be used.  By putting
the text in the resource file, non-English speaking people can replace it
with meaningful non-English text.

Eric
ericco@sag4.ssl.berkeley.edu


Eric
ericco@ssl.berkeley.edu