From: "A. Fachat"; on Friday, January 20, 2012; at 07:02 PM -0500 > > > > There's also a reason not to rely on imports: The string table for > > > the names of the symbols might get rather big. That is the reason why > > > loadable drivers (which are in o65 format) use a jump-table instead > > > of imports-by-name. > > > > That's an important point. > > Well ... in fact, even though I don't have it documented explicitely on the web > page, the recommendation is a mixed approach. Use a jump table, and only > import the base address of the jump table. The file format is intelligent > enough to handle offsets to imported variables. So, what I do in my own > operating system is to have two imports, "OSA65" and "LIB6502", and all > references are like "OSA65+3" (hidden by defined constants like "PUTC"). The > loader then adds the offset to the import. That way, you keep the import table > small; and, still have the relocation ability. I don't know if CC65 supports > that though. As Uz mentioned, that is the way that LUnix works. CC65 does support it. CC65 could build programs for your OSes. ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sat Jan 21 20:31:51 2012
This archive was generated by hypermail 2.1.8 : 2012-01-21 20:31:54 CET