On Fri, Jul 25, 2008 at 01:56:02PM +0200, silverdr@inet.com.pl wrote: > > > >Alternatively, in the particular case of the Commodore 64, it wouldn't > >be hard to redirect the BSOUT/CHROUT call through a custom routine > >that handles CR specially when output to device 3. It would be > >overkill, IMO, but not difficult, since the jump table calls through > >an indirect vector at 0x0326. > > Yes - that is what I thought of initially. This shouldn't be > difficult and would probably work well without breaking things in > many other places as Ullrich was afraid of (unless I am again unaware > of something). It would be inconsistent and is not necessary for portable programs. Therfore I don't like the idea. Writing something to a file and then "displaying" this data on the screen would have other results than writing the data to the screen directly. On the other side, you're free to implement your own assembler module that does just the described things. Add a constructor to the module that is called automatically on program start. Hook the vector in the constructor. Linking this module to your application would then give the desired behaviour without any changes in the code. 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 Sat Jul 26 15:35:54 2008
This archive was generated by hypermail 2.1.8 : 2008-07-26 15:35:56 CEST