Path: utzoo!attcan!uunet!motcid!king
From: king@motcid.UUCP (Steven King)
Newsgroups: comp.sys.amiga
Subject: Re: Whats wrong with self Modifying Code?
Message-ID: <4065@grape3.UUCP>
Date: 13 Jul 90 18:56:16 GMT
References: <24379@snow-white.udel.EDU>
Organization: Motorola Inc. - Cellular Infrastructure Div., Arlington Heights, IL 60004
Lines: 15

Aside from other considerations, self-modifying code is a true nightmare
to maintain.  If you're going to do a one-shot demo or something like that,
great.  Do what you want to get every last cycle of performance you can out
of the system.  On the other hand, if you're writing something that has
a long lifecycle, something that you're going to be upgrading and keeping
around for years, self-modifying code is probably the worst thing imaginable
to try to change.  It's very hard to thoroughly debug and test.  And if
you move on to another project and someone ELSE has to take it over...
Things degrade rapidly.

-- 
---------------------------------------------------+---------------------------
It's only impossible until it's done.              | Steve King  (708) 991-8056
                                                   |   ...uunet!motcid!king
                                                   |   ...ddsw1!palnet!stevek