On Fri, Mar 26, 2021 at 10:42 AM [email protected] <[email protected]> wrote:
Instead of changing the rst3 code, we could consider just not telling > people about these options, or advising them not to use any. Would not > this give the same result without the time and risk of modifying the code? > Imo, this work is worth doing. Yes, there is always a risk in modifying code. However, there several gains, which I've already discussed: - Easier to learn. - Easier to maintain. This will be important after I am gone. - Easier to document. This is a big deal. I have already ripped out a lot of code. I am not looking back. Some unit tests are failing, but eventually they will be stronger than ever. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS3t1NaexL6817qn9HSyFwMvU6T%2Bv-L8EU%2B_3zOkqwd6NQ%40mail.gmail.com.
