Hey Alex, thanks for giving the links to the previously asked questions. In fact, the example given in
http://lists.scheme-reports.org/pipermail/scheme-reports/2013-October/003806.html > nails down my point. So, does this mean that there is no portable way to share, for example, parameter objects between code living in different libraries apart from handling the objects by hand? (By handling by hand, I mean to import all stateful objects in the main program and then calling procedures in imported libraries to set! exact copies of these stateful objects.) Forgive me if I am too bold, but: If not specifying this behaviour (the behaviour of runtime bindings of identifiers of libraries imported more than once) in R7RS (although it is implemented the same in all known implementations) means that it is neccessary to make such contortions to write portable code, then that's a flaw in the R7RS (small) specification. Marc
_______________________________________________ Scheme-reports mailing list [email protected] http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports
