Unfortunately for you, most companies today, and even Linux developers,
would not like such practices among their programmers. For the same reason
that a good programmer comments their code. Are you always going to be
there to fix problems? I don't think so. 9 out of 10 developers would pick
the programmer who wrote well-structured and readable (albeit slower) code,
over the programmer who wrote hard to follow, yet faster, code.
dwyatt
----- Original Message -----
From: "Austin L. Denyer" <[EMAIL PROTECTED]>
To: "List Linux-Mandrake" <[EMAIL PROTECTED]>
Sent: Monday, October 02, 2000 8:51 AM
Subject: Re: OT [newbie] Antique systems [was: Off-topic posts.]
>
> > Self modifying code. The only use I found for this on a z80 was speed.
It
> > DAD nagging me yto go to bed
>
> Self modifying code is SERIOUSLY useful for memory reasons too. Allow me
to
> give you a brief example.
>
> I once had to re-write a system that performed around 40 different
> calculations depending on the type of data received. Conventional
> programming (which was the way the original was written) would have had a
> subroutine for each case, with tests to check which one to jump to. Self
> modifying code allowed me to write one block of code, with NO jumps or
> tests - the code changed itself based on the input data.
>
> The net result was a program that ran MANY times faster, and took up
nearly
> 95% less memory.
>
> The users LOVED it!
>
> My successor HATED it...
>
> #;-D
>
> Regards,
> Ozz.
>
>
>
