Hi Julian Thanks for the reply.but since this is a common request, I've written a new class: GenericSpace. I don't know whether it should be added to JITLib (I prefer to keep it as small as possible) but it seems to be quite useful.This is great. However, I don't think it solves my problem. I need to store the environment values somewhere that if a _user_ of the environment (the ixiQuarks) suddenly runs ProxySpace it doesn't erase all the data from the currentEnvironment.
I see.Yes, within a class you should not use the currentEnvironment without pushing your own - not only that you run into th eproblem you describe, also other values that somene may have stored could be overridden by it.
why not just push an environment and pop it again? you can keep one (or more) environments in a class variable of your system.
I cannot tell the user to use GenericSpace rather than ProxySpace. So I guess I'll stop using environmental variables and make a specific class for the storage of environmental (ixiQuarks) data. Thanks thor PS. I love the names of the Maybe and Perhaps classes. No helpfiles : ( What do they do?
Maybe is a loose derivation from the Haskell Maybe type. It is a value that does not yet exist (similar to the other proxies) which you can calculate with, and change at a later time. If it contains no value, any calculation that you have constructed with it will just return nil, otherwise it returns the value. There is a helpfile now, too.
Perhaps adds a dependency scheme to this. It is not tested very well yet. I've just moved it out for sparcity, I may move it in again when it is ready.
We need more of Maybes and Perhapses and Possiblys and Rarely and AlmostDefinitively in programming languages.
also Utterly is still missing. -- .