Re: Change commitment control after compilation

On 21 December 2013 02:02, dieter bender wrote:

I would think about adding some exit points with well
defined interfaces, so that new functionality could be
integrated without only having a look to the old
programms! The changing parts have to be separated
from the "static" parts, needing noc change.

This was the idea behind making a conversion program to reformat the
new swipe data to match the old time card data. If the input stays
the same, nothing else needs to be looked at! I like the idea of exit
points in general; I will have to think on how I could implement these
in a situation like this.

<Buck>
It wasn't a design choice, as much as that is how it slowly grew.
</Buck>

We hope that software grews, mostly this is the ways software shrinks.

Too true.

In your scenario the main problem is not using commitment
control, but seperating the old stuff from the stuff needed
to be changed. This is very diffrent from the starting point
of discussion, talking about programms using embedded
SQL, if such programms write data, commitment controll
is a must have, in your case maybe nice to have.

It IS different, but related in the way that adjusting one program to
use CC doesn't make the entire application more sane. But it is a
start!
--buck