From: mikel evins <mevins@me.com>
To: Per Bothner <per@bothner.com>
Cc: mikel evins <mevins@me.com>, kawa@sourceware.org
Subject: Re: Redefinition/re-loading [was: kawa paid support]
Date: Sun, 05 Apr 2015 21:53:00 -0000 [thread overview]
Message-ID: <1D4B54AF-5477-4413-A8BD-EE40D13CC8CB@me.com> (raw)
In-Reply-To: <5521A43D.7070009@bothner.com>
> On Apr 5, 2015, at 4:08 PM, Per Bothner <per@bothner.com> wrote:
>
> Kawa does have "smart" re-loading when you do a require or import.
> This can support the kind of dynamic re-loading you want, though
> you might have to slightly re-organize your code.
>
> To see how it works consider this:
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.
next prev parent reply other threads:[~2015-04-05 21:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 23:05 kawa paid support Per Bothner
2015-04-05 5:01 ` Alcides Flores Pineda
2015-04-05 6:51 ` Per Bothner
2015-04-05 17:11 ` Dan Leslie
2015-04-05 17:30 ` Per Bothner
2015-04-05 17:52 ` Per Bothner
2015-04-05 20:03 ` mikel evins
2015-04-05 20:37 ` Redefinition/re-loading [was: kawa paid support] Per Bothner
2015-04-05 20:49 ` mikel evins
2015-04-05 21:08 ` Per Bothner
2015-04-05 21:53 ` mikel evins [this message]
2015-04-05 22:15 ` Per Bothner
2015-04-05 22:59 ` mikel evins
2015-04-05 23:32 ` mikel evins
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1D4B54AF-5477-4413-A8BD-EE40D13CC8CB@me.com \
--to=mevins@me.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.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).