as of commit d15309....
there are 66 deprecation warnings part of cutting over gradually from the direct use of CompiledExpression to the more powerful Evaluatable technique.
Some of these are relatively easy to fix, others are tied up in the delimiter-scope stuff, and text numbers stuff.
Fixing these enables refactoring the code so that we eliminate the dual-paths where one path is about "static" stuff, and the other "dynamic" stuff. Done right, one need only do "dynamic stuff" using Evaluatable.
So these aren't quick or tiny fixes (or I would have done them). They do require some significant reflactoring.
Some mechanisms we have: CachedDynamic, ..... the refactoring to be done is such that Evaluatable should replace CachedDynamic, because it is effectively a generalization of it that adds additional capabilities.