From: <tomas@tuxteam.de>
To: guile-user@gnu.org
Subject: Re: trace-calls-to-procedure
Date: Fri, 25 Dec 2020 09:42:36 +0100 [thread overview]
Message-ID: <20201225084236.GA16738@tuxteam.de> (raw)
In-Reply-To: <3c36067b-5247-03a0-ab64-b4241a8fea30@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
On Fri, Dec 25, 2020 at 06:58:00AM +0100, Zelphir Kaltstahl wrote:
> Hi Tim!
>
> I do not know the answer to your question, but I noticed something else:
> trace-calls-to-procedure returns a procedure. That procedure and its
> return value can be applied infinitely, it seems:
[...]
> Not sure if that helps :D
Not the OP here, but look at what you've done: now I feel dizzy %-)
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2020-12-25 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 4:51 trace-calls-to-procedure Tim Meehan
2020-12-25 5:58 ` trace-calls-to-procedure Zelphir Kaltstahl
2020-12-25 8:42 ` tomas [this message]
2020-12-26 1:23 ` trace-calls-to-procedure Tim Meehan
2020-12-25 12:37 ` trace-calls-to-procedure Tim Van den Langenbergh
2020-12-25 14:56 ` trace-calls-to-procedure Tim Van den Langenbergh
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=20201225084236.GA16738@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=guile-user@gnu.org \
/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).