From: CHRIS (chris_at_CosmicWolf.com)
Date: 2003-05-01 23:49:31
Thanks for the quick reply, Ullrich! Sorry for the name typo; my cousin's name is Ulrik and I keep typing that instead.. > > If I were to rewrite and/or update the Apple II > > support library, how would I go about it? That is, > > how do I know which functions I should be implementing? > > If you want to rewrite and/or update the Apple II support > library, shouldn't > you have an idea, which functions you want to rewrite and/or update? :-) To a degree, yes. As you pointed out, the clock() function, file I/O functions and rs232 routines. I was thinking about it more from the standpoint of how one might go about creating a whole new target library for CC65. CC65 itself has routines like, for example, the printf() function, but the platform/target library must supply its own putc() function (for example) as that would platform dependant. Or am I incorrect? > Out of my head, this is what is missing in the Apple library: > > * The clock() function (seems to be quite difficult to implement on the > Apple). > > * A complete set of file I/O functions. > > * Routines for rs232 communication (NOTE: I'm currently redoing > the rs232 > API to use loadable drivers, so it's not a good idea to add that now). > > * Drivers for extended memory, joysticks, mice, ... The clock() function will have to be a real kludge. A vanilla Apple II/II+/IIe has no means for generating periodic interrupts. Only with certain peripheral cards can that be done. When (or in which version of CC65) do you expect to have the new rs232 driver model in place? Thanks Ullrich, // CHRIS ---------------------------------------------------------------------- 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 : 2003-05-01 23:46:29 CEST