<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>
Date   : Fri, 06 Nov 2009 17:13:38 +0000
From   : robert@... (Rob)
Subject: Basic6809 1.00

On 06/11/2009, Rick Murray <rick@...> wrote:
>
>    $.BUILD_IT
...
$ ?!?!

$.PaidWork.Bulk.Source.barerom/s
$.PaidWork.Bulk.Source.hayes/s
$.PaidWork.Bulk.Source.bulkbits/s
....
but yes I agree .. that folder also has a cp2123/s file - modem driver
for an esoteric most-definitely-non-hayes Racal Milgo modem I got from
Tandy..


> Tell me the significance of this code snippet:
>    &3954  36 35     ROL &35,X
>    &3956  30 32     BMI &398A
>    &3958  20 72 6F  JSR &6F72
>    &395B  6F 6C 7A  BBR6 &6C,&39D8
>    &395E  20 6F 6B  JSR &6B6F
>    &3961  21 20     AND (&20,X)
>    &3963  3A        DEA
>    &3964  2D 29 00  AND &0029

EQUS "6502 roolz ok! :-)"
EQUB 0

sequences of 3x and 20s are a dead giveaway that you're dealing with
text.  Well they are to me, when you've poked at enough code (6502 and
lots of other stuff; ASCII is ASCII whatever it's surrounded by!).

If you were to see these bytes in, say, a Beeb utility ROM disassembly:

82 23 82 76 83 0A 83 9F 84 16 84 F0

what would you think it was?

Totally agree with using comments and long variable names.  The above
mentioned source code I've not looked at for at least 20 years, and it
all still makes sense because I was verbose when writing it!  (It's
useless now, mind, as the service it talked to no longer exists..)
As do all the library routines in $.AsmLib ..!


Rob
<< Previous Message Main Index Next Message >>
<< Previous Message in Thread This Month Next Message in Thread >>