Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!ficc!cliff From: cliff@ficc.uu.net (cliff click) Newsgroups: comp.arch Subject: Re: Optical computing reference Summary: Code & Data access Message-ID: <4045@ficc.uu.net> Date: 1 May 89 14:26:25 GMT References: <89@ <46500061@uxe.cso.uiuc.edu> Organization: Ferranti International Controls Lines: 21 In article <46500061@uxe.cso.uiuc.edu>, mcdonald@uxe.cso.uiuc.edu writes: [deleted stuff about not being able to access code as data] > I am NOT - read my lips - referring to what is usually called > "self modifying code", but rather "incremental compilation". > Popular "compile and go" environments > like Turbo Pascal also seem to use this concept. > Is it just basically that some designers are rooted in the > old fashioned "compile now, run later" philosophy that they can't > even conceive of this? That is the only RATIONAL answer I can think of. > Doug McDonald I have implemented several programming environments that essentially did this - and I got a *LOT* of mileage out of it. I vote *YES* for non-compiler writers to be able to generate & execute their own code! -- Cliff Click, Software Contractor at Large Business: uunet.uu.net!ficc!cliff, cliff@ficc.uu.net, +1 713 274 5368 (w). Disclaimer: lost in the vortices of nilspace... +1 713 568 3460 (h).