On 2008-07-23, at 15:56, Mark J. Reed wrote: > On Wed, Jul 23, 2008 at 9:29 AM, <silverdr@inet.com.pl> wrote: >> Don't get me wrong but the code in question didn't require any >> kind of >> "special treatment" on any of the compilers/platforms I used in >> the past. > > Well, yeah, but there's a big difference between "it works on several > varieties of UNIX and DOS" and "it's portable across C > implementations". Different sets of commonalities. Yes, I got convinced already. > I mean, does it work on Atari 8-bit computers? Apple II? NES? :) I haven't checked. On the 64, since the only reasonable choice is CC65 I have to answer "NO" :-) but - hey! - I still should have the native C compiler for the 64 somewhere. The one I wrote the first main () with in the eighties... I am sure it wouldn't compile anything even remotely close to the complexity that CC65 can handle but I can write a helloworld to check \r behaviour there and then give the definite answer! :-D > I agree that it's unfortunate that the Commodore 64 display driver > doesn't have a way of sending the cursor back to the first column via > a CHROUT call. (The Commodore 128 one does, although you have to send > two characters, ESC followed by J.) This should still be fine - shouldn't it? I mean on the DOS and derivatives one needs two chars to get \n and this works for sure. But it's still a different thing to parse \n into a platform specific sequence of chars - even if longer than one - and do the uniform write afterwards, and a different thing to break the flow and treat one output device so differently than another. BTW. Is this C128 capability being used by the CC65 when compiling for the 128 target? ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Wed Jul 23 16:30:52 2008
This archive was generated by hypermail 2.1.8 : 2008-07-23 16:30:54 CEST