[Glass] Jade 1.059: package extension naming ...

[James Foster via Glass]

Marten,

Thank you for this report. I think that it is related to the method used to compile code. I made a change to get back warnings as well as errors and it appears that this low-level method does not set the package properly. I will investigate and report back.

James

> On Dec 2, 2014, at 1:41 AM, itlists at schrievkrom.de via Glass <glass at lists.gemtalksystems.com> wrote:
> 
> I can anyone confirm this ? I'm working here further on with this
> version, but get not a very good feeling.
> 
> If I add a method to an extension method category, this method is stored
> in the base package but also in the extension package. This at least can
> be seen in the Monticello packages created via Jade.
> 
> I looked at the source code within Dolphin, but actually on a first
> quikck view I simply did not understand how the stuff is working.
> 
> 
> Marten
> 
>> Am 27.11.2014 um 07:36 schrieb itlists at schrievkrom.de via Glass:
>> Something has changed in the behaviour of recognizing, that an extension
>> has changed.
>> 
>> If I have a package named "Hallo" and "HalloExtension" and I add a
>> method category "*HalloExtension" to a class defined in "Hallo" and add
>> a method to that category, the system will not make any package "black"
>> (= changed).
>> 
>> If I add a category "*halloextension" the system works as in in earlier
>> releases: the extension is "blacked".
>> 
> 
> 
> -- 
> Marten Feldtmann
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass