D. Richard Hipp wrote: > > (2) Formal and detail requirements that define precisely what SQLite > does. > > http://www.sqlite.org/draft/tokenreq.html > http://www.sqlite.org/draft/syntax.html >
These look great. I noticed a few typos, but on the whole they are very good. I noticed that in many places you specify that sqlite will fail with an error, but you do not specify what the error will be (i.e. the error code and or message isn't specified). Perhaps these details should be added. BTW, have you noticed how much closer these documents are to the style of the SQL standard than your previous, less formal and more more ambiguous, documents were? :-) > > (6) New test harnesses and requirements-based test cases that give > 100% branch coverage and that can be run on embedded systems. > Will this test system be written in C instead of TCL to make it portable to a wider variety of system? Dennis Cote _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
