This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: Using Kawa extensions in R7RS libraries
- From: Per Bothner <per at bothner dot com>
- To: ElÃas Alonso G.-Cornejo <eliasagc at gmail dot com>
- Cc: kawa mailing list <kawa at sourceware dot org>
- Date: Sun, 12 Jul 2015 17:16:13 -0700
- Subject: Re: Using Kawa extensions in R7RS libraries
- Authentication-results: sourceware.org; auth=none
- References: <m28ug38opn dot fsf at gmail dot com> <54DCE968 dot 7000800 at bothner dot com> <m2d25aaoj7 dot fsf at gmail dot com> <54E2DE69 dot 2060708 at bothner dot com> <851CA162-87C3-4161-BD7D-338E6AC34FEC at theptrgroup dot com> <552B70EC dot 8040608 at bothner dot com> <CANfjrNW0FFmM3Xp5gX+BNqAbq2Y=C2OiuHYEXv50Y09r9NWipA at mail dot gmail dot com> <559958AE dot 2060101 at bothner dot com> <CANfjrNWYi8Hj78rAuMFMeROobWYUnzgCXU6NQNoPKiA9PP9hGQ at mail dot gmail dot com>
On 07/06/2015 12:29 AM, ElÃas Alonso G.-Cornejo wrote:
The patch works correctly but raises another issue: (future ...) and
(runnable ...) are not included in (kawa base).
'runnable' appears to have been in (kawa base).
I also added 'future' and 'sleep.'
I don't know if they
should be included, but if I require kawa/lib/thread.scm with (import
thread), any attempt to call (future ...) will show the following
message:
warning - no declaration seen for lambda
And fail. I fixed it by adding (import (scheme base)) at the top of
kawa/lib/thread.scm but I'm not sure if that's the best way to do it.
Yes, that is the correct idea, though I used prim_imports instead.
--
--Per Bothner
per@bothner.com http://per.bothner.com/