From: mikel evins <mevins@me.com>
To: Charles Turner <chturne@gmail.com>
Cc: mikel evins <mevins@me.com>, Kawa mailing list <kawa@sourceware.org>
Subject: Re: the right way to compile and load modules
Date: Tue, 13 May 2014 07:45:00 -0000 [thread overview]
Message-ID: <B9933B97-4D98-489D-8792-AD6D7018B9DE@me.com> (raw)
In-Reply-To: <CAPMhJv3mgSgwP_OxUbVR85pH7crgyunz2q-b2i2-iC2wA+=agQ@mail.gmail.com>
On May 13, 2014, at 2:29 AM, Charles Turner <chturne@gmail.com> wrote:
> Hi Mikel,
>
> Can you post your test code so that the people on this list can see
> what you're trying to do?
Your code is not significantly different from what I would provide. In fact, it closely resembles my own test case.
I don't mind supplying a boiled-down test case, but I doubt it will shed any new light.
> At this point, the BAR procedure from bar.scm is publicly visible
> (exported) as you correctly said. I'm guessing your first runtime
> error is because you're not
> requiring (using REQUIRE) or loading (using LOAD) the bar.scm file from foo.scm.
No; I see the same error if I require the file unless the required file contains a module-export form.
> I now compile these files like so,
> prompt> java kawa.repl -C bar.scm
> prompt> java jawa.repl --main -C foo.scm
>
> I'm guessing that you're second observation about Kawa "complains that
> bar is exported but never defined" is because you're compiling bar.scm
> with the --main switch.
No; I see the warnings when loading interactively into the repl, not when compiling.
I'd like to reach a state where I can work interactively without seeing gobs of warnings, and where I can also compile the same sources to an executable jar.
I'm partway there; I can in fact build an executable jar. I can also load the code into an interactive session; I just can't do so without kawa spewing warnings at me.
next prev parent reply other threads:[~2014-05-13 7:45 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 [this message]
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
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=B9933B97-4D98-489D-8792-AD6D7018B9DE@me.com \
--to=mevins@me.com \
--cc=chturne@gmail.com \
--cc=kawa@sourceware.org \
/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).