Re: cc65 competition?

[Harry Potter <maspethrose7@aol.com>]

On Apr 13, 5:52 am, Marc 'BlackJack' Rintsch <bj_...@gmx.net> wrote:
> It would be unnecessary big with `printf()`, at least with cc65, because
> all the formatting code will be included.  Try `puts()` for constant
> strings instead.
>

True, but if I exclude long and float support, I could probably
decrease overhead by as much as .5k.

> And I don't consider 11 KiB that big.  Remember that cc65 doesn't use the
> BASIC ROM, so there is some "base part" that makes short programs seem to
> look quite large compared to BASIC counter parts.  Because the BASIC ROM
> isn't needed you have about 50 KiB free RAM for C programs on the C64.  So
> part of your first feature, use of RAM from $a000-$cfff is already
> implemented in cc65.
>

11k is manageable, but what if I'm creating a program for the Vic20,
or for the C64 at $8000 or $C000?

> The RAM from $d000-$ffff is used by the graphics libraries that come with
> cc65 or can be accessed through the "memory driver" API.
>

True, but I'd like to access this data directly (i.e. declare it as
"hidden" and have the compiler automatically access this data through
a function cal whenever it is encountered).   Functions wouldn't work
well on a C64, but they would in Bank 1 on a C128.