> So: I've been using the environment eggs code for some things. > This does not work any longer. I'd rather like to keep the > code compatibility with rscheme and chicken's eval. > > So far I've been using only four functions: > > make-environment > environment-extend! > environment-copy > environment-ref > > These I found so far to be kind of the minimum to enable envt > manipulations from user code. > > Could we have such a thing? I'm ready to hack the code overnight, > but what's the API chicken does need right now and which changes > to this API are expected to come more sooner than later?
There will be a replacement, but it will need some modifications in the evaluator. Do you evaluate a lot of code, are the environments long- or short-lived and small or large? Do you reuse them or create many environments on the fly? cheers, felix _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users
