Heh. He implemented it with a goto statement! While I personally have no problem with this, especially when it is the most efficient solution, we have a client who demands all source code comply with MISRA and I don't relish the day we have to defend SQlite and our parser (lemon generated).
Ron Wilson, S/W Systems Engineer III, Tyco Electronics, 434.455.6453 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ralf Junker Sent: Friday, February 22, 2008 9:09 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] Unrecognized "Z" UTC time zone signifier Aristotle Pagaltzis wrote: >* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2008-02-21 13:45]: >> Ralf Junker <[EMAIL PROTECTED]> wrote: >> > SQLite does not recognize "Z" as the zero offset time zone >> > specifier. >> >> If we start accepting any symbolic timezone names, seems like >> we would then need to start accepting them all. >Not hardly. FWIW, the IETF recommendation for timestamps in >any new internet standards is to use the format specified in >RFCÂ 3339, which is based on codified experience. For time zones, >it prescribes that they be given as either a numeric offset or >`Z` a shortcut for `+00`; no provision is made for other symbolic >names as those only cause trouble. So you should have no trouble >refusing requests to support those. Richard did it, and it works like a charm: http://www.sqlite.org/cvstrac/chngview?cn=4805 Many thanks! Ralf _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
