On Tue, 21 Oct 2014 17:29:08 -0700 (PDT) "Edward K. Ream" <[email protected]> wrote:
> My first thought was to delay the allocation of new gnx's until after > the postpass. Like this: > > 1. ni.getNewIndex would allocate None as the gnx if it is called > before the post-pass. In that case, getNewIndex would add the vnode > with the dummy gnx to a global list. > > 2. After the post-pass, all nodes on this list would get a proper, > safe, gnx based on the updated ni.lastIndex. > > But this is all delusion! Consider these itsy-bitsy teeny-weeny > questions: > > 1. How many .leo files did the previous clashing invocation of Leo > open? > > 2. When is *this* invocation going to open all the files opened in > the *other* invocation of Leo? > > Oops! Leo can only run the post-pass after we open *all* the .leo > files opened by the "clashing" invocation of Leo. But Leo has no > idea what those .leo files were! As a result, Leo can *never* be > sure a .leo file that is opened *after* the post-pass won't contain > gnx's that clash with newly-allocated gnx's in *this* invocation of > Leo. I don't understand the above - I don't see how there's more than one invocation involved. I certainly thought of the possibility of Leo needing to allocate gnxs before all the @auto nodes were loaded, if I didn't mention it, and figured that something like the solution you mention would work - so I'm not seeing why it doesn't? Cheers -Terry -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
