01 Aug 2020 01:57 UTC |
Re: Establishing a Scheme registry |
John Cowan |
01 Aug 2020 03:48 UTC |
Re: Establishing a Scheme registry |
John Cowan |
01 Aug 2020 06:28 UTC |
Re: Establishing a Scheme registry |
Marc Nieper-Wißkirchen |
01 Aug 2020 13:19 UTC |
Re: Establishing a Scheme registry |
John Cowan |
01 Aug 2020 13:47 UTC |
Re: Establishing a Scheme registry |
Marc Nieper-Wißkirchen |
01 Aug 2020 13:54 UTC |
Re: Establishing a Scheme registry |
Amirouche Boubekki |
01 Aug 2020 19:50 UTC |
Re: Establishing a Scheme registry |
Lassi Kortela |
01 Aug 2020 20:10 UTC |
Re: Abstract or concrete data type for foreign error object? |
Lassi Kortela |
02 Aug 2020 03:40 UTC |
Re: How would we use BCP 47 strings in a simple way? |
John Cowan |
02 Aug 2020 06:49 UTC |
Keyword support in SRFI 198 |
Lassi Kortela |
02 Aug 2020 06:58 UTC |
Re: Keyword support in SRFI 198 |
Lassi Kortela |
02 Aug 2020 07:07 UTC |
Re: Keyword support in SRFI 198 |
Shiro Kawai |
02 Aug 2020 07:40 UTC |
Re: Keyword support in SRFI 198 |
Lassi Kortela |
02 Aug 2020 08:34 UTC |
Re: How would we use BCP 47 strings in a simple way? |
Lassi Kortela |
02 Aug 2020 09:27 UTC |
Re: How would we use BCP 47 strings in a simple way? |
Lassi Kortela |
02 Aug 2020 09:36 UTC |
Re: How would we use BCP 47 strings in a simple way? |
Lassi Kortela |
02 Aug 2020 09:51 UTC |
Re: How would we use BCP 47 strings in a simple way? |
Lassi Kortela |
02 Aug 2020 11:35 UTC |
SRFI 198: clear enough for next draft? |
Lassi Kortela |
02 Aug 2020 12:21 UTC |
Re: SRFI 198: clear enough for next draft? |
hga@xxxxxx |
02 Aug 2020 13:21 UTC |
Re: SRFI 198: clear enough for next draft? |
Lassi Kortela |
02 Aug 2020 15:00 UTC |
Re: Keyword support in SRFI 198 |
Marc Nieper-Wißkirchen |
02 Aug 2020 15:04 UTC |
Re: SRFI 198: clear enough for next draft? |
hga@xxxxxx |
03 Aug 2020 16:34 UTC |
Foreign errors are not necessarily errors |
Lassi Kortela |
03 Aug 2020 16:38 UTC |
Re: Foreign errors are not necessarily errors |
John Cowan |
03 Aug 2020 16:46 UTC |
Re: HTTP error codes |
hga@xxxxxx |
03 Aug 2020 16:49 UTC |
Re: Foreign errors are not necessarily errors |
Lassi Kortela |
03 Aug 2020 16:53 UTC |
Re: Foreign errors are not necessarily errors |
John Cowan |
03 Aug 2020 17:03 UTC |
Re: Foreign errors are not necessarily errors |
Lassi Kortela |
03 Aug 2020 17:04 UTC |
Re: HTTP error codes |
John Cowan |
03 Aug 2020 17:06 UTC |
Re: HTTP error codes |
John Cowan |
03 Aug 2020 17:15 UTC |
Complexity of SRFI 198 interface and naming |
Lassi Kortela |
03 Aug 2020 17:52 UTC |
Re: Complexity of SRFI 198 interface and naming |
hga@xxxxxx |
03 Aug 2020 17:53 UTC |
Re: Complexity of SRFI 198 interface and naming |
John Cowan |
03 Aug 2020 18:06 UTC |
Re: Complexity of SRFI 198 interface and naming |
Lassi Kortela |
03 Aug 2020 18:12 UTC |
Re: Complexity of SRFI 198 interface and naming |
Lassi Kortela |
04 Aug 2020 15:52 UTC |
Re: Complexity of SRFI 198 interface and naming |
John Cowan |
04 Aug 2020 16:24 UTC |
Re: Complexity of SRFI 198 interface and naming |
hga@xxxxxx |
04 Aug 2020 16:35 UTC |
Re: Complexity of SRFI 198 interface and naming |
Lassi Kortela |
05 Aug 2020 02:30 UTC |
Re: Complexity of SRFI 198 interface and naming |
John Cowan |
05 Aug 2020 06:13 UTC |
Re: SRFI 198: clear enough for next draft? |
John Cowan |
05 Aug 2020 10:33 UTC |
Foreign status objects for syslog and other logging frameworks |
Lassi Kortela |
05 Aug 2020 13:10 UTC |
Re: SRFI 198: clear enough for next draft? |
hga@xxxxxx |
05 Aug 2020 15:23 UTC |
Re: SRFI 198: clear enough for next draft? |
Lassi Kortela |
05 Aug 2020 15:59 UTC |
Re: SRFI 198: clear enough for next draft? |
hga@xxxxxx |
05 Aug 2020 16:17 UTC |
Re: SRFI 198: clear enough for next draft? |
Lassi Kortela |
06 Aug 2020 03:22 UTC |
Re: SRFI 198: clear enough for next draft? |
John Cowan |
06 Aug 2020 03:49 UTC |
Re: SRFI 198: clear enough for next draft? |
John Cowan |
06 Aug 2020 04:30 UTC |
Re: How would we use BCP 47 strings in a simple way? |
John Cowan |
09 Aug 2020 17:09 UTC |
Re: two items |
hga@xxxxxx |
09 Aug 2020 18:29 UTC |
Re: two items |
John Cowan |
09 Aug 2020 19:46 UTC |
SRFI 198 Foreign interface Status Handling, general and for the purposes of SRFI 170 |
hga@xxxxxx |
09 Aug 2020 21:01 UTC |
Re: SRFI 198 Foreign interface Status Handling, general and for the purposes of SRFI 170 |
Lassi Kortela |
09 Aug 2020 21:29 UTC |
Solving the symbol-vs-number conundrum |
Lassi Kortela |
10 Aug 2020 00:39 UTC |
Re: SRFI 198 Foreign interface Status Handling, general and for the purposes of SRFI 170 |
hga@xxxxxx |
10 Aug 2020 00:40 UTC |
Re: SRFI 198 Foreign interface Status Handling, general and for the purposes of SRFI 170 |
John Cowan |
10 Aug 2020 00:52 UTC |
Re: SRFI 198 Foreign interface Status Handling, general and for the purposes of SRFI 170 |
hga@xxxxxx |
10 Aug 2020 00:55 UTC |
Re: SRFI 198 Foreign interface Status Handling, general and for the purposes of SRFI 170 |
John Cowan |
10 Aug 2020 01:02 UTC |
Re: Solving the symbol-vs-number conundrum |
John Cowan |
10 Aug 2020 06:48 UTC |
Re: Solving the symbol-vs-number conundrum |
Lassi Kortela |
10 Aug 2020 07:03 UTC |
SQLSTATE |
Lassi Kortela |
10 Aug 2020 07:11 UTC |
Any alphanumeric errors anywhere? |
Lassi Kortela |
10 Aug 2020 07:15 UTC |
Re: Any alphanumeric errors anywhere? |
Lassi Kortela |
10 Aug 2020 07:42 UTC |
Re: Any alphanumeric errors anywhere? |
Göran Weinholt |
10 Aug 2020 08:29 UTC |
VMS errors |
Lassi Kortela |
10 Aug 2020 11:32 UTC |
libsodium error codes |
Lassi Kortela |
10 Aug 2020 13:11 UTC |
Localization and a new STFI 198 draft to base it upon |
hga@xxxxxx |
10 Aug 2020 14:07 UTC |
Re: Localization and a new STFI 198 draft to base it upon |
Lassi Kortela |
10 Aug 2020 15:10 UTC |
What to do for bad arguments to foreign-status-plist? |
hga@xxxxxx |
10 Aug 2020 15:14 UTC |
Re: What to do for bad arguments to foreign-status-plist? |
Lassi Kortela |
10 Aug 2020 15:28 UTC |
Re: What to do for bad arguments to foreign-status-plist? |
hga@xxxxxx |
10 Aug 2020 15:38 UTC |
Re: What to do for bad arguments to foreign-status-plist? |
Lassi Kortela |
10 Aug 2020 20:35 UTC |
Re: Solving the symbol-vs-number conundrum |
John Cowan |
10 Aug 2020 21:30 UTC |
Re: Solving the symbol-vs-number conundrum |
Lassi Kortela |
10 Aug 2020 22:11 UTC |
Re: Solving the symbol-vs-number conundrum |
hga@xxxxxx |
11 Aug 2020 02:44 UTC |
Re: VMS errors |
John Cowan |
11 Aug 2020 03:48 UTC |
Re: Solving the symbol-vs-number conundrum |
John Cowan |
11 Aug 2020 06:50 UTC |
Re: Solving the symbol-vs-number conundrum |
Lassi Kortela |
11 Aug 2020 17:42 UTC |
Sources for the new Common Lisp condition system book |
Lassi Kortela |
12 Aug 2020 12:01 UTC |
Re: Solving the symbol-vs-number conundrum |
hga@xxxxxx |
12 Aug 2020 12:06 UTC |
Re: Solving the symbol-vs-number conundrum |
hga@xxxxxx |
12 Aug 2020 12:38 UTC |
Re: What to do for bad arguments to foreign-status-plist? |
hga@xxxxxx |
12 Aug 2020 12:48 UTC |
Re: Solving the symbol-vs-number conundrum |
John Cowan |
12 Aug 2020 12:49 UTC |
Re: Localization and a new STFI 198 draft to base it upon |
hga@xxxxxx |
12 Aug 2020 12:50 UTC |
Special properties of the 'set key |
John Cowan |
12 Aug 2020 12:54 UTC |
Re: Localization and a new STFI 198 draft to base it upon |
John Cowan |
12 Aug 2020 12:58 UTC |
Re: What to do for bad arguments to foreign-status-plist? |
John Cowan |
12 Aug 2020 13:12 UTC |
SRFI 198 proposal to change 'set to 'facility |
hga@xxxxxx |
12 Aug 2020 13:18 UTC |
Re: Special properties of the 'set key |
hga@xxxxxx |
12 Aug 2020 15:14 UTC |
plist pre-SRFI |
hga@xxxxxx |
12 Aug 2020 15:20 UTC |
Re: plist pre-SRFI |
John Cowan |
12 Aug 2020 15:53 UTC |
Re: plist pre-SRFI |
John Cowan |
12 Aug 2020 15:58 UTC |
Re: plist pre-SRFI |
hga@xxxxxx |
12 Aug 2020 16:32 UTC |
Re: SRFI 198: clear enough for next draft? |
hga@xxxxxx |
12 Aug 2020 16:55 UTC |
Re: SRFI 198: clear enough for next draft? |
hga@xxxxxx |
12 Aug 2020 16:59 UTC |
Re: plist pre-SRFI |
John Cowan |
12 Aug 2020 17:34 UTC |
Re: plist pre-SRFI |
hga@xxxxxx |
12 Aug 2020 19:37 UTC |
Re: plist pre-SRFI |
John Cowan |
12 Aug 2020 20:03 UTC |
Use of SRFI 198 in SRFI 170 |
hga@xxxxxx |
13 Aug 2020 06:58 UTC |
Re: Special properties of the 'set key |
Lassi Kortela |
13 Aug 2020 10:55 UTC |
Re: Special properties of the 'set key |
hga@xxxxxx |
13 Aug 2020 18:46 UTC |
On POSIX errnos using 'number as a key, and SRFI 198 not defining that, 'code, etc. as standards at its level |
hga@xxxxxx |
13 Aug 2020 20:31 UTC |
Re: On POSIX errnos using 'number as a key, and SRFI 198 not defining that, 'code, etc. as standards at its level |
John Cowan |
13 Aug 2020 21:04 UTC |
Re: On POSIX errnos using 'number as a key, and SRFI 198 not defining that, 'code, etc. as standards at its level |
hga@xxxxxx |
14 Aug 2020 04:28 UTC |
Re: Special properties of the 'set key |
John Cowan |
14 Aug 2020 07:37 UTC |
Re: Special properties of the 'set key |
Lassi Kortela |
14 Aug 2020 08:20 UTC |
Re: Special properties of the 'set key |
Lassi Kortela |
14 Aug 2020 08:47 UTC |
Sub-set key and zero/nonzero success/failure status sets |
Lassi Kortela |
14 Aug 2020 09:59 UTC |
Design by construction |
Lassi Kortela |
14 Aug 2020 12:22 UTC |
R6RS foreign-error sketch |
Lassi Kortela |
14 Aug 2020 13:30 UTC |
Re: What to do for bad arguments to foreign-status-plist? |
Lassi Kortela |
14 Aug 2020 13:46 UTC |
Promise objects |
Lassi Kortela |
14 Aug 2020 14:03 UTC |
Re: Promise objects |
Lassi Kortela |
14 Aug 2020 15:12 UTC |
Clearing up confusion |
Lassi Kortela |
14 Aug 2020 15:27 UTC |
Re: Clearing up confusion, and Windows errors as POSIX errno's |
Lassi Kortela |
14 Aug 2020 15:43 UTC |
Compound conditions and foreign status objects |
Lassi Kortela |
14 Aug 2020 15:54 UTC |
Semantic property names and static vs dynamic types |
Lassi Kortela |
14 Aug 2020 15:57 UTC |
Re: Solving the symbol-vs-number conundrum |
Lassi Kortela |
14 Aug 2020 16:35 UTC |
Good-enough localization? |
Lassi Kortela |
14 Aug 2020 22:06 UTC |
Re: Semantic property names and static vs dynamic types |
John Cowan |
14 Aug 2020 22:07 UTC |
Re: Good-enough localization? |
John Cowan |
14 Aug 2020 22:10 UTC |
Re: Good-enough localization? |
Lassi Kortela |
14 Aug 2020 22:10 UTC |
Re: Good-enough localization? |
John Cowan |
14 Aug 2020 22:16 UTC |
Re: Good-enough localization? |
Lassi Kortela |
14 Aug 2020 22:18 UTC |
Re: Compound conditions and foreign status objects |
John Cowan |
14 Aug 2020 22:30 UTC |
Re: Good-enough localization? |
John Cowan |
14 Aug 2020 23:28 UTC |
Re: Compound conditions and foreign status objects |
Shiro Kawai |
15 Aug 2020 00:49 UTC |
Re: Final review of johnwcowan/srfi-170/srfi-170.html, part 2 starting with 3.3 File system, create-temp-file |
hga@xxxxxx |
15 Aug 2020 00:54 UTC |
Re: Clearing up confusion |
John Cowan |
15 Aug 2020 01:46 UTC |
Re: Another sketch of foreign-status abstraction in Common Lisp |
John Cowan |
15 Aug 2020 10:46 UTC |
Re: Clearing up confusion |
Marc Nieper-Wißkirchen |
15 Aug 2020 10:57 UTC |
Re: posix-error and a list of scheme procedure arguments |
hga@xxxxxx |
15 Aug 2020 11:16 UTC |
Re: posix-error and a list of scheme procedure arguments |
Marc Nieper-Wißkirchen |
15 Aug 2020 11:20 UTC |
Re: Compound conditions and foreign status objects |
Marc Nieper-Wißkirchen |
15 Aug 2020 11:31 UTC |
Re: Another sketch of foreign-status abstraction in Common Lisp |
hga@xxxxxx |
15 Aug 2020 11:46 UTC |
Clearing up the previous clearing up |
Lassi Kortela |
15 Aug 2020 11:50 UTC |
Re: posix-error and a list of scheme procedure arguments |
hga@xxxxxx |
15 Aug 2020 12:09 UTC |
Re: posix-error and a list of scheme procedure arguments |
Lassi Kortela |
15 Aug 2020 12:16 UTC |
Another sketch of foreign-status abstraction in Common Lisp (sent to the wrong mailing list) |
Lassi Kortela |
15 Aug 2020 12:42 UTC |
Re: posix-error and a list of scheme procedure arguments |
hga@xxxxxx |
15 Aug 2020 13:10 UTC |
Synthetic errno values |
Lassi Kortela |
15 Aug 2020 15:03 UTC |
Re: Clearing up the previous clearing up |
John Cowan |
15 Aug 2020 15:19 UTC |
Re: Synthetic errno values |
John Cowan |
15 Aug 2020 15:34 UTC |
Re: Synthetic errno values |
Lassi Kortela |
15 Aug 2020 16:02 UTC |
Re: Synthetic errno values |
hga@xxxxxx |
15 Aug 2020 16:25 UTC |
Re: Solving the symbol-vs-number conundrum |
hga@xxxxxx |
15 Aug 2020 16:31 UTC |
Re: Compound conditions and foreign status objects |
hga@xxxxxx |
15 Aug 2020 16:45 UTC |
Re: Compound conditions and foreign status objects |
John Cowan |
15 Aug 2020 16:46 UTC |
Re: Compound conditions and foreign status objects |
Marc Nieper-Wißkirchen |
15 Aug 2020 16:49 UTC |
Re: Compound conditions and foreign status objects |
Marc Nieper-Wißkirchen |
15 Aug 2020 16:50 UTC |
Re: Clearing up confusion, and Windows errors as POSIX errno's |
hga@xxxxxx |
15 Aug 2020 17:07 UTC |
Re: Compound conditions and foreign status objects |
Marc Nieper-Wißkirchen |
15 Aug 2020 18:35 UTC |
Updating Scheme Registry with the latest ideas for SRFI 198 |
Lassi Kortela |
15 Aug 2020 18:59 UTC |
A better name for 'set, a need for a reflection API for SRFI 198?? |
hga@xxxxxx |
15 Aug 2020 20:22 UTC |
Re: Clearing up confusion |
hga@xxxxxx |
16 Aug 2020 01:11 UTC |
Re: posix-error and a list of scheme procedure arguments |
Shiro Kawai |
16 Aug 2020 02:26 UTC |
Re: posix-error and a list of scheme procedure arguments |
hga@xxxxxx |
16 Aug 2020 02:30 UTC |
Re: posix-error and a list of scheme procedure arguments |
Shiro Kawai |
16 Aug 2020 02:43 UTC |
Split SRFI 198 from generic debugging/inspection? |
hga@xxxxxx |
16 Aug 2020 06:31 UTC |
Re: A better name for 'set, a need for a reflection API for SRFI 198?? |
Lassi Kortela |
16 Aug 2020 07:58 UTC |
Re: Synthetic errno values |
Lassi Kortela |
16 Aug 2020 08:52 UTC |
Re: posix-error and a list of scheme procedure arguments |
Göran Weinholt |
16 Aug 2020 09:01 UTC |
Re: posix-error and a list of scheme procedure arguments |
Lassi Kortela |
16 Aug 2020 09:06 UTC |
Re: Split SRFI 198 from generic debugging/inspection? |
Lassi Kortela |
16 Aug 2020 09:10 UTC |
Re: posix-error and a list of scheme procedure arguments |
Shiro Kawai |
16 Aug 2020 09:40 UTC |
Re: posix-error and a list of scheme procedure arguments |
Göran Weinholt |
16 Aug 2020 10:20 UTC |
Re: posix-error and a list of scheme procedure arguments |
Marc Nieper-Wißkirchen |
16 Aug 2020 11:17 UTC |
Re: posix-error and a list of scheme procedure arguments |
Shiro Kawai |
16 Aug 2020 11:21 UTC |
Passing symbols to say where errors came from? |
Lassi Kortela |
16 Aug 2020 11:29 UTC |
Re: posix-error and a list of scheme procedure arguments |
Shiro Kawai |
16 Aug 2020 11:29 UTC |
Continuation marks and SRFI 198 |
Lassi Kortela |
16 Aug 2020 12:18 UTC |
Re: posix-error and a list of scheme procedure arguments |
Marc Nieper-Wißkirchen |
16 Aug 2020 12:30 UTC |
Re: A better name for 'set, a need for a reflection API for SRFI 198?? |
hga@xxxxxx |
16 Aug 2020 12:39 UTC |
Re: Synthetic errno values |
hga@xxxxxx |
16 Aug 2020 12:41 UTC |
Re: A better name for 'set, a need for a reflection API for SRFI 198?? |
Marc Nieper-Wißkirchen |
16 Aug 2020 12:51 UTC |
Re: Continuation marks and SRFI 198 |
Marc Nieper-Wißkirchen |
16 Aug 2020 13:01 UTC |
Re: Split SRFI 198 from generic debugging/inspection? |
hga@xxxxxx |
16 Aug 2020 13:07 UTC |
Re: Synthetic errno values |
Lassi Kortela |
16 Aug 2020 13:18 UTC |
Re: A better name for 'set, a need for a reflection API for SRFI 198?? |
hga@xxxxxx |
16 Aug 2020 13:36 UTC |
SRFI 35 (Conditions), SRFI 198, and do we have a compatible vision |
Lassi Kortela |
16 Aug 2020 13:47 UTC |
Matching what other languages give in SRFI 170 errors |
Lassi Kortela |
16 Aug 2020 13:49 UTC |
Re: SRFI 35 (Conditions), SRFI 198, and do we have a compatible vision |
hga@xxxxxx |
16 Aug 2020 14:06 UTC |
Do we have a compatible vision for SRFI 198 |
Lassi Kortela |
16 Aug 2020 14:13 UTC |
Re: SRFI 35 (Conditions), SRFI 198, and do we have a compatible vision |
Marc Nieper-Wißkirchen |
16 Aug 2020 14:22 UTC |
Re: Do we have a compatible vision for SRFI 198 |
hga@xxxxxx |
16 Aug 2020 14:23 UTC |
Re: Do we have a compatible vision for SRFI 198 |
Marc Nieper-Wißkirchen |
16 Aug 2020 14:23 UTC |
SRFI 35 compound conditions |
Lassi Kortela |
16 Aug 2020 14:26 UTC |
Re: SRFI 35 compound conditions |
Marc Nieper-Wißkirchen |
16 Aug 2020 14:30 UTC |
raise-foreign-error |
Marc Nieper-Wißkirchen |
16 Aug 2020 14:44 UTC |
Decision on foreign-status constructor and accesor syntax |
Lassi Kortela |
16 Aug 2020 15:04 UTC |
Re: raise-foreign-error |
hga@xxxxxx |
16 Aug 2020 15:19 UTC |
Re: Decision on foreign-status constructor and accesor syntax |
hga@xxxxxx |
16 Aug 2020 15:26 UTC |
Re: raise-foreign-error |
Marc Nieper-Wißkirchen |
16 Aug 2020 15:31 UTC |
Re: Decision on foreign-status constructor and accesor syntax |
Marc Nieper-Wißkirchen |
16 Aug 2020 16:01 UTC |
Re: raise-foreign-error |
hga@xxxxxx |
16 Aug 2020 17:12 UTC |
Re: Decision on foreign-status constructor and accesor syntax |
hga@xxxxxx |
16 Aug 2020 17:19 UTC |
Re: Decision on foreign-status constructor and accesor syntax |
Marc Nieper-Wißkirchen |
16 Aug 2020 17:24 UTC |
On the messiness of alists for lists as values |
hga@xxxxxx |
16 Aug 2020 17:31 UTC |
Re: Decision on foreign-status constructor and accesor syntax |
hga@xxxxxx |
16 Aug 2020 17:39 UTC |
Re: On the messiness of alists for lists as values |
Marc Nieper-Wißkirchen |
16 Aug 2020 17:52 UTC |
Re: On the messiness of alists for lists as values |
hga@xxxxxx |
16 Aug 2020 18:39 UTC |
Re: On the messiness of alists for lists as values |
Marc Nieper-Wißkirchen |
16 Aug 2020 19:04 UTC |
Re: On the messiness of alists for lists as values |
hga@xxxxxx |
16 Aug 2020 22:26 UTC |
Re: On the messiness of alists for lists as values |
John Cowan |
17 Aug 2020 02:35 UTC |
Re: raise-foreign-error |
John Cowan |
17 Aug 2020 02:51 UTC |
Re: Do we have a compatible vision for SRFI 198 |
John Cowan |
17 Aug 2020 06:11 UTC |
Re: Matching what other languages give in SRFI 170 errors |
Marc Nieper-Wißkirchen |
17 Aug 2020 10:07 UTC |
PC-Scheme for DOS |
Lassi Kortela |
17 Aug 2020 10:10 UTC |
Re: Matching what other languages give in SRFI 170 errors |
Lassi Kortela |
17 Aug 2020 10:52 UTC |
Should foreign-status properties be divided into sets or not? |
Lassi Kortela |
17 Aug 2020 11:58 UTC |
Re: raise-foreign-error |
hga@xxxxxx |
17 Aug 2020 12:06 UTC |
Re: raise-foreign-error |
Lassi Kortela |
17 Aug 2020 12:10 UTC |
R6RS condition type hierarchy |
Lassi Kortela |
17 Aug 2020 13:40 UTC |
Re: R6RS condition type hierarchy |
John Cowan |
17 Aug 2020 14:01 UTC |
Re: Should foreign-status properties be divided into sets or not? |
John Cowan |
17 Aug 2020 14:19 UTC |
Re: raise-foreign-error |
hga@xxxxxx |
17 Aug 2020 14:47 UTC |
Re: R6RS condition type hierarchy |
Lassi Kortela |
17 Aug 2020 14:56 UTC |
Re: R6RS condition type hierarchy |
Marc Nieper-Wißkirchen |
17 Aug 2020 15:05 UTC |
Re: Should foreign-status properties be divided into sets or not? |
hga@xxxxxx |
17 Aug 2020 15:30 UTC |
Re: Should foreign-status properties be divided into sets or not? |
John Cowan |
17 Aug 2020 15:38 UTC |
Re: Should foreign-status properties be divided into sets or not? |
Lassi Kortela |
17 Aug 2020 15:38 UTC |
New draft (#3) of SRFI 198: Foreign Interface Status [renamed] |
Arthur A. Gleckler |
17 Aug 2020 15:51 UTC |
Re: Should foreign-status properties be divided into sets or not? |
Lassi Kortela |
17 Aug 2020 15:51 UTC |
Re: Should foreign-status properties be divided into sets or not? |
Marc Nieper-Wißkirchen |
17 Aug 2020 16:02 UTC |
Re: Should foreign-status properties be divided into sets or not? |
Lassi Kortela |
17 Aug 2020 16:09 UTC |
Why plists? |
John Cowan |
17 Aug 2020 16:11 UTC |
Re: Should foreign-status properties be divided into sets or not? |
hga@xxxxxx |
17 Aug 2020 16:17 UTC |
Re: Should foreign-status properties be divided into sets or not? |
Marc Nieper-Wißkirchen |
17 Aug 2020 16:25 UTC |
Re: Should foreign-status properties be divided into sets or not? |
hga@xxxxxx |
17 Aug 2020 16:33 UTC |
Re: Should foreign-status properties be divided into sets or not? |
Marc Nieper-Wißkirchen |
17 Aug 2020 17:06 UTC |
Re: Passing symbols to say where errors came from? |
John Cowan |
17 Aug 2020 17:28 UTC |
Re: New draft (#3) of SRFI 198: Foreign Interface Status [renamed] |
Arthur A. Gleckler |
17 Aug 2020 18:43 UTC |
Re: Passing symbols to say where errors came from? |
hga@xxxxxx |
17 Aug 2020 19:05 UTC |
SRFI 170 versus process SRFI |
John Cowan |
17 Aug 2020 19:27 UTC |
Re: Why plists? |
Marc Nieper-Wißkirchen |
17 Aug 2020 19:36 UTC |
Re: Why plists? |
hga@xxxxxx |
17 Aug 2020 20:42 UTC |
Re: Why plists? |
Marc Nieper-Wißkirchen |
17 Aug 2020 21:10 UTC |
Re: Why plists? |
hga@xxxxxx |
17 Aug 2020 22:05 UTC |
Re: Passing symbols to say where errors came from? |
Shiro Kawai |
17 Aug 2020 22:20 UTC |
Re: New draft (#3) of SRFI 198: Foreign Interface Status [renamed] |
Arthur A. Gleckler |
18 Aug 2020 05:45 UTC |
Re: Why plists? |
Marc Nieper-Wißkirchen |
18 Aug 2020 06:09 UTC |
Re: Passing symbols to say where errors came from? |
Marc Nieper-Wißkirchen |
18 Aug 2020 09:24 UTC |
Re: Why plists? |
hga@xxxxxx |
18 Aug 2020 09:50 UTC |
Re: Why plists? |
Marc Nieper-Wißkirchen |
18 Aug 2020 19:18 UTC |
Re: Why plists? |
John Cowan |
18 Aug 2020 19:46 UTC |
Changes to SRFI 170 |
John Cowan |
18 Aug 2020 20:00 UTC |
Re: Why plists? |
Marc Nieper-Wißkirchen |
18 Aug 2020 20:16 UTC |
Re: Why plists? |
John Cowan |
18 Aug 2020 22:32 UTC |
author Github links for 170, 178, 181, 194, 196, and 198 |
Arthur A. Gleckler |
18 Aug 2020 23:14 UTC |
Re: author Github links for 170, 178, 181, 194, 196, and 198 |
Arthur A. Gleckler |
19 Aug 2020 11:30 UTC |
Arguments |
Marc Nieper-Wißkirchen |
30 Aug 2020 12:36 UTC |
SRFI 198 and the Schemeregistry |
hga@xxxxxx |
30 Aug 2020 14:01 UTC |
Re: SRFI 198 and the Schemeregistry |
Lassi Kortela |
30 Aug 2020 14:24 UTC |
Re: SRFI 198 and the Schemeregistry |
hga@xxxxxx |
30 Aug 2020 14:52 UTC |
Re: SRFI 198 and the Schemeregistry |
Lassi Kortela |
30 Aug 2020 14:55 UTC |
Re: SRFI 198 and the Schemeregistry |
John Cowan |
30 Aug 2020 15:22 UTC |
Re: SRFI 198 and the Schemeregistry |
Lassi Kortela |
30 Aug 2020 15:23 UTC |
Re: SRFI 198 and the Schemeregistry |
hga@xxxxxx |
30 Aug 2020 15:35 UTC |
Re: SRFI 198 and the Schemeregistry |
Lassi Kortela |
30 Aug 2020 15:44 UTC |
Re: SRFI 198 and the Schemeregistry |
Lassi Kortela |
30 Aug 2020 15:45 UTC |
Re: SRFI 198 and the Schemeregistry |
hga@xxxxxx |
30 Aug 2020 16:02 UTC |
Re: SRFI 198 and the Schemeregistry |
Marc Nieper-Wißkirchen |
30 Aug 2020 16:05 UTC |
Re: SRFI 198 and the Schemeregistry |
John Cowan |
30 Aug 2020 16:06 UTC |
Re: SRFI 198 and the Schemeregistry |
Lassi Kortela |
30 Aug 2020 16:38 UTC |
Re: SRFI 198 and the Schemeregistry |
Lassi Kortela |
30 Aug 2020 16:56 UTC |
Re: SRFI 198 and the Schemeregistry |
Lassi Kortela |
30 Aug 2020 17:05 UTC |
Re: SRFI 198 and the Schemeregistry |
Lassi Kortela |
30 Aug 2020 17:33 UTC |
Re: SRFI 198 and the Schemeregistry |
hga@xxxxxx |
30 Aug 2020 17:47 UTC |
Re: SRFI 198 and the Schemeregistry |
John Cowan |
30 Aug 2020 17:54 UTC |
Re: SRFI 198 and the Schemeregistry |
John Cowan |
30 Aug 2020 18:26 UTC |
Re: SRFI 198 and the Schemeregistry |
Arthur A. Gleckler |
30 Aug 2020 18:56 UTC |
Re: SRFI 198 and the Schemeregistry |
John Cowan |
30 Aug 2020 18:57 UTC |
Re: SRFI 198 and the Schemeregistry |
Lassi Kortela |
30 Aug 2020 18:59 UTC |
Re: SRFI 198 and the Schemeregistry |
Lassi Kortela |
30 Aug 2020 19:09 UTC |
Re: SRFI 198 and the Schemeregistry |
Arthur A. Gleckler |
30 Aug 2020 19:28 UTC |
Don't panic |
Lassi Kortela |
30 Aug 2020 19:34 UTC |
Re: Don't panic |
Marc Nieper-Wißkirchen |
30 Aug 2020 19:44 UTC |
Re: SRFI 198 and the Schemeregistry |
Marc Nieper-Wißkirchen |
30 Aug 2020 19:57 UTC |
Re: SRFI 198 and the Schemeregistry |
Lassi Kortela |
30 Aug 2020 20:00 UTC |
Re: Don't panic |
Arthur A. Gleckler |
30 Aug 2020 20:09 UTC |
Re: SRFI 198 and the Schemeregistry |
John Cowan |
30 Aug 2020 20:13 UTC |
Re: SRFI 198 and the Schemeregistry |
hga@xxxxxx |
30 Aug 2020 22:20 UTC |
What to do if two conventions define different meanings to the same required key? |
hga@xxxxxx |