Am Fr., 14. Okt. 2022 um 18:29 Uhr schrieb Daphne Preston-Kendal
<xxxxxx@nonceword.org>:
>
> I will delete comparison-procedures and express a wish in the ‘future work’ section for a SRFI providing it. (Despite what I wrote on the SRFI 237 list, a hygiene-breaking macro, automatically defining xyz=?, xyz<? etc from a given base name xyz, might be the best solution …)

Suggestion: Something like:

(define-comparisons PREFIX COMPARATOR-EXPRESSION SYMBOL ...)

where SYMBOL is one of <. >, <=, etc.

> The other remaining issue is with the implementation, which I will fix asap
>
> unterwegs mit Händi gesendet
> entschuldige(n Sie) bitte Tippfehler und Top Posting
>
> On 14 Oct 2022, at 08:34, Marc Nieper-Wißkirchen <xxxxxx@gmail.com> wrote:
>
> Two more comments:
>
> - The last sentence of make-sum-comparator is a copy-and-paste error.
>
> - Change comparison-procedures into a macro (where you can have
> keyword-like arguments as much as you would like to have) or replace
> it with a macro define-comparators (that can implicitly create names)
> to make it actually usable. Or drop it and possibly postpone it to a
> future SRFI (it does not have much to do with the make-???-comparator
> procedures anyway
>
> Am Fr., 14. Okt. 2022 um 01:52 Uhr schrieb Arthur A. Gleckler
> <xxxxxx@speechcode.com>:
>
>
> Hello, Daphne.  I haven't received any response from you about SRFI 228 since May, so I'm planning to withdraw it on 2022-10-21 unless I hear from you.
>
>
> There are only a few unresolved email threads:
>
>
> Making the `comparison-procedures` procedure more usable
>
> Some remarks on the implementation
>
> SRFI 228: Abstract still mentions macros (which were removed)
>
>
> If you like, I can send you an archive of those.
>
>
> Thanks very much for your contributions.  I look forward to hearing from you soon.