From: tomas@tuxteam.de
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Applicable structs and vtables
Date: Sat, 14 Aug 2021 12:40:56 +0200 [thread overview]
Message-ID: <20210814104056.GA22710@tuxteam.de> (raw)
In-Reply-To: <4f308868-fb6b-6557-76a8-1c3481983a48@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
On Sat, Aug 14, 2021 at 09:19:49AM +0000, Zelphir Kaltstahl wrote:
> Hi Tomas!
>
> Ultimately I need the minimum and maximum arity of functions [...]
It seems that the second number in `procedure-minimum-arity's result
is the number of optional arguments (cf. `define*'). Since Guile 2.0,
optional args are in the core.
So that still might fit your bill. Or perhaps not ;-)
Cheers
- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2021-08-14 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 20:33 Applicable structs and vtables Zelphir Kaltstahl
2021-08-14 6:53 ` tomas
2021-08-14 9:19 ` Zelphir Kaltstahl
2021-08-14 10:40 ` tomas [this message]
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=20210814104056.GA22710@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).