This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: the right way to compile and load modules
- From: mikel evins <mevins at me dot com>
- To: Per Bothner <per at bothner dot com>
- Cc: mikel evins <mevins at me dot com>, kawa at sourceware dot org
- Date: Wed, 14 May 2014 01:51:45 -0500
- Subject: Re: the right way to compile and load modules
- Authentication-results: sourceware.org; auth=none
- References: <9F312D97-98C6-4F47-BDD9-B6CAF3868A28 at me dot com> <5371CFD0 dot 7070708 at bothner dot com> <7D1A5D60-5997-4B7A-9176-8F6FA315F016 at me dot com> <ED4375FE-30EE-4ABC-A9DC-2C6C4D67A87A at me dot com> <54132084-D633-4AAA-B2A4-9008FF37F779 at me dot com> <5372CA25 dot 7050602 at bothner dot com> <B01E0129-CA46-46DF-B6F1-65C33CC5A0BC at me dot com> <5372E86B dot 9020600 at bothner dot com> <61B59A7F-0868-48D1-9C18-DFDD6C09850E at me dot com> <53730D3A dot 4040904 at bothner dot 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.