LUMIERA.clone/wiki
Ichthyostega 0782dd4922 investigate and confirm the logic underlying the matchSrc, skipSrc and acceptSrc primitives
In Theory, acceptSrc and skipSrc are to operate symmetrically,
with the sole difference that skipSrc does not move anything
into the new content.

BUT, since skipSrc is also used to implement the `skip` verb,
which serves to discard garbage left back by a preceeding `find`,
we cannot touch the data found in the src position without risk
of SEGFAULT. For this reason, there is a dedicated matchSrc operation,
which shall be used to generate the verification step to properly
implement the `del` verb.

I've spent quite some time to verify the logic of predicate evaluation.
It seems to be OK: whenever the SELECTOR applies, then we'll perform
the local match, and then also we'll perform the skipSrc. Otherwise,
we'll delegate both operations likewise to the next lower layer,
without touching anything here.
2016-08-09 23:42:42 +02:00
..
draw TiddlyWiki: fix some orphaned pages 2014-02-16 22:02:55 +01:00
DIR_INFO update some DIR_INFO entries 2011-04-05 00:44:30 +02:00
empty.html upgrade TiddlyWiki to v2.8.1 2013-08-10 05:36:57 +02:00
InterfaceConcept_Varga.mm Lumiera GUI thoughts -- Mindmap to complement the Interface concept PDF 2015-04-26 23:22:42 +02:00
renderengine.html solution draft for integration of the whole tree diff application machinery 2016-07-31 00:33:25 +02:00
thinkPad.ichthyo.mm investigate and confirm the logic underlying the matchSrc, skipSrc and acceptSrc primitives 2016-08-09 23:42:42 +02:00
uml better use doc/devel/uml... 2007-06-21 02:57:49 +02:00
workflow.mm DOC: expand concept map 2014-10-25 01:56:44 +02:00