[cc65] Re: An idea to resolve this

On Sat, Nov 06, 2010 at 12:16:47PM +0100, Markus Stehr wrote:
> So, if you write a C64 program you would write .option c64 and the
> assembler would automaticly create those loader address bytes at the
> start.

At the start of what?

> Typing .option c64-basicloader $1000 would autogenerate the loader
> address and a BASIC stub that would SYS to $1000.

And place it where?

> So for Example an .option Nintendo would generate me an iNES Header at
> the start of my binary.

Of which binary? Depending on the config, ld65 may output no binary, one,
three, or 16.

> ".option fillspaces $ff" would fill all empty spaces inside a binary
> with $ff.

So what happens if one assembler module contains

        .option fillspaces $ff

and another one

        .option fillspaces $00

and finally the linker config contains

        fillval = $80

> ".option explicit" would warn or even refuse to write in non-declared
> space.
>
> And for that translation table stuff.
> ".option chartranslation cbm" would translate all string declarations to
> CBMSCII.

Most of this is already there, and it is in places where it is far more
appropriate. Code placement is not the job of the assembler but that of the
linker. So placement of headers or whatever must go into the linker config.
Trying to add it to the assembler creates all sorts of confusion as you can
see from my questions and explanations above.

Regards


        Uz


-- 
Ullrich von Bassewitz                                  uz@musoftware.de
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.