From: Patrick McCarty <INVALID.NOREPLY@gnu.org>
To: Andy Wingo <wingo@pobox.com>, Patrick McCarty <pnorcks@gmail.com>,
bug-guile@gnu.org
Subject: [bug #30469] `procedure-source' is broken in Guile 1.9.11
Date: Fri, 23 Jul 2010 16:46:20 +0000 [thread overview]
Message-ID: <20100723-094620.sv74381.39458@savannah.gnu.org> (raw)
In-Reply-To: <20100719-192229.sv20118.15312@savannah.gnu.org>
Follow-up Comment #2, bug #30469 (project guile):
I discovered this while debugging a compile failure with LilyPond...
LilyPond's autogenerated documentation of its internal procedures uses
`procedure-source' to access the signature of a given procedure.
Would you recommend a different solution for this?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30469>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
next prev parent reply other threads:[~2010-07-23 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-18 0:02 [bug #30469] `procedure-source' is broken in Guile 1.9.11 Patrick McCarty
[not found] ` <20100719-192229.sv20118.15312@savannah.gnu.org>
2010-07-23 16:46 ` Patrick McCarty [this message]
2011-02-13 19:05 ` Andy Wingo
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=20100723-094620.sv74381.39458@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=pnorcks@gmail.com \
--cc=wingo@pobox.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).