From: mikel evins <mevins@me.com>
To: Per Bothner <per@bothner.com>
Cc: mikel evins <mevins@me.com>, kawa@sourceware.org
Subject: Re: the right way to compile and load modules
Date: Wed, 14 May 2014 06:52:00 -0000 [thread overview]
Message-ID: <7F193E7B-AF6B-49B6-B8B6-58A8E686E301@me.com> (raw)
In-Reply-To: <53730D3A.4040904@bothner.com>
On May 14, 2014, at 1:29 AM, Per Bothner <per@bothner.com> wrote:
> On 05/13/2014 08:59 PM, mikel evins wrote:
>>
>> On May 13, 2014, at 10:52 PM, Per Bothner <per@bothner.com> wrote:
>>> Still need to look into what is going on, but I suggest replacing the
>>> (require "fact.scm")
>>> by:
>>> (require fact)
>>
>> Here's why I'm not doing that:
>>
>> $ ant factest
>> Buildfile: /Users/mikel/Workshop/fabric/build.xml
>>
>> fact:
>> [kawa] (compiling fact.scm to fact)
>>
>> factest:
>> [kawa] (compiling factest.scm to factest)
>> [kawa] factest.scm:3:1: invalid specifier for 'require'
>>
>> BUILD FAILED
>
> This means it couldn't find the class 'test'. You means to tweak the
> classpath (when compiling facttest) so it finds fact.class.
>
> This error message is rather unhelpful; I checked in an improvement.
Thanks; that solved it for the test program. The real deal still doesn't compile using class names instead of source-file names, but I'll assume that's because of something I've overlooked and can find with further examination.
Have I mentioned lately how great Kawa is? I've used it before, though it's been some years. I picked it again for this project after a short period of trying it alongside ABCL and Clojure. I like Common Lisp just fine, and I like Clojure too, but Kawa was just easier to work with and faster. I'm particularly impressed by its quick launch times compared to other JVM tools.
next prev parent reply other threads:[~2014-05-14 6:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 4:09 mikel evins
2014-05-13 7:29 ` Charles Turner
2014-05-13 7:45 ` mikel evins
2014-05-13 7:49 ` Per Bothner
2014-05-13 7:55 ` Per Bothner
2014-05-13 8:02 ` mikel evins
2014-05-13 8:40 ` mikel evins
2014-05-13 10:23 ` mikel evins
2014-05-14 1:13 ` mikel evins
2014-05-14 1:19 ` parameters not working? mikel evins
2014-05-14 1:31 ` Per Bothner
2014-05-14 1:41 ` mikel evins
2014-05-14 2:12 ` mikel evins
2014-05-14 2:19 ` mikel evins
2014-05-14 9:32 ` mikel evins
2014-05-14 16:07 ` Per Bothner
2014-05-14 1:43 ` the right way to compile and load modules Per Bothner
2014-05-14 1:50 ` mikel evins
2014-05-14 2:05 ` mikel evins
2014-05-14 3:52 ` Per Bothner
2014-05-14 3:59 ` mikel evins
2014-05-14 6:29 ` Per Bothner
2014-05-14 6:52 ` mikel evins [this message]
2014-05-14 18:59 ` Kawa experience [was: the right way to compile and load modules] Per Bothner
2014-05-14 20:06 ` Charles Turner
2014-05-15 2:16 ` mikel evins
2014-05-14 7:26 ` the right way to compile and load modules mikel evins
2014-05-14 7:33 ` Per Bothner
2014-05-14 7:35 ` mikel evins
2014-05-14 18:46 ` Per Bothner
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=7F193E7B-AF6B-49B6-B8B6-58A8E686E301@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).