> > For side effects, you may introduce an optional argument EVAL instead of > > mandatory API change. That will make it 100% safe even if some > > third-party code is using this internal function. > > ...
Good point. I drafted a version that did that but didn't go with it because I didn't think about third-party callers. > It has been a while since the last update in this thread. > Tom, have you had a chance to look into my comments? Yes, sorry, a major (positive) life event has delayed my ability to get back to this. Will try to revisit this week.
