hidden/gensymed variables are registered for export
This might cause problems if an interned symbol with the same name is defined. Find out if this really is a problem.
Also: alias global hook strikes again ;)
Example:
(module foo (x123)
(import scheme (chicken syntax))
(define-syntax define-x123
(ir-macro-transformer
(lambda (e i c)
(let ((name (gensym 'x)))
`(define ,name 'blah))))
(define x123 5)
(define-x123) ;; Should not overwrite the interned version of x123, which happens if both collide on foo#x123!
)
(import foo)
(print x123) ;; Should print 5, not blah
Of course this requires some fiddling to get the numbers right, which would differ per CHICKEN version (a proper test would require reading the gensym counter to force the collision, or something like that).
Change History (8)
Description: |
modified (diff)
|
Description: |
modified (diff)
|
Milestone: |
someday →
6.0.0
|
Milestone: |
6.0.0 →
someday
|
Note: If this is fixed we should be able to remove the
##sys#register-export
in##core#define-foreign-type