From: tomas@tuxteam.de
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: guile-user@gnu.org
Subject: Re: Writing a procedure in different style
Date: Mon, 21 Dec 2020 13:31:48 +0100 [thread overview]
Message-ID: <20201221123147.GC3816@tuxteam.de> (raw)
In-Reply-To: <93cfbdc6-a013-d6c8-15a7-b2d2feb2455a@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
On Sun, Dec 20, 2020 at 06:57:34PM +0100, Zelphir Kaltstahl wrote:
> Hello Tomas!
>
> I think you are right about it only being down one stack frame down. The
> checks are performed on what contains the next thing which is recurred on.
Nice explanation :)
> For a moment I thought "But isn't the null? check done twice in the
> first cond part?" [...]
This is one of the fantastic (and scary) things I often experience
in this (scheme-y) context (take SICP, or the Little Schemer).
Everything looks so easy, but whenever I try myself, I realise that
I've been taken along a path along high mountains, with breathtaking
views, and down there it gets messy and there are crocodiles.
It takes a long time to massage one's messy, lowly programs into a
form which approaches that deep beauty.
But it's fun :)
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-12-21 12:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 12:22 Writing a procedure in different style Zelphir Kaltstahl
2020-12-13 7:06 ` Taylan Kammer
2020-12-13 11:51 ` Taylan Kammer
2020-12-13 12:29 ` Zelphir Kaltstahl
2020-12-13 14:24 ` tomas
2020-12-13 15:01 ` Zelphir Kaltstahl
2020-12-13 15:43 ` tomas
2020-12-20 17:57 ` Zelphir Kaltstahl
2020-12-21 12:31 ` tomas [this message]
2020-12-21 21:29 ` Zelphir Kaltstahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201221123147.GC3816@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=guile-user@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).