On Wed, Jul 28, 2004 at 11:48:08PM -0400, Greg King wrote: > That info. suggests that an easy division of the code would be: > o put DOS 3 file-functions into the "apple2/" sub-directory; > o put ProDOS file-functions into the "apple2enh/" sub-directory. I don't think this is true. apple2enh assumes several things about the hardware (mousetext characters, small and capital letters, ...), but it doesn't make assumptions about the disk I/O system running. An Apple //e can be run with an older ProDOS version, and as I understood it, most probably are. I have to admit that I don't like to add more and more apple targets, but on the other side, I cannot see how to map this to either of the existing ones. Maybe I will have to reconsider using separate libraries. Currently all stuff is in one target library. Having one main target library plus additional ones may work, since file routines could come with a second library. I've already thought about this when planning floating point math: To avoid linking in the whole math library just because printf is used, a dummy math library must be used, which leads to the same library design. One problem is currently the linker, because it doesn't consider a library twice, and doesn't allow circular dependencies between libraries as it is. But adding that feature wouldn't be a big change. Using this library method would need a clean design, however. The common stuff may contain hooks that are satisfied from a second library, but the second library would not be able to change main target code. 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.Received on Thu Jul 29 09:49:32 2004
This archive was generated by hypermail 2.1.8 : 2004-07-29 09:49:41 CEST