Henrik,

> > 1. The binding is made read-only...why?
> 
> Ehm this is not a bug its a "feature". When I was halfway 
> through the module code the read only bindings were thrown
> into the stream without any warning, and the policy I could
> come up with was to use them by default (as in the nonö-modular
> system). I soon realized too that this was not very handy so I
> invite anyone to invent a better policy. Having them not be 
> used by default is one attractive option.

Don't use them by default. The point of read-only bindings is to protect
certain, critical classes making up the core of the class library from
being overwritten. In other words: All the existing classes in a release
should have read-only bindings but everything the user is defining
should not.

Cheers,
  - Andreas