Hi Chris,

On Jul 2, 2015, at 2:25 PM, Chris Muller <asqueaker at gmail.com> wrote:

>>> Do MC overrides actually somehow "reload" the code that was overridden
>>> when you unload the overriding code?
>> 
>> Yes. It goes through the method history in the changes/sources file and loads the overridden definition.
>> 
>>> If so, that is kind of amazing.
>> 
>> Indeed. Although scary, too. Overrides are still evil, and should not be used unless really necessary.
> 
> I wonder if it would work even after condenseSources.  That's been
> done for this release.

Should do given that condenseSources now preserves history right?

> 
>>> My purpose of doing this is to avoid having dirty packages in the release.
>> 
>> The overridden package shouldn’t actually be dirty. Did you do “changes” on it?
> 
> ReleaseBuilder prepareNewRelease ends up doing that check and
> complains if it finds any.  That's how I came to know about it.
>