On 2010-03-15, at 21:12, Groepaz wrote: >> >> Is it a good idea to create some header file, which would redefine >> read/write/fread/fwrite when included? (something like #define >> read(a,b,c) >> read_ide64(a,b,c) ) But then I have to make a copy from fread/ >> fwrite as >> well... > > no, bad idea. much better idea to simply link custom versions of > read/write > Have mercy :-) Soci is a brilliant low-level hacker. He fully analyses 16KiB of assembler code in more or less the same time I need for writing helloworld ;-) so this might have some influence. As for the matter in question - I would vote for external library, that could be linked-in whenever needed. I wouldn't like to have extra code in the _STANDARD_ library. Even if I love IDE64 (just ordered the latest revision), and it is my clear favourite... Therefore I would rather ask the question: how can we make it easy for the programmer to just recompile (or even relink only) the program (without making any chenges in it), which uses POSIX calls to support various IO flavours at his choice. IDE64 being one of them. -- SD! ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Mon Mar 15 21:43:42 2010
This archive was generated by hypermail 2.1.8 : 2010-03-15 21:43:45 CET