On Sat, Oct 20, 2012 at 5:30 PM, Oliver Schmidt <ol.sc@web.de> wrote: >> Why did >> _curunit HAVE to go away completely? > > I hoped I did explain well why _curunit can't stay around: Write > access to it causes inconsistencies inside he C library. You *could* declare it as const for read-only access. But personally I think I still prefer wrapping it in a function (getcurrentdevice()), the overhead is negligible. -thefox ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sat Oct 20 17:40:50 2012
This archive was generated by hypermail 2.1.8 : 2012-10-20 17:40:54 CEST