[CZT-Devel] section manager dependencies

[Leo F. <leo...@ne...>]

Hi guys,

we've been working in a way to start using the section manager dependencies in order to avoid duplicated work (e.g., as is, we have section manager per buffer in Eclipse and jEdit).
obviously, the trouble is that invalidation of "dirty" sections is crucial in order to trust that the manager is in a correct state. This is necessary mostly for large specs, given that rework 
gets in your way (e.g., Mondex has about 20 sections; you would get 20 section managers like a onion-layer of duplicated information - quite a waste!).

we started adding the various dependency relationships between various parts of CZT. This is experimental and we will come to it soon. At the moment, since no tool is using such 
dependency information, it will make no difference. Andi n the end, if there is any issue on trusting the dependency results, one can just return to the (inefficient) section manager
 per buffer approach.

We will summarise soon what think the dependencies for each element involve are. There is also the issue of which directions of dependency should we worry about (upwards to 
parents or downwards to children or both; as well as mutual dependencies like ZSect and its OpTable).

In the past, I come across a Z spec of a similar database of information management, and ideally an implementation should have such a origin. 
Are you aware of this spec? I couldn't find it.... Also, if you have any thoughts or comments, please let us know ...

Best,
Leo & Andrius