On Sep 20, 7:08 am, "Edward K. Ream" <[EMAIL PROTECTED]> wrote:
> However, my hypothesis appears valid: terminating the loops using
> comparisons on head strings, while not valid in general, shows that
> the iterators are probably working correctly, while p == after isn't.
> This is good progress.
I've been thinking that it's too bad I can't run Leo's unit tests
outside of Leo. But that's silly. Most of the test refer to Leo and
its data, so running them outside of Leo makes no sense.
It is possible, using the curses gui, to run commands from the menu.
I just did this with the check-outline command, and it fails on every
node. This is expected given the behavior of the '==' command. The
dump-outline command works, again indicating that iterators work.
So enough of background. Time to do __eq__ and __ne__.
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
-~----------~----~----~----~------~----~------~--~---
