[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-janitors] #1218: Cannot install coops with CHICKEN 4.10
From: |
Chicken Trac |
Subject: |
Re: [Chicken-janitors] #1218: Cannot install coops with CHICKEN 4.10 |
Date: |
Tue, 15 Sep 2015 19:09:32 -0000 |
#1218: Cannot install coops with CHICKEN 4.10
-------------------------+--------------------
Reporter: iraikov | Owner:
Type: defect | Status: new
Priority: major | Milestone: 4.11.0
Component: extensions | Version: 4.10.x
Resolution: | Keywords: coops
-------------------------+--------------------
Comment (by sjamaan):
I tried to reproduce what you said you did to the files, but I keep
getting the same error message.
However, it worked if I simply moved the import files to the end (even
with the orignal versions of {{{coops.scm}}} and {{{coops-module.scm}}}),
so they're compiled after all the other files. That's because the
{{{(import foo)}}} statements will then fall back to simply loading the
source files instead. This may be a good "solution" for coops and similar
eggs (perhaps 90% of our eggs, in fact), but it won't work in the general
case:
If you have an egg consisting of two modules, let's say module A and B,
where A depends on B at compile-time (perhaps B offers some important
macros), it must be able to load it. If module B contains FFI calls, it
'''must''' be compiled.
Of course this is a pretty contrived example: most eggs are not this
complicated. So I guess this "bug" should be considered to be in coops
after all.
--
Ticket URL: <http://bugs.call-cc.org/ticket/1218#comment:6>
CHICKEN Scheme <http://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Chicken-janitors] #1218: Cannot install coops with CHICKEN 4.10,
Chicken Trac <=