|
On Jan 10, 2008, at 8:05 AM, Toon Verwaest wrote:
> Again on the [RB], is there a way of ordering the changes so that they
> are ensured to be applicable? Or do I need to generate my changes
> myself in a certain order. I am talking here about generating classes
> which subclass from each other. The RB should be able to detect this
> order itself easily enough. However, the RB in the current VW seems to
> rely on the order of input received. It seems useless to order this
> myself since it is a general RB problem to tackle.
The RB change model just does what you tell it to, in the order you
tell it to. Different clients tell it to do different things, and
specify the order. These "clients" are typically refactorings. For
example, an rename method knows that it first makes a duplicate of the
method, then rewrites all call sites, and finally removes the
original. This allows the system to stay running while the refactoring
is taking place. The logic for the order is in the refactoring though.
--
Travis Griggs
Objologist
"Only one thing is impossible for God: to find any sense in any
copyright law on the planet." - Mark Twain
|