|
The name of "keyword-call"
John Cowan
(22 Oct 2019 19:42 UTC)
|
|
Re: The name of "keyword-call"
Lassi Kortela
(22 Oct 2019 19:56 UTC)
|
|
Re: The name of "keyword-call"
Marc Nieper-Wißkirchen
(23 Oct 2019 06:00 UTC)
|
|
Re: The name of "keyword-call"
Lassi Kortela
(23 Oct 2019 07:32 UTC)
|
|
Re: The name of "keyword-call"
Rhys Ulerich
(23 Oct 2019 12:10 UTC)
|
|
Re: The name of "keyword-call" Marc Nieper-Wißkirchen (23 Oct 2019 13:37 UTC)
|
|
Re: The name of "keyword-call"
John Cowan
(23 Oct 2019 13:52 UTC)
|
|
Re: The name of "keyword-call"
Lassi Kortela
(23 Oct 2019 14:03 UTC)
|
|
Re: The name of "keyword-call"
John Cowan
(23 Oct 2019 14:23 UTC)
|
|
Re: The name of "keyword-call"
Marc Nieper-Wißkirchen
(23 Oct 2019 14:34 UTC)
|
|
Re: The name of "keyword-call"
John Cowan
(23 Oct 2019 15:47 UTC)
|
Re: The name of "keyword-call" Marc Nieper-WiÃkirchen 23 Oct 2019 13:37 UTC
Am Mi., 23. Okt. 2019 um 14:10 Uhr schrieb Rhys Ulerich <xxxxxx@gmail.com>: > > > The name "kcall" is as short as "apply". Should it be even shorter? > > Does it violate some convention to choose call-with-keywords and to allow the shorthand call/kw? The prefix "call-with-XXX" is used for procedures that, when called, call one of their arguments, supplying some XXX as the argument for that call. So "call-with-XXX" (and "call/XX") instead of "kcall" seems to follow the tradition. What may be debatable is the suffix "keywords"/"kw" as the procedure called is not called with keywords but with keyword arguments. Marc