D. Richard Hipp a écrit : > This is not error in the SQLite code. The code here is correct. The > bug is in your compiler.
Sorry but I don't agree at all. > Adding a work-around so that this will work in your compiler makes the > code rather more complicated: > > wsdPrng.j = (wsdPrng.j + wsdPrng.s[i] + k[i]) & 0xff; > > I am opposed to obfuscating the code in this way because of your > compiler bug. Is there some command-line option or something on your > compiler that can turn off the silly overflow check? This makes code clearer. Adding unsigned char with value that exceeds maximum value (255) is a potential bug. Compiler doesn't know if it's done deliberately or not, and neither other people that read the code. So this option in compiler is useful to detect some bugs. If you say it's not one, that's fine, I'll add bit masking in my version, I just needed to know that. Thanks for help, Gérald _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
