[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-users] How to make bindings available to eval?
From: |
Jörg F. Wittenberger |
Subject: |
[Chicken-users] How to make bindings available to eval? |
Date: |
Fri, 03 Jul 2015 16:07:42 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux armv7l; rv:31.0) Gecko/20100101 Icedove/31.7.0 |
Hi all,
I'm caught in the compiled vs. evaluated semantics...
In csi everything runs perfect, but in compiled mode I'm confuse why
eval does not see most bindings. What am I missing?
The crazy thing: in the attached file "bar" is bound only when compile
as `csc tt.scm` (the "else" branch in the cond-expand) but unbound if
compiled as `csc -Dv1 tt.scm`. The binding to bar however is correct in
either case within "baz":
(cond-expand
(v1
(import foo))
(else
(import (prefix foo foo:))
(define bar foo:bar)))
(define (baz x) (bar x))
Scratching my head… This effects basically all the eggs. The only work
around I found so far is to do the import/prefix trick in the file/unit
exporting the binding. But that's tedious and probably not what I want
to do.
Thanks
/Jörg
tt.scm
Description: Text Data
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Chicken-users] How to make bindings available to eval?,
Jörg F. Wittenberger <=