unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Skyler via "Developers list for Guile, the GNU extensibility library" <guile-devel@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: "guile-devel@gnu.org" <guile-devel@gnu.org>
Subject: RE: Removing program-arities export
Date: Mon, 06 Jan 2025 11:01:27 +0000	[thread overview]
Message-ID: <tzMSaEifYECKJsWFM5ZZyIiFWwM_3_d0J28rsc8dsDWaX36PyzWw8TDxEMuAuSMRR6NwyBXQZSDePbyLwZsnaao-b--z_kCgykep8abEKUw=@protonmail.com> (raw)
In-Reply-To: <20250105190726.xW7S2D00948vBLV06W7S96@albert.telenet-ops.be>

[-- Attachment #1: Type: text/plain, Size: 1547 bytes --]

On Sunday, January 5th, 2025 at 6:07 PM, Maxime Devos <maximedevos@telenet.be> wrote:

>>It is only used in the `program-arity function`, which is not called anywhere in the Guile repository (and calling it with valid inputs results in an error due to the `program-arities` being undefined).
>
> This is untrue, it (i.e. program-arities) is also used in the manual.

Fair point.

>>Removing those functions is simple, but the `arity:` accessors have more users, […]
>
> It shouldn’t be removed, rather a replacement should be provided somewhere.
>
> Regardless of the changes to the VM, compiled procedures still exist, and by definition that’s what a ‘program’ is, so ‘programs’ still exist, and hence many of the procedures in that module still make sense, including program-arities. In particular, arity information is still recorded (in .guile.arities), so it should be made / kept accessible somewhere.

I agree that this information should be available. I should have explicated my assumption that the similarly-named function "find-program-arities" was a suitable replacement. It is defined in "system/vm/debug.scm" and references .guile.arities. I will interrogate this assumption more thoroughly before submitting a patch, the email was meant as an early notification that this is something that I'm starting to look at in case someone else is already looking at it. I am fine with changing the direction of the patch if that turns out to make sense (perhaps by turning program-arities an alias for find-program-arities).

>

[-- Attachment #2: Type: text/html, Size: 2938 bytes --]

  reply	other threads:[~2025-01-06 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-29 11:16 Removing program-arities export Skyler via Developers list for Guile, the GNU extensibility library
2025-01-05 18:07 ` Maxime Devos
2025-01-06 11:01   ` Skyler via Developers list for Guile, the GNU extensibility library [this message]
2025-01-08 11:23     ` Skyler Ferris via Developers list for Guile, the GNU extensibility library
2025-01-08 20:21       ` yeRemoving " Dr. Arne Babenhauserheide

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='tzMSaEifYECKJsWFM5ZZyIiFWwM_3_d0J28rsc8dsDWaX36PyzWw8TDxEMuAuSMRR6NwyBXQZSDePbyLwZsnaao-b--z_kCgykep8abEKUw=@protonmail.com' \
    --to=guile-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=skyvine@protonmail.com \
    /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).