Still stuck on this point that keeps being repeated. To wit, since I wrote the 450 lines of relatively complex code, I don’t see how I could be in … more control over what’s happening. AFAIK, FMP doesn’t make the source code of the Evaluate() function available for modification.
Also, each time I make a code change, I have a JUnit test do regression testing on the hundred or so examples to make sure I didn’t break anything.
Plus the users get very helpful detailed messages. (See below). In my earlier screenshot above, I forgot to include transcendental functions’ results (FMP handles these too, of course).
In any case, for me, it’s a moot point since most of my clients have never heard of FileMaker. My code works with any HTTP-enabled application, not just FileMaker. My clients just want an endpoint (FileMaker not required).
The updated first example (called from FMP) below shows that the logic still works even with mismatched parentheses. The last example gives the user a plain English thing to check with that they entered. FileMaker just gives “3” in this case as the result. That’s just a different design decision.