On Sunday 19 September 2004 00:38, Raj Wurttemberg wrote: > > that happens because cc65 converts the charset encoding (from > > ascii to petscii in this case). however, i am not sure if this > > is correct behaviour here (when using \x).... no idea what the > > standard says here. > > I'm a noob to C so I have no idea about the standard. I used the same > printf statement that would be used in TurboC 3.0 and GCC on Linux > (SuSE) to print a graphic character and those two compilers generated > the correct code with no translation. So I'm guessing cc65 _should_ > be the same. Figures... a lowly noob like me would find something > silly. Haha! The problem is that both TurboC and GCC generate a program for a platform that uses the same character set as the source code. So there's no translation necessary. The cc65 tools have to translate the ASCII stuff to the target platforms that don't support ASCII. 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. Ciao, Marc 'BlackJack' Rintsch -- "A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away." -- Antoine de Saint-Exupéry ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.
This archive was generated by hypermail 2.1.8 : 2004-09-19 19:23:05 CEST