What a great idea!
Actually, the functions listed won’t work on Sequoia without recompile. They will still work in in previous versions of macOS. But I would suggest taking care of it now if you use any of these functions. Once recompiled, they will work on any version of macOS. And the recompile step is very fast.
I think they would still run. But if you ever edited them in b39, you would need to recompile them again using b41 (or later) or they won’t work on Sequoia (or later, unless Apple fixes the problem, which I suspect they never will). See my comments below about bouncing between versions.
Nope. The textbefore( function does not need recompilation.
I hope so too. If it doesn’t, let me know, there is a further step available in b41. But I don’t want to use it unless necessary.
You may already know this, but bouncing between Panorama versions has been the source of various problems over the years. Sometimes the problems turn out to be worse than whatever the person was trying to avoid by using multiple versions. Whenever possible, I recommend always increasing the version number, and never decreasing.
Have you ever looked at Panorama’s blueprint feature? It’s designed to do exactly what you are trying to do. I use it to track database changes in git, but you can also use it for BBEdit searches.
I always check this after building a new release. It’s right there on the Release Notes page.
Ok, somehow this, and the new Recompiling Code and SaveAndClose statements did not get into the search. That’s a new type of failure, not sure how that happened. Here are the links for the 4 new pages. I’m not going to make a new build just for this, but I’ll make sure this is resolved in the next version.