On Jan 7, 9:26 am, "Edward K. Ream" <[email protected]> wrote: > On Jan 7, 8:41 am, "Edward K. Ream" <[email protected]> wrote: > > > This example really stresses the update algorithm. It's a fascinating > > test case.
Here is the checkin log for rev 2639: A potentially major improvement to the @shadow update algorithm. The main loop now handles 'replace' opcodes very differently from 'insert' opcode. This appears to handle Gil Shwartz's example in a much better way than previously. **Warning**: This must be considered a speculative change. True, all unit tests pass, including a new @shadow test, but there is *no* guarantee that the new code is reasonable. Use care is you use @shadow files. Please report any problems immediately. Edward
-- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
