[Chicken-users] Redefinition of imported binding gets implicitly exported

2013-10-25 Thread Andy Bennett
Hi, With the following in m.scm: - (module m (do-something) (import chicken scheme) (use posix) (define process (make-parameter 'hello)) (define (do-something) (printf Doing something...\n)) ) - ...and compiled thusly: csc -s -O2 -d1 m.scm -j m -o m.so csc -s m.import.scm

Re: [Chicken-users] Redefinition of imported binding gets implicitly exported

2013-10-25 Thread Andy Bennett
Hi, I get the wrong binding for process when I (use m): - #;1 (use m) ; loading ./m.import.so ... ; loading ./m.so ... #;2 (process) hello - Of course... I was expecting the posix unit's binding for process: - #;1 (use posix) ; loading library posix ... #;2 process

[Chicken-users] iset egg, wrong intersection result

2013-10-25 Thread r
Hi, i have found that on some numbers iset-intersection produce wrong results. example in attachment, all numbers in fixnum range iset b a:(44189 50194 78574 80802 80902 88559 89629 89832 89862 90701 91234 92306 93599 95409 95687 96350 97827 97844 97845 97846 97847 97848 850 97851 97852 97853

Re: [Chicken-users] Redefinition of imported binding gets implicitly exported

2013-10-25 Thread Evan Hanson
Hi Andy, all. I looked into this recently since it also seemed like a bug to me, but the behavior seems to be intentional judging from the code. A workaround is to exclude `process` from the import list in `m` (as in `(import (except posix ...))`) -- this prevents the behavior you're seeing, at

Re: [Chicken-users] [Chicken-hackers] Redefinition of imported binding gets implicitly exported

2013-10-25 Thread Peter Bex
On Sat, Oct 26, 2013 at 06:51:10AM +1300, Evan Hanson wrote: It seems to me that when `##sys#alias-global-hook` is used to resolve names for `set!` forms, it should be called with the bare (pre-se-lookup) identifier, and when `assign` is true and you're currently in a module it should always