|
SRFI 231 and empty arrays
Bradley J Lucier
(31 Mar 2026 16:08 UTC)
|
|
Re: SRFI 231 and empty arrays
Bradley J Lucier
(01 Apr 2026 17:50 UTC)
|
|
Re: SRFI 231 and empty arrays
John Cowan
(01 Apr 2026 21:30 UTC)
|
|
Re: SRFI 231 and empty arrays
John Cowan
(01 Apr 2026 21:47 UTC)
|
|
Re: SRFI 231 and empty arrays
Bradley J Lucier
(01 Apr 2026 22:21 UTC)
|
|
Re: SRFI 231 and empty arrays Per Bothner (01 Apr 2026 22:44 UTC)
|
|
Re: SRFI 231 and empty arrays
John Cowan
(01 Apr 2026 23:30 UTC)
|
|
Re: SRFI 231 and empty arrays
Bradley Lucier
(01 Apr 2026 23:43 UTC)
|
|
Re: SRFI 231 and empty arrays
John Cowan
(02 Apr 2026 00:36 UTC)
|
|
Re: SRFI 231 and empty arrays
John Cowan
(01 Apr 2026 23:04 UTC)
|
|
Re: SRFI 231 and empty arrays
Arthur A. Gleckler
(01 Apr 2026 17:57 UTC)
|
I orginally mis-read the SRFI-268 specification - I didn't realize it only provided a way to specify optional lower bunds - but no way specify optional upper bounds. In my opinion, this makes the specification a non-starter. We're discussing that there is no way to specify certains kinds of empty arrays. Additionally, it is highly useful to have an option to specify upper bounds for readability and catching (some) errors. It appears to me that SRFI-268 solves no problems that SRFI 163 doesn't solve, but fails to solve some problems that SRFI-163 does solve. So what is the purpose? -- --Per Bothner xxxxxx@bothner.com http://per.bothner.com/