Arne, you may want to take a look at Chez's "module" syntax, see [1]. It is orthogonal to our discussion about library names, but it may be what you have in mind for your specific use case. A module is like a library but is bound to an identifier, not to a library name.
Marc -- [1] https://cisco.github.io/ChezScheme/csug10.0/syntax.html#./syntax:h5 Am Mo., 22. Juli 2024 um 23:05 Uhr schrieb Dr. Arne Babenhauserheide < arne_...@web.de>: > Maxime Devos <maximede...@telenet.be> writes: > > * hence, you can define a module from within another module (might be > > situationally useful, but comes with new difficulties for module > > lookup) > > I actually tried something in that direction in enter three witches — > and failed. > > I wanted to add a macro that maps > > SCENE I > > to defining a module that cleanly separates different parts of a story. > > But I didn’t get that to work well (because it would have had to add > automatic exports and canonical imports and all together caused more > problems than it solved. > > Or maybe I didn’t understand well enough what I was doing. Generating > code that generates modules isn’t a good idea if there’s a similar > option that uses standard mechanisms. > > Best wishes, > Arne > -- > Unpolitisch sein > heißt politisch sein, > ohne es zu merken. > draketo.de >
