From: Daniel Hartwig <mandyke@gmail.com>
To: guile-devel@gnu.org
Subject: Re: [PATCH] Add inspection command "source (, src)" which shows Scheme code of loaded module
Date: Sun, 31 Mar 2013 08:33:56 +0800 [thread overview]
Message-ID: <CAN3veRe+e_kdGo1pB1+zvV47F_ibW61MrFSLjx=F8CQzBmQzCg@mail.gmail.com> (raw)
In-Reply-To: <87zjxk7fjy.fsf@tines.lan>
On 31 March 2013 05:17, Mark H Weaver <mhw@netris.org> wrote:
> Nala Ginrut <nalaginrut@gmail.com> writes:
>> +
>> +(define (print-src p)
>> + (define (get-program-src p)
>> + (let ((source (program-source p 0)))
>> + (cond
>> + ((not source) "It's inner procedure implemented with C")
>
> I'm not sure we can conclude that the procedure is implemented in C just
> because 'program-source' returns #f. There might be other reasons why
> that might happen.
>
Yes right, instead of trying to interpret the meaning and display a
message, returning ‘#f’ like e.g. ‘describe’ should be sufficient.
This is enough of a clue to indicate that the material is not
available.
next prev parent reply other threads:[~2013-03-31 0:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 13:57 [PATCH] Add inspection command "source (,src)" which shows Scheme code of loaded module Nala Ginrut
2013-03-30 21:17 ` [PATCH] Add inspection command "source (, src)" " Mark H Weaver
2013-03-31 0:33 ` Daniel Hartwig [this message]
2013-03-31 12:47 ` [PATCH] Add inspection command "source (,src)" " Nala Ginrut
2013-04-01 0:42 ` [PATCH] Add inspection command "source (, src)" " Daniel Hartwig
2013-04-01 3:54 ` Mark H Weaver
2013-04-01 4:22 ` Daniel Hartwig
2013-04-01 19:12 ` Andy Wingo
2013-04-23 7:26 ` Show source code from .debug_info section (Was Re: [PATCH] Add inspection command "source (, src)" which shows Scheme code of loaded module) Nala Ginrut
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='CAN3veRe+e_kdGo1pB1+zvV47F_ibW61MrFSLjx=F8CQzBmQzCg@mail.gmail.com' \
--to=mandyke@gmail.com \
--cc=guile-devel@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).