From: Ullrich von Bassewitz (uz_at_musoftware.de)
Date: 2002-11-13 22:43:41
On Wed, Nov 13, 2002 at 04:15:00PM +0100, MagerValp wrote:
> Yep, that'd be nice. The idea here is to be low level though. A ram
> expansion API could be implemented on top of these functions, and
> include a decent way of allocating memory. Here I just opted for a
> clean way of changing the start of free ram pointer, and left the
> specifics to the user. I'll be using this for a game project, that'll
> manage SuperRAM on its own.
Implementing the loadable module on top would be difficult, since there are
some conditions that must be met by such a module. But you're right, having a
low level API in addition to that is also ok.
> UvB> switch ((unsigned char *)0xd0b0 & $c0) {
> UvB> ^^^^
> UvB> does not seem to work for me. Maybe it's some secret optimization:-)
>
> Whoops, typo. Should be 0xd0b9, or possibly 0xd0bc -- the CMD docs say
> 53433 decimal but d0bc hex...
What I meant was more the "$c0" - this is not a valid hex constant in C.
> Oh, ok, well this is probably what I want, A --cpu 65c816 switch.
The assembler has it, but not the compiler.
Regards
Uz
--
Ullrich von Bassewitz uz_at_musoftware.de
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo_at_musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.3 : 2002-11-13 22:43:47 CET