1997-10-21 - Re: Interactive Programming - Self-modifying code

Header Data

From: phelix@vallnet.com
To: cypherpunks@Algebra.COM
Message Hash: f28cd462607af2eb256a34b17af4d89bb4143c04d81a5678f040f90ceddd0bbb
Message ID: <3450f621.2700668@128.2.84.191>
Reply To: <199710201628.LAA08124@einstein.ssz.com>
UTC Datetime: 1997-10-21 00:31:07 UTC
Raw Date: Tue, 21 Oct 1997 08:31:07 +0800

Raw message

From: phelix@vallnet.com
Date: Tue, 21 Oct 1997 08:31:07 +0800
To: cypherpunks@Algebra.COM
Subject: Re: Interactive Programming - Self-modifying code
In-Reply-To: <199710201628.LAA08124@einstein.ssz.com>
Message-ID: <3450f621.2700668@128.2.84.191>
MIME-Version: 1.0
Content-Type: text/plain



On 20 Oct 1997 18:43:14 -0500, Jim Choate <ravage@ssz.com> wrote:

>
>Forwarded message:
>
>> From: Brandon Crosby <bcrosby@mncs.k12.mn.us>
>> Subject: Re: [LONG, off-topic]] Interactive Programming
>> Date: Mon, 20 Oct 1997 10:22:23 -0500 (CDT)
>
>> > As are some perl programmers.  As both a perl programmer and a lisp
>> > programer I have never had the need to use self modifing code.  In fact I
>> > would consider haveing to use s-m code as a sine that I have made a
>> > mistate in my desinge.
>
>Come on, tell us how you really feel...
>
>What if your design specificaly includes self-modifying code for reasons of
>execution speed or some recursive efficiency? Glad to know I don't have to
>compete with you on those sorts of jobs...thanks.
>

I would think that self modifying code would play havoc with today's
pipelined and superscalar processors (if s&m code would even work on such
beasts).  Then they're those OS's that won't allow you to muck with code
space.  However, I guess it will always have a place in the embedded world.

-- Phelix






Thread