Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!NIU.BITNET!A01MES1
From: A01MES1@NIU.BITNET (Michael Stack)
Newsgroups: comp.lang.asm370
Subject: Re: Self Modifying Code
Message-ID: <8906142254.AA20930@jade.berkeley.edu>
Date: 14 Jun 89 22:22:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List <ASM370%UCF1VM.bitnet@jade.berkeley.edu>
Distribution: inet
Organization: The Internet
Lines: 14

> I am interested in readers' experiences with self-modifying code.

Over the last twenty years, my experience is:

>  ... self-modifying code is not reentrant; is not sharable; it can't
> reside in a ROM; it must be paged; it leads to serious cache coherency
> problems; it isn't easy to understand; it is architecture and
> perhaps implementation dependent.

... plus, it leads to coding errors (how did you forget that one?).


Michael Stack
Northern Illinois University