From: Noel W. <noe...@ya...> - 2004-07-01 13:06:23
|
Hi all, I've just run into a bug in SRFI 19: it doesn't seem to parse the ~z zone offset specifier in string->date at all. Judging from past mailing posts there are a number of bugs in the current implementation. Is anyone working on SRFI 19? I've seen mention of Neil van Dyke's port, which sounds like it will become an excellent replacement for the current port. Is work progressing on that? Thanks, Noel ===== Email: noelwelsh <at> yahoo <dot> com Jabber: noelw <at> jabber <dot> org __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: MJ R. <mj...@ds...> - 2004-07-02 01:33:31
|
On 2004-07-01 14:06:16 +0100 Noel Welsh <noe...@ya...> wrote: > Is anyone working on SRFI 19? ISTR getting a reply to a bug report, then not seeing an updated reference implementation (which is the source of some bugs IIRC?) when I first checked and I've not had time to check again. So I guess, no, I'm not working on it. :D |
From: Francisco S. <so...@ac...> - 2004-07-27 19:02:08
|
Noel Welsh <noe...@ya...> writes: Hi, > I've just run into a bug in SRFI 19: it doesn't seem to > parse the ~z zone offset specifier in string->date at all. > Judging from past mailing posts there are a number of bugs > in the current implementation. Is anyone working on SRFI > 19? I did some work last week, and I found a couple of bugs there. Not with ~z, though. I added ~N to the reader, and change string->date so that it allows reading of partial dates. > I've seen mention of Neil van Dyke's port, which sounds like it will > become an excellent replacement for the current port. Indeed. I haven't had time to check Neil's implementation, but that was my plan originally. The only thing I'd like to preserve from the current implementation (apart from the ~N above) is the i18n stuff that I added, using SRFI-29. > Is work progressing on that? Give it a go. I used it to extend SPGSQL last week, and it is working fine, methinks. See the parse procedures parse-time, parse-date, etc. in sql-types.scm. (Ryan, I hope it's OK with you that I modified spgsql. Only modified that file.) Why I did it, well because we're extending SchemeQL to support other drivers. As a matter of fact, the latest MikeSurgery tagged version of schemeql now supports SrPersist and SPGSQL, have not updated the docs though. We're also writing SRFIs around this DB thing. (Hopefully we'll have drafts by the end of this week). In short, once you get the latest cvs version of schemeql do: (require (lib "spgsql.ss" "schemeql")) and you'll get schemeql over spgsql. The original "schemeql.ss" still sits atop srpersist. best regards, --Francisco |
From: Noel W. <noe...@ya...> - 2004-07-28 10:15:32
|
--- Francisco Solsona <so...@ac...> wrote: > Why I did it, well because we're extending SchemeQL to > support other > drivers. As a matter of fact, the latest MikeSurgery > tagged version > of schemeql now supports SrPersist and SPGSQL, have not > updated the > docs though. We're also writing SRFIs around this DB > thing. > (Hopefully we'll have drafts by the end of this week). This is great! I look forward to reading them. (The work on SRFI 19 is great as well!) Noel ===== Email: noelwelsh <at> yahoo <dot> com Jabber: noelw <at> jabber <dot> org __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |