[Coco] pacos9 ported to lwtools

[Tormod Volden]

On Sat, Feb 8, 2014 at 7:40 AM, Bill Pierce wrote:
>
> Wayne, in going through litterally hundreds of C and asm sources in the past 2 years, I completely disagree with you.
> I see asm sources with the edition byte set to various values all the time, usually reflecting the edition of the program.
> In  compiling C or RMA programs, when running the linker you specify -e=xx to set the edition in the compiled program.
> You can also set the revision number in asm programs by using the lower 4 bits of the attr byte, usually ReEnt+rev on program files.

revision number != edition

For instance, pacos9 sets an EDITION symbol in the source which is not
referenced anywhere. Maybe RMA/RLINK did something magic with it, but
lwtools seems to ignore it.


> -----Original Message-----
> From: Wayne Campbell
> Sent: Sat, Feb 8, 2014 12:38 am
>
> The Edition byte in 6809 OS9 is a little different. First, while the
> documentation says it is part of the header, it is actually the first byte
> after the module name string. This means it is the first byte of the
> execution offset address (or the I-Code area address in a Basic09 module).
> In either case, it is something that many 6809 OS9 programmers seemed to
> get along without and never used.

I can confirm that ToolShed os9 ident reads the edition from the byte
following the name string.

But I don't think it is correct to say it is the first byte of the
execution offset address. The execution offset is in the header, while
the name string is in the body somewhere. In the pacos9 example, as
linked with lwtools, the module name is the very last part of the
body, so the shown "edition" is the first byte of the CRC.

Tormod