On 9 January 2014 00:49, Colin Putney <colin at wiresong.com> wrote:
>
> Hi all,
>
> Here's a weird consequence of environments: since many of our preferences
> are now created via pragmas, and environments allows the "same" class to be
> loaded into more than one environment at the same time, we have the
> potential for a preference to have different settings in different
> environments.
>
> AFAICT that should be fine, except at the GUI level, where we need to make
> it clear what's going on when a preference exists in more than one
> environment. That ought to be a project for 4.6, as it's too big to
> shoe-horn into 4.5.

Agreed. You have two Environments at play: that of your IDE, and that
of the code. "In the context of the Environment in which this code
runs, the preference Foo has value #localValue."

> In the meantime, what do you think? Are the problems that
> environment-specific preferences would cause? Is there something cool we
> could do with it?

My first thought is that it lets people using the wrong (*) token for
assignment - $_ - to change Scanner's preference within their
Environment, while the base/"top" Environment uses the correct token -
:=. Ditto for things that require allowing $_ in selectors, like
Xtreams.

frank

> Colin

(*) :)