On 2014-06-27 21:56:39 +0800, YX Hao wrote: > > > I think I've already seen such a bug with some software, probably > > > because it wasn't detecting EOF (-1) correctly. > > Even if it is a "0xFF", it should not be the EOF, though many people > say it. You can make a file to test using my attachment. ;)
Yes, that's why I say above that it is a bug. I think that some developers *incorrectly* store the result of fgetc() to a char instead of an int, in which case 0xFF can't be distinguished from EOF. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
