Re: parameter config is a mess

Scott Miller wrote:

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

Correct. I suppose we could add a set-parameter-default! procedure.

The more difficult challenge is to figure out how to deal with all the 
"special" parameters, i.e. parameters that aren't straightforward 
dynamic Parameters. On that list we have:

minprecision
maxprecision
permitinterrupts
strictr5rs
emitannotations
emit-debugging-symbols
home
slib
stack-trace-on-error

We should turn as many of these as possible into straightforward dynamic 
parameters. Failing that, special dynamic parameters (i.e. entries 
directly handled by DynamicEnvironment). Failing that, AppContext scope. 
Failing that, global scope (i.e. static members of some class).


matthias.
PS: we should also use the opportunity to harmonize the naming scheme 
for config parameters.



-------------------------------------------------------
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