This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: Redefinition/re-loading [was: kawa paid support]
- From: Per Bothner <per at bothner dot com>
- To: mikel evins <mevins at me dot com>
- Cc: kawa at sourceware dot org
- Date: Sun, 05 Apr 2015 15:15:33 -0700
- Subject: Re: Redefinition/re-loading [was: kawa paid support]
- Authentication-results: sourceware.org; auth=none
- References: <5519D688 dot 7080704 at bothner dot com> <5520C199 dot 9010705 at gmail dot com> <5520DB6D dot 6060208 at bothner dot com> <20755B3D-7B83-4772-A18C-E62901015DAD at me dot com> <55219CE9 dot 3080207 at bothner dot com> <5521A43D dot 7070009 at bothner dot com> <1D4B54AF-5477-4413-A8BD-EE40D13CC8CB at me dot com>
On 04/05/2015 02:53 PM, mikel evins wrote:
Yeah, this is already how I do things. I still need to restart Kawa
on pretty much any significant edit, or I get stack traces that
disappear when I do restart it.
I don't pretend to understand the problem deeply, because I've simply
done what I needed to do to make the stack traces disappear. If you
want me to examine things more closely, I'd be happy to do so. We
just need to talk about what you'd like me to try.
Yes, it would be useful to know where the stack trace is coming from.
It would be useful to in each foo.scm add a
(format #t "loading foo.scm~%")
That will help see which modules are loaded and when.
If you modify function f, you want all modules that depend on f
(directly and indirectly) to get re-loaded. The exception is f
is used as an untyped procedure value - for example stached somewhere
and then used as the argument to apply.
As a check: I hope you're using require or import, not load to load
your modules.
--
--Per Bothner
per@bothner.com http://per.bothner.com/