The reason Leo 1.5+ million lines of code work reliably is that Leo's design ensures that almost all code has strictly local effect. Leo's developers can add new features without fear of breaking other code. Furthermore, Leo's overall design has remained remarkably stable for over 20 years.
I learned the practical techniques from two giants. This was in the 1970, way before classes were invented: David L Parnas <http://en.wikipedia.org/wiki/David_Parnas> wrote On the Criteria to be use in Decomposing Systems into Modules <https://www.cs.umd.edu/class/spring2003/cmsc838p/Design/criteria.pdf>. Glenford Myers <http://en.wikipedia.org/wiki/Glenford_Myers> wrote Composite/Structured Design <http://www.amazon.com/Composite-Structured-Design-Glenford-Myers/dp/0442805845/ref=pd_sim_sbs_b_1?ie=UTF8&refRID=0TZ62C6J9JMXWXA0A61G> . Both are well worth reading today. In essence, they talk about the properties of "strong" classes. The next post shows how this works in practice. 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
