On Tuesday, August 25, 2015 at 9:53:01 AM UTC-5, Edward K. Ream wrote: > ...it's time to declare that configuration setting should never be cached. Instead code should always call c.config.getX. We shouldn't sacrifice flexibility to save a few millionths of a second here and there.
There is an alternative, namely to call x.updateSettings for all classes x that have an updateSettings method. This would "re-cache" settings. I'm not sure which is the simplest thing that could possibly work. On the one hand, declaring that caching shouldn't happen is a global constraint. Otoh, adding updateSettings methods for classes that cache settings is more work. Using updateSettings has the advantage that it is explicit, so maybe it's better despite the new infrastructure to call all x.updateSettings. It's a close call, imo. EKR -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
