On 7/13/2013 1:36 AM, Keith Medcalf wrote:
Of course, the behaviour is not actually "undefined" -- it is perfectly determinable and entirely predictable and reasonable. However, if one does not understand the factors which determine the behaviour then, for you, the behaviour is undefined. In other words, if one does not know what results are expected to be obtain and why, then the responsibility rests with the one who is "using the force" instead of understanding what they are doing.
The results are undefined in the sense that the authors don't document any particular behavior, and perhaps more importantly, don't commit to maintaining any particular behavior in future releases. If your program does something that falls under undefined behavior, and it appears to work to your liking, it does so only by accident. It relies on internal implementation details, subject to change without notice.
You may of course continue to live dangerously; just don't be surprised when you upgrade to a newer SQLite version and you program breaks.
-- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
