Chris Muller wrote:
>>>I think I used the word "render" meaning that these class references has
>>>always been to the class Delay in category Kernel-Processes - it is
>>>after all "stored" as an object reference in the CM. But suddenly, when
>>>it turns ambiguous, this reference is "rendered" as "Kernel::Delay" in
>>>the source.
>>
>>Hmm... So you're proposing that my code might change when I file in 
>>another package?  So if I have Foo filed in, and then I load Bar, I 
>>might have to commit a new version of Foo because its code got changed 
>>while loading Bar?
> 
> 
> No, Foo did not change, so no need to commit a new version.  It always knew
> it's fully-qualified names, just they weren't displayed by the browser until it
> was necessary (when Bar was filed in).

Well I don't like that either.  Obviously the compiled method would know 
specifically what class I was referring to, since I would have to 
unambiguate (if necessary) when compiling, but is this proposal now 
suggesting that the code I type is not the code that gets saved to the 
.sources file?  This is a rather major deviation from the way things 
work now and hardly a simple humble proposal.

Julian