| Re: Version Control Strategies For Block-Based Forths? |
|
 |
|
 |
|
 |
|
 |
Group: comp.lang.forth · Group Profile
Author: John PassanitiJohn Passaniti Date: Sep 19, 2008 09:55
Jean-François Michaud wrote:
> A simpler approach is to simply store the entire block while tying a
> version number to it. Pulling the version is as simple as looking up
> the associated pairs (version and block). This is simple to implement
> but will rapidly become bulky space-wise; check-in/check-out is
> necessary here as well. The same "multi" function applies under the
> bulky solution. Rollback is the same as previously mentioned except
> that here we delete whole blocks instead of deltas.
Again, I'm not looking for a discussion on how to implement this. I am
interested in existing strategies that others may have used because I'm
looking for proven approaches, not an abstract discussion about how I
might choose to implement this.
The answer may simply be that nobody had ever implemented version
control in block-based systems. That's fine, and if so it tells me that
I'm not going to be considering proven approaches but something I invent
for the particular project I'm considering.
| 
