> The cc65 tools have to translate the ASCII stuff to the > target platforms that don't support ASCII. True... But if I tell CC65 that I want a \x73 shouldn't I get a $73?? I understand your point but IMHO I think that if I tell the compiler I want X character I should get X character. :) > BTW it's not the compiler but the linker that translates strings. > This way you can compile C source to an object file and link it into > executables for different target platforms and always get the correct > text output. Keep in mind that I am no C/C++ expert... So correct me if I am wrong, but I believe your statement above is incorrect. When I run CC65 like this: cc65 -O -t c64 hello1.c Generates the "hello1.s" assembly file. If I open the "hello1.s" file I see that this string in the source code: "\nhello world! \x73" Is translated into this: L0001: .byte $0D,$48,$45,$4C,$4C,$4F,$20,$57,$4F,$52,$4C,$44,$21,$20,$53,$00 See? I never even got to the linker stage before the $73 was converted to $53. :( Thanks, /*Raj*/ ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sun Sep 19 21:05:27 2004
This archive was generated by hypermail 2.1.8 : 2004-09-19 21:05:36 CEST