From: mikel evins <mevins@me.com>
To: Per Bothner <per@bothner.com>
Cc: mikel evins <mevins@me.com>,
"Rafik Naccache (TNTeam Rocks!)" <rafik@tnteam.rocks>,
kawa@sourceware.org
Subject: Re: What is the Development Environment of Choice for Kawa?
Date: Thu, 18 Feb 2016 21:22:00 -0000 [thread overview]
Message-ID: <FBA2ACC9-031D-40EE-83E3-6CB81E0A7FF5@me.com> (raw)
In-Reply-To: <56C6351E.90107@bothner.com>
> On Feb 18, 2016, at 3:18 PM, Per Bothner <per@bothner.com> wrote:
>
> Until then, you can try the --no-inline flag, and be prepared to re-load
> everything after changes. One of the big advantages of Kawa that its
> fast compiler and loading makes re-starting ok.
Depends on what you mean by “ok.” It’s virtually instant, so if the time it takes is the main consideration, it’s better than “ok”.
next prev parent reply other threads:[~2016-02-18 21:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3go6arm3yvsi6iuungnfyd1o.1455824305674@email.android.com>
2016-02-18 21:18 ` RE : " Per Bothner
2016-02-18 21:22 ` mikel evins [this message]
2016-02-18 22:24 ` Rafik
2016-02-18 22:38 ` Per Bothner
2016-02-19 0:09 ` Alex Shinn
2016-02-18 18:53 F. Rafael Leon
-- strict thread matches above, loose matches on Subject: below --
2016-02-18 16:18 Rafik
2016-02-18 18:57 ` Per Bothner
2016-02-18 19:39 ` mikel evins
2016-02-18 19:59 ` Dominique Boucher
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=FBA2ACC9-031D-40EE-83E3-6CB81E0A7FF5@me.com \
--to=mevins@me.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
--cc=rafik@tnteam.rocks \
/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).