Re: Flat vs nested alist

Show/hide message thread

Splitting foreign-error:code Lassi Kortela (27 Jul 2020 06:46 UTC)

Re: Splitting foreign-error:code Lassi Kortela (27 Jul 2020 08:26 UTC)

Re: Splitting foreign-error:code Lassi Kortela (27 Jul 2020 08:51 UTC)

Re: Splitting foreign-error:code John Cowan (28 Jul 2020 19:25 UTC)

Re: Splitting foreign-error:code for SRFI 198, Foreign Errors hga@xxxxxx (27 Jul 2020 11:26 UTC)

Re: Splitting foreign-error:code for SRFI 198, Foreign Errors John Cowan (27 Jul 2020 23:22 UTC)

Re: Splitting foreign-error:code for SRFI 198, Foreign Errors hga@xxxxxx (27 Jul 2020 23:40 UTC)

Re: Splitting foreign-error:code for SRFI 198, Foreign Errors Lassi Kortela (27 Jul 2020 23:59 UTC)

Re: Splitting foreign-error:code for SRFI 198, Foreign Errors Lassi Kortela (27 Jul 2020 23:44 UTC)

Flat vs nested alist Lassi Kortela (27 Jul 2020 23:50 UTC)

Re: Flat vs nested alist Lassi Kortela (27 Jul 2020 23:53 UTC)

Re: Flat vs nested alist John Cowan (28 Jul 2020 03:06 UTC)

Pre-SRFI for property list utilities Lassi Kortela (28 Jul 2020 07:35 UTC)

Re: Pre-SRFI for property list utilities hga@xxxxxx (28 Jul 2020 11:00 UTC)

Plist utilities and SRFI 198 Lassi Kortela (28 Jul 2020 11:08 UTC)

Re: Plist utilities and SRFI 198 John Cowan (28 Jul 2020 18:12 UTC)

plist pre-SRFI hga@xxxxxx (12 Aug 2020 15:14 UTC)

Re: plist pre-SRFI John Cowan (12 Aug 2020 15:21 UTC)

Re: plist pre-SRFI John Cowan (12 Aug 2020 15:53 UTC)

Re: plist pre-SRFI hga@xxxxxx (12 Aug 2020 15:58 UTC)

Re: plist pre-SRFI John Cowan (12 Aug 2020 16:59 UTC)

Re: plist pre-SRFI hga@xxxxxx (12 Aug 2020 17:34 UTC)

Re: plist pre-SRFI John Cowan (12 Aug 2020 19:37 UTC)

Use of SRFI 198 in SRFI 170 hga@xxxxxx (12 Aug 2020 20:04 UTC)

Re: Splitting foreign-error:code for SRFI 198, Foreign Errors hga@xxxxxx (28 Jul 2020 00:29 UTC)

Re: Splitting foreign-error:code for SRFI 198, Foreign Errors Lassi Kortela (28 Jul 2020 09:10 UTC)

Re: Splitting foreign-error:code for SRFI 198, Foreign Errors hga@xxxxxx (28 Jul 2020 14:15 UTC)

Re: Flat vs nested alist Lassi Kortela 27 Jul 2020 23:53 UTC

> If we have a flat alist, we might as well use a plist which leads to
> more Lispy constructor syntax, similar to keyword arguments:
>
> (make-foreign-error
>   'error-set errno
>   'code 2
>   'symbol ENOENT
>   'scheme-procedure open-file
>   'foreign-interface open
>   'message "open-file called open: ..."
>   'arguments '("not-a-valid-filename" 0 428)
>   'heritage "SRFI 170")

Adding the missing single quotes:

(make-foreign-error
  'error-set 'errno
  'code 2
  'symbol 'ENOENT
  'scheme-procedure 'open-file
  'foreign-interface 'open
  'message "open-file called open: ..."
  'arguments '("not-a-valid-filename" 0 428)
  'heritage "SRFI 170")