> Further above you mention "overlay code". I don't know what you are > refering to but want nevertheless make sure you are aware of the > 'overlaydemo' program in the 'samples' directory. Thanks for the tip, that's just what I was looking to do! My game is divided into a bunch of separately-compiled binaries (e.g. bootstrapping code, drivecode, the main program and per-level code) and linking them together manually is getting rather tedious, especially where any sort of mutual dependencies are involved. By the way, is it possible to link in overlays automatically at the end of a preceding segment? That is to let the overlays fill up the remaining space without having to hardcode a specific size. > Combining a little C with a lot of assembler is in general certainly a > viable option. Thanks for the reassuring words. I wasn't really expecting any problems but I wanted to make sure that I wouldn't run into any brick walls before spending weeks on converting the code. /doynax ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sun Oct 10 14:58:24 2010
This archive was generated by hypermail 2.1.8 : 2010-10-10 14:58:27 CEST