On Fri Dec 5, 2025 at 8:59 AM CET, Diogo Behrens wrote: > > I have submitted another one-liner patch, this time to codeberg. It ensures > the > function names are mangled when emitting wrappers.
Thanks - it has been merged. > Now we have two versions of the library and I think they should have > *different* > names. But -emit-wrappers give the same name "foo" to the module defined in > foo.wrap.scm. > > With two different names I could do this: > > ;; some crunch-only code: > (import foo) > > ;; some chicken code: > (import (foo wrap)) > > The only change that would be necessary is to derive the module name from the > emit-wrapper argument instead of using that of the wrapped module. > > What do you think? Perhaps we should leave the choice to the user, by adding a second argument to -emit-wrappers. Deriving the name from the file is of course also possible, but I'm afraid of adding unnecessary naming restrictions. Let me think about this. cheers, felix
