Re: Re: Threading / Pipe Macro (Chris Vine, Mark H Weaver)

[Zelphir Kaltstahl]

Ah, I must have mixed it up when copying it out of the e-mail. It was
good to understand that macro nevertheless. I'll use the hygienic one
then or the one from Linus repository, because it does something, that I
thought would be very useful to have: A configurable place where to put
the value from the previous step of computation. In fact, I did not
understand at first what `<>` and `<...>` do, and thought maybe I could
try and write one which uses `_` to achieve this effect, but then I read
the examples in the follow-up e-mails and saw, that that macro already
does it. This is great!

On 7/9/19 11:26 AM, address@hidden wrote:
> Date: Tue, 9 Jul 2019 00:00:51 +0100
> From: Chris Vine <address@hidden>
> To: address@hidden
> Subject: Re: Threading / Pipe Macro (Chris Vine, Mark H Weaver)
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=US-ASCII
>
> On Mon, 8 Jul 2019 23:10:28 +0200t
> Zelphir Kaltstahl <address@hidden> wrote:
>> Hello Chris and hello Mark,
>>
>> Thank you both for posting your macros! This is really useful and I am
>> looking forward to using this in the next situation where there would be
>> deep nesting or where it seems appropriate in other ways.
>>
>> To understand what is going on in the macro, I wrote a lot of explaining
>> comments and uploaded it in a new repository, where I intend to keep
>> macros I come across and explain them, if I can:
>>
>> https://gitlab.com/ZelphirKaltstahl/guile-scheme-macros/blob/master/threading-pipe-macro/macro.scm
> You are using the wrong macro, because the one you have chosen has been
> revealed to be unhygienic.  Either use the syntax-rules one (which is
> the simplest) or the revised syntax-case macro.