Should we create a general "systems errors" SRFI?
hga@xxxxxx
(19 Sep 2019 13:27 UTC)
|
Re: Should we create a general "systems errors" SRFI?
Lassi Kortela
(19 Sep 2019 13:34 UTC)
|
Re: Should we create a general "systems errors" SRFI?
John Cowan
(19 Sep 2019 20:26 UTC)
|
Re: Should we create a general "systems errors" SRFI?
Lassi Kortela
(19 Sep 2019 20:54 UTC)
|
Re: Should we create a general "systems errors" SRFI?
John Cowan
(19 Sep 2019 21:04 UTC)
|
Re: Should we create a general "systems errors" SRFI?
Lassi Kortela
(19 Sep 2019 21:21 UTC)
|
Re: Should we create a general "systems errors" SRFI?
hga@xxxxxx
(19 Sep 2019 21:23 UTC)
|
Re: Should we create a general "systems errors" SRFI? Lassi Kortela (19 Sep 2019 21:32 UTC)
|
Re: Should we create a general "systems errors" SRFI?
hga@xxxxxx
(19 Sep 2019 22:12 UTC)
|
Re: Should we create a general "systems errors" SRFI?
Lassi Kortela
(20 Sep 2019 10:37 UTC)
|
Re: Should we create a general "systems errors" SRFI?
John Cowan
(20 Sep 2019 11:27 UTC)
|
> This is good, since I'm mentally budgeted one calendar year for my DBI/DBD API and perhaps something on top of it. Very nice :) I wish I had your and John's ability to dedicate myself to something. > Since getting one's error signaling regime nailed down is one of the very first parts of such a project, I've already been walking this path with SRFI 170, and I suggested the idea ^_^, I'll be delighted to work with Lassi to nail this down. Great! Do you want to write the first draft or should I? Design work should of course be constantly ongoing as we think of new stuff, but documents tend to be more coherent if one person at a time is writing :)