Re: parameter config is a mess

On Wed, Apr 09, 2003 at 07:00:44PM +0100, Matthias Radestock wrote:
> 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.

Ah, so the issue is that the parameter's defaults aren't changeable?

	Scott

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+lHwbr9IW4v3mHtQRAtfjAJ9QzOQBhHx3MrSBcbBBTScnMPAy2gCeMIm1
UmFxrP1CeQyrgBSuVjJGyPY=
=Yw4j
-----END PGP SIGNATURE-----