..." was a classic printing pattern for blocks in polyForth where 3 blocks...1st 64 character line of each block and the convention to put a...Since most systems filled their available block ranges, having two sets of ...> Given the requirement for a block based system, and the OP's... attempt to force an ancient block based system accomplish a very prevalent task which can easily (trivially) ...

...is easy to have a new version in front of the old versions... screen doc's suggest this strategy, but I have never seen ... 64 character line of each block and the convention to put a... most systems filled their available block ranges, having two sets of ... the printouts. Since most revision control systems assume that there are ... be put together and most block based systems assume that there ...

... am interested in is what *existing* strategies may have been used in the ...for doing version control using Forths that stored source using *true* blocks. Note carefully that I make two...I'm only interested in *existing* strategies because I'm looking for something.... There is (not yet) a block editor working over Kermit with a... the same and differing in version based on the remainder of the...

...posting it... I've only seen people using external strategies. The colorForth folks all seem to keep a stack ... keep a series of image files (or to increment the "zero" block in the native version). You mostly just backed up to the most recent one when ... and copying some bits and pieces over. Gah. It's so tempting to speculate; version control is such a fascinating topic...you might have ...

...> We never developed a block-based version control system per se, ...> compare a current vs. previous version (its primary purpose was to ... it two starting ranges of blocks, and it would show which .... You could then display differing blocks side-by-side (or above/below, or toggling back and forth with 1 key, depending on ... that might lend itself to block-style development directly on the ...

...JapanIsShinto.com> wrote: I'm just looking for past strategies. A block that contains the current and previous checksums for all blocks, a word to show changed blocks, and an archive of release versions by date. Kind of vague, but thanks. Did your archive store only changed blocks for each release that was checked in? Or did you copy...

...am interested in is what *existing* strategies may have been used in the...for doing version control using Forths that stored source using *true* blocks. Note carefully that I make two...I'm only interested in *existing* strategies because I'm looking for something...strategies because we don't use blocks any more, but I can ... years that we did use block-based systems on rather large ...

... that here we delete whole blocks instead of deltas. Again, I...I am interested in existing strategies that others may have used...had ever implemented version control in block-based systems.  That's...I'm outlining the overall strategy. Two in fact. So to...both strategies: Check-in/check-out is necessary otherwise version control...describes in context and the *strategy* for rolling back is very...

On Sep 19, 8:51 am, John Passaniti <n...@JapanIsShinto.com> wrote: I'm just looking for past strategies. A block that contains the current and previous checksums for all blocks, a word to show changed blocks, and an archive of release versions by date.

...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 ...> that here we delete whole blocks instead of deltas. Again, I'm.... I am interested in existing strategies that others may have used ... had ever implemented version control in block-based systems. That's fine...