On Feb 25, 12:02 pm, "Edward K. Ream" <[email protected]> wrote:
> The issue has relevance for Leo 4.7.1. Yesterday I attempted, and > failed, to create a unit test that would verify directly that reading > an external file with file-like sentinels would set the corresponding > @file node dirty. I now have a robust test. The trick was to use g.openWithFileName to read the .leo file. Imo, this is worth the several hours of work required. Creating this test was not without risk: I changed two core files during the test, but that could not be helped. The changes are small enough to be checked thoroughly by hand. Besides, all unit tests still pass, so what could go wrong ;-) On to lint checking... 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.
