Ullrich von Bassewitz wrote: > When loading the drivers, there's a lot that may go wrong. The device may not > present, the library may be out of file descriptors, the driver may not be on > disk, there may not be enough memory to load the driver or whatever. All this > maps to TGI_ERR_CANNOT_LOAD - and has not been a problem until now. So I'm > sure the "saves hours of debugging" argument is greatly exaggerated. The "no IOCB" error in fact indicates that the system is out of file descriptors. But IMO it should happen that rarely that it doesn't justify a separate error code. > Using a platform dependent error function just complicates things and adds > another return value that has to be checked. How bloated will we want the API > to be? The Atari is already the platform that generates the biggest > executables, and I don't want to make this the general policy: > > ----------------------------------------------------------------------------- [snip - nice example showing Atari library memory consumption] > ----------------------------------------------------------------------------- I already knew that the Atari library has the biggest memory footprint :-/. I'll check the next days if I can find some room for optimizations. I'll also play with the possible settings in the library makefile and check out their memory impacts. regards, chris ---------------------------------------------------------------------- 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 Nov 12 22:24:08 2009
This archive was generated by hypermail 2.1.8 : 2009-11-12 22:24:10 CET