On 04.03.2016, at 15:59, karl ramberg <karlramberg at gmail.com> wrote:

> 
> 
> On Fri, Mar 4, 2016 at 3:25 PM, Bert Freudenberg <bert at freudenbergs.de> wrote:
> On 03.03.2016, at 23:28, Chris Cunningham <cunningham.cb at gmail.com> wrote:
>> 
>> On Thu, Mar 3, 2016 at 12:31 PM, karl ramberg <karlramberg at gmail.com> wrote:
>> Nice.
>> BTW: there is a lot of empty categories in the Preferences class.
>> We must remove those in a post script or something.
>> Preferences organization removeEmptyCategories
>> 
>> I'm not sure how to do it ?
>> 
>> Add it in a package preamble ?
>> Does we then need to remove the preamble again ?
>> 
>> If I remember right, the preamble (and postlude?) only get run once - when they are first changed.  After that, they are skipped.
>> This means you want to leave them in and not remove them - otherwise a person later on would update from Trunk and just get the latest version - which doesn't have the preamble - and the work wouldn't be done.
>> 
>> Or am I wrong, and this only happens with Class initialization?
> 
> It happens exactly the same as with class initialization:
> 
> If the definition (of the script or method) changed, it gets executed.
> 
> You cannot rely on it having executed, or it only executing once. It’s better to write it in a way that running it again does no harm.
> 
> We can force execution by issuing an update map, but it’s better to avoid that.
> 
> For the problem at hand (empty method categories) we also could just add a step to the release builder to ensure all categories are clean.
> 
> We could run this for all classes I guess. I don't see much value in keeping empty method categories around...
> 
> Anyone objects ?


"look at class side" …

Best
	-Tobias

> 
> Best,
> Karl
>   
> 
> - Bert -