> > Here's another part of the problem that can, and *will* cause problems.
> Positions in the original list might no longer exist after a previous > delete operation. That's why the code I suggest contains: > > You are thinking in the terms of positions, but they are irrelevant for my code. After initial transformation of input positions into the list of immutable pairs, positions have no influence on the execution of main loop. Links that are requested to be cut, will be cut and no link will be cut twice, which means when it is time to cut it it is not cut yet. The code is so obvious once you shift your mind away from the mutable positions to immutable pairs of integers and vnode instances. Nor the integer index can change, neither the vnode instance can become invalid. Vitalije -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/8760ce1f-3eeb-4a34-9167-504f11dd7cd7%40googlegroups.com.
