Date   : Sat, 17 Dec 2011 22:00:49 +0000
From   : jgh@... (jgh@...)
Subject: 32016 + 32082

Rick Murray wrote:
> job; because JGH's HADFS suggests a much greater familiarity with the
> 6502/MOS than to do a mistake like setting X to 255, and *then* to 
> the
> value of the stack pointer...

Hmm. HADFS has had a /lot/ of work done on it since I started writing 
it
in 1989, and has lots of code to work around problems with other 
systems
trampling over resources they shouldn't. It probably wouldn't look like
that if I started it now.

I'm currently carefully going through the code doing some tidying up
and optimisations, and better commenting it. I'm about halfway through,
but the slowness is that I'm testing it for about a week for each 
change
I make.

> That said, I find I have to look in my book to confirm which way 
> around
> TSX/TXS go - for being used to the ARM where the destination comes 
> first...

I get that swapping between ARM and i86, especially as they both use 
the
MOV instruction, but the i86 MOV is actually LD. I was digging through
some 32016 code yesterday and found myself going down a very long goose
chase with the direction of parameters. And who on earth thinks to use
CMP #0,R0 instead of CMP R0,#0 ??? (yeah, ok, it sets Carry the other
way around ;) )

JGH