On Aug 12, 8:40 am, "Edward K. Ream" <[email protected]> wrote:
> P.S. The drawback to [creating new rst-related commands] > will be that it doesn't clean up > the existing code. But in the absence of proper unit tests it's too > risky to change *anything*. Better just to leave the code as it is, > and build a simpler structure on top of the old. It's unbearable to leave leoRst.py the way it is now that I know how to clean it up. Furthermore, the very first unit test I wrote exposed a bug. Therefore, I plan a suite of tests that test the major options. This is pleasant now that the exec (g.findTestScript(...)) pattern exists. Once these unit tests are in place I shall start refactoring the code and making other important changes. I would like the code's complexity to collapse in tandem with the complexity of the docs. 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.
