🚀 go-pugleaf

In <4jcnbb$np0@piglet.cc.utexas.edu> mcintosh@ccwf.cc.utexas.edu (Aubrey McIntosh) writes:

>I work with unix people a lot.  They have an elaborate protocol in 
>place to have different source versions of programs.  They have 
>tools, such as the gnu rcs suite of programs, to manage these 
>versions.
...
>Page 110, "Project Oberon", discusses the generalized piece chain, 
>to support looks.  This existing representation of a document within 
>Oberon already supports multi-file documents and updates.  The 
>existing Text module collapses all of these different pieces into 
>one file when a text is stored.  In addition, when a text is first 
>opened, all of the pieces point to one file.

>In order to support version control, the only major changes that I 
>envision are the ability to store the file information in the piece 
>dictionary, and to reconstruct this upon open.  The new version of a 
>text would consist of the piece dictionary header, and the relevant 
>portions of the internal file that has newly typed text.  
....
>http://ccwf.cc.utexas.edu/~mcintosh
>... seeking old comp.lang.oberon articles

Aubrey,
  Thank you for this timely comment.  I am also facing this issue
where I will soon need to maintain consistency of module releases
with a distant client.
  Forgetting a little about the details of the implementation,
how do you see this being used?  What do you see the process to be?

-Doug

-- 
-----------------------------------------------------------------------------
  Douglas G. Danforth, Ph.D.                       danforth@csli.stanford.edu
  Visiting Scholar                                 (415)723-2487 x332 vox  
  Applied Speech Technology Lab                    (415)725-2166 fax
  Center for the Study of Language and Information
  Ventura Hall                    
  Stanford University, Stanford CA.  94305-4115             
-----------------------------------------------------------------------------