Houston, we have a problem with gnx's

2014-10-21 Thread Edward K. Ream
Terry congratulated me on fixing #76 erroneous clone markers in @auto trees. The celebrations are premature. It's easy to see at least one flaw in the present gnx allocation code: the post-pass calculates ni.lastIndex after reading all external files **including @auto nodes**. But suppose

Re: Houston, we have a problem with gnx's

2014-10-21 Thread 'Terry Brown' via leo-editor
On Tue, 21 Oct 2014 17:29:08 -0700 (PDT) Edward K. Ream edream...@gmail.com 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