Announcement Loop Facility
Marc Nieper-Wißkirchen
(16 Aug 2022 08:31 UTC)
|
Re: Announcement Loop Facility
Lassi Kortela
(16 Aug 2022 09:03 UTC)
|
Re: Announcement Loop Facility
Vladimir Nikishkin
(16 Aug 2022 09:24 UTC)
|
Re: Announcement Loop Facility
Marc Nieper-Wißkirchen
(16 Aug 2022 09:43 UTC)
|
Re: Announcement Loop Facility
Marc Nieper-Wißkirchen
(16 Aug 2022 10:01 UTC)
|
Re: Announcement Loop Facility
Ricardo G. Herdt
(16 Aug 2022 10:04 UTC)
|
Re: Announcement Loop Facility
Lassi Kortela
(16 Aug 2022 10:17 UTC)
|
Re: Announcement Loop Facility
Ricardo G. Herdt
(16 Aug 2022 10:22 UTC)
|
Re: Announcement Loop Facility
Marc Nieper-Wißkirchen
(16 Aug 2022 10:39 UTC)
|
Name of the loop macro Lassi Kortela (16 Aug 2022 10:55 UTC)
|
Re: Name of the loop macro
John Cowan
(16 Aug 2022 11:03 UTC)
|
Re: Name of the loop macro
Jakub T. Jankiewicz
(16 Aug 2022 11:18 UTC)
|
Re: Name of the loop macro
Marc Nieper-Wißkirchen
(16 Aug 2022 11:25 UTC)
|
Changing the binding of quote et.al.
Lassi Kortela
(16 Aug 2022 11:46 UTC)
|
Re: Name of the loop macro
John Cowan
(16 Aug 2022 11:57 UTC)
|
Re: Name of the loop macro
Marc Nieper-Wißkirchen
(16 Aug 2022 12:33 UTC)
|
Re: Name of the loop macro
Marc Nieper-Wißkirchen
(16 Aug 2022 11:16 UTC)
|
> Yes, I plan to name the macro "loop". Perhaps "loop*" would be a decent alternative? By analogy to let*. > At least in R[67]RS, it won't > clash with locally defined variables named "loop". Thanks to the > rename facility of the R[67]RS module system, it can also peacefully > coexist with other loop facilities named "loop" as well. Indeed. It's one of the best features of Scheme that it doesn't have any reserved words. Scheme is the only language I know where the module system isn't painful to use.