On Freitag 03 Dezember 2010, you wrote: > Can someone confirm that printf (on C64) selects the screen for > output (as in, cbm_k_ckout(STDOUT) or similar) before outputting the > text? I inserted some debug messages without considering this... > > I placed a (printf) debug message directly following a call to > cbm_k_ckout(lfn_serial). What seemed to happen was the debug message > went to the screen, and so did the character I sent after that using > BSOUT, that was intended to go to the lfn_serial device. > > Obviously what I did was in error, but the behavior seems to imply that > printf always writes to the screen, and cannot not be used to send output > to a logical file. This would be a bit unfortunate, but I imagine > sprintf() could be used as a workaround... ? you can not mix calls to the posix standard functions and arch dependend stuff like the cbm_ functions. so yes, what you say is what happens :) if you want to "printf" to a file, use fopen and fprintf. (or well, hack your own stuff with sprintf if you like to reinvent the wheel =P) -- http://www.hitmen-console.org http://magicdisk.untergrund.net http://www.pokefinder.org http://ftp.pokefinder.org To most Christians, the Bible is like a Software license. Nobody actually reads it. They just scroll to the bottom and click "I agree." ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Fri Dec 3 04:15:20 2010
This archive was generated by hypermail 2.1.8 : 2010-12-03 04:15:24 CET