[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The Apple II is EVIL, it's the computer of SATAN ! ! ! !
- Subject: Re: The Apple II is EVIL, it's the computer of SATAN ! ! ! !
- From: "Bender MX" <nitroacdNO@telusplanetMORE.netSPAM>
- Date: Tue, 26 Oct 2004 17:25:36 GMT
- Newsgroups: comp.sys.apple2, can.uucp, alt.evil
- References: <7666ed5f.0410252309.7304847b@posting.google.com> <6cnfd.1974$VA5.1334@clgrps13> <q9vfd.21302$EZ.20243@okepread07>
- Reply-to: "Bender MX" <nitroacdNO@telusplanetMORE.netSPAM>
- Xref: g2news1.google.com comp.sys.apple2:5305 can.uucp:2713 alt.evil:3935
"Scott Alfter" <salfter@salfter.diespammersdie.dyndns.org> wrote in message
news:q9vfd.21302$EZ.20243@okepread07...
>The source code doesn't match the object code, and writing directly to
> screen memory probably isn't a good idea:
> Other than that, it's a clever rejoinder. Stuff like this is the reason I
> have AppleWin on one of my work machines. :-)
Hi Scott,
My brain didn't match working last night when I pecked that source into my
news agent. :)
By writing directly to the screen locations I eliminated the superflurous
steps
of loading a register and storing it for both the VTAB / HTAB positions
prior
to calling a COUT routine. Which essentially saves a few Bytes for a
program
of this nature...
Besides, lol, it's not like this is a user-friendly source code! :)
For what it's worth, really, it's pretty safe to write to the screen areas
of the
Apple. As a matter of fact, any game you've ever played on the Apple ][
absolutely had to address these areas directly for speed of execution.
Cheers,
Craig