Hi, > also one thing that seems to be lost in the discussion: ROMable code is _not_ > the rule for cc65 targets, This was in fact explicitly stated for the Lynx and Apple II. > most programmers are not > surprised that their code is not romable And placing the smc code in the data segment as I suggested wouldn't cause any surprise even for those: As far as I remember the cc65 docs even state somewhere that it is the responsibility of the "ROM creator" to copy the data segment somewhere into RAM on program startup... All nothing new as there's already some smc code in the C library placed in the data segment for these very reasons. I think it rather boils down to soft facts like "clean" and "easy to maintain / debug". Regards, Oliver ---------------------------------------------------------------------- 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 Feb 6 16:50:54 2011
This archive was generated by hypermail 2.1.8 : 2011-02-06 16:50:56 CET