Henrik Gedenryd <h.gedenryd at open.ac.uk> wrote:
> danielv at netvision.net.il wrote:
> > * As I discovered, it's not trivial to package modularizing code in a
> > manner that's understandable/appliable by clean images. If there are no
> > guideline, we'll get every variation possible.
> 
> Well that is exactly why these should be done as subclasses of
> ModuleRefactorer. Look at the existing ones. This is then put in a change
> set along with any methods that are changed/moved/removed etc.

I'm studying the subject... And when are the module refactorings run?
how do you make sure they run after the code refactorings it depends on?
Run it in the post script?

[Refactorings breaking]
 
> SqC and Dan have been pretty good about this so I don't think it will be a
> problem if the code is well done and of good quality. When it is approved
> then I think it will be adopted in the next set of updates or so. That has
> been the case in the past.
> 
> H

Actually, as I recall, the Modules work took quite a bit of time to
enter the image. Understandably, of course, it's a pretty darn big
change. I hope it won't be a problem.

Daniel