On Thu, Aug 20, 2009 at 10:00:47PM +0200, Oliver Schmidt wrote: > I'm far from having an overview but just the two changes > a) startup code in library > b) undef'ed functions trigger error > imply quite some incompatibility compared to the latest official > release. Especially a) means that I can't have a makefile working both > with the latest release and the latest snapshot. I didn't realize that to it's full extent, but you're right, I see your problem. > >From that perspective I'd suggest to create a new official cc65 > release to clearly define (and document) a) and b) as "the" cc65 > behaviour. Then one could change the makefiles instead of > communicating statements like "but don't dare to use a snapshot" or > "be sure to use the latest snapshot". My plan for the next few months is a new cc65 release, but as usual it's not as easy as it seems: * There should be a compelling reason for a new major release. Maybe I'm wrong, but I think, people expect that. Just "a few default behaviours changed" is not really enough. * There are a few things I want to go into a new release. Nothing big, a few days of coding and debugging anway. Unfortunately a day of coding cannot be replaced by 16 half hours, so I need real spare time. * Changing stuff (especially if code generation and optimizations are involved) is error prone. While I do understand that testing is difficult if there are incompatible changes, rushing out only loosely tested stuff gives me a bad feeling. Usually, bug reports start coming in when I release a new version. I'm still trying to find a way to get these bug reports *before* the release. 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 Aug 20 22:23:14 2009
This archive was generated by hypermail 2.1.8 : 2009-08-20 22:23:16 CEST