Re: HTTP error codes
hga@xxxxxx
(03 Aug 2020 16:47 UTC)
|
Re: HTTP error codes
John Cowan
(03 Aug 2020 17:04 UTC)
|
Re: HTTP error codes
John Cowan
(03 Aug 2020 17:07 UTC)
|
Complexity of SRFI 198 interface and naming
Lassi Kortela
(03 Aug 2020 17:15 UTC)
|
Re: Complexity of SRFI 198 interface and naming
hga@xxxxxx
(03 Aug 2020 17:52 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
John Cowan
(04 Aug 2020 15:52 UTC)
|
Re: Complexity of SRFI 198 interface and naming
hga@xxxxxx
(04 Aug 2020 16:24 UTC)
|
Re: Complexity of SRFI 198 interface and naming
Lassi Kortela
(04 Aug 2020 16:36 UTC)
|
Re: Complexity of SRFI 198 interface and naming
John Cowan
(05 Aug 2020 02:30 UTC)
|
Re: Complexity of SRFI 198 interface and naming
John Cowan
(03 Aug 2020 17:53 UTC)
|
Re: Complexity of SRFI 198 interface and naming
Lassi Kortela
(03 Aug 2020 18:06 UTC)
|
> Or just drop the ". args" convenience feature, and always return > whatever's there, lambda or not. Based on whatever is specified in > the SRFI's use of lambdas for localization, or the conventions of the > error-set collection, the user, IDE, whatever then calls the lambda > with the correct arguments, if any. That may end up being the best idea in the end. Thanks for being an advocate of simplicity. > Making the API regular is more important than a bit of convenience, > especially given how fundamental lambdas are to Scheme. That's true, and regularity is a particular virtue of Scheme as compared to most other languages, even to other Lisps. However, the ubiquity of lambdas also means that they are quite cheap both syntax- and efficiency-wise so we shouldn't worry too much about sprinkling them around.