From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org, spikegran@earthlink.net
Subject: Re: Guile top-level functions
Date: Thu, 20 Jan 2005 09:15:33 +1100 [thread overview]
Message-ID: <87acr5uku2.fsf@zip.com.au> (raw)
In-Reply-To: <41EED39C.3080906@ossau.uklinux.net> (Neil Jerram's message of "Wed, 19 Jan 2005 21:39:40 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
>
> guile> (source-properties (caddr (procedure-source callback)))
> ((breakpoint . #f) (line . 1) (column . 26) (filename . "standard input"))
Sweet. I've already got my own backtrace, so I can plug that in
easily. I'll use it for my lint program too I think.
Doesn't work in the cvs head though, it seems. Unmemoizing like you
said before maybe.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2005-01-19 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 19:54 Guile top-level functions Mike Gran
2005-01-17 0:05 ` Kevin Ryde
2005-01-17 8:38 ` Neil Jerram
2005-01-17 22:20 ` Kevin Ryde
2005-01-17 23:15 ` Neil Jerram
2005-01-18 0:23 ` Kevin Ryde
2005-01-19 21:39 ` Neil Jerram
2005-01-19 22:15 ` Kevin Ryde [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=87acr5uku2.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-user@gnu.org \
--cc=spikegran@earthlink.net \
/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).