Hi! On Thu, Aug 09, 2007 at 01:27:01PM +0200, Oliver Schmidt wrote: > I didn't know if the conio.h issue was just an example or in fact the > (only) issue you have. Looking at conio.h I must admit that I aggree > wih you in that I don't understand why it strictly requires being > processed on a "known" target - especially as it doesn't depend on > target-specific macros to be defined or alike ?!? > > Hopefully Uz can explain... There are two reasons for this behaviour: The first is that errors are detected early, if you compile your app including conio.h when there is no corresponding implementation. Removing the check would mean that errors are detected in the link stage instead of compile stage. Admittedly this is nothing to worry about. The second reason is that system specific header files are included in the header. These may override certain functions that then expand to "nothing" instead a call to an empty function saving some bytes. Again it is not really necessary to check if the target is really known here, so I will remove the check in the develpment version. 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 Tue Aug 21 15:15:17 2007
This archive was generated by hypermail 2.1.8 : 2007-08-21 15:15:20 CEST