Re: parameter config is a mess

Scott Miller wrote:
>>I'm not sure what you mean. Only the *defaults* of these parameters are 
>>configured globally on startup. Threads must still be able to set their 
>>own individual values that override the defaults.
> 
> 
> How is this not currently the case, notwithstanding the borked 
> properties of Parser/Lexer?

As I mentioned before, there are many different scenarios in which new 
DynamicEnvironments are created. Only very few of them do/can copy a 
parent environment. They can still all see the parameters, but only 
their default values.

typical example: after initializing the scheme system some Java thread calls
  Context.enter("some-app-name");
and then does evals in that context.

This creates a new DynamicEnvironment. Accessing a parameter will return 
that parameters default value, regardless of what has been specified on 
startup.


Matthias.



-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com