Let say that you build a FileMaker Custom Function (deploying to different files at different times) and later want to either:
- Fix a bug
- Extend its functionality
Either would create a different version of the Custom Function (CF) and you would want to make the version string as visible as possible to your eyes and tools.
What is the best way to implement Custom Functions versions?
[-] Renaming a Custom Function has the downside of making your code less portable. If you copy and paste a script (that uses a CF) into a file where the custom function has a different name it will break
[+] A better way might be to use an extra Custom Functions parameter to store the version and any other text that might be useful when deploy a custom function into your code.
For example a Custom Function signature like...
convertFromFileMakerPath.pre19 ( a_path ; a_format ; v1~PosixPath~WinPath~URLPath )
convertFromFileMakerPath.pre19 ( "file:/" & $filePath ; "PosixPath" ; "v1” )
Tested as working and useful when programming in English.