Really do not want integers! Going to go straight to Glenn's website now and look through some UDFs!
Operation is pretty simple:
Create a Dev folder, with a KixLib subfolder. Can be a network share.
Define a System environment var called KixLibPath and point to the Dev\KixLib folder.
Copy the KGen.bat file to a folder that's in your Path (C:\Windows is OK for testing).
Create a subfolder in Dev for your project, and create your basic script.txt file there. Don't include any public UDFs in your code.
Optionally, break your script into modules, with your app-specific UDFs placed in a script.udf file in the same folder. I often break large files into multiple .UDF files in the project folder.
When you run (from a command prompt) KGEN script (without the .txt extension) it will parse your code, include all local .KXF and .UDF files, and then recursively scan your script and the external UDFs to include any required files from the KixLib folder. It creates a .KIX file ready to run with all needed UDFs. It also runs your finished script through the Sanity UDF, which checks for variable definitions, mismatched operator pairs (if/endif) and paired character sets (quotes, parens, and such).
The package is free to download and use, and has way more options and capabilities than I've mentioned here. Refer to the User Guide for complete information.
Using one of the advanced options (build.ini), I can run KGEN to build a new rev and copy it to the app folder on my machine. After local testing and validation, I re-run KGEN with a "PROD" argument and it re-gens the script, tokenizes it, and copies it to the shared folder for deployment.
Glenn
_________________________
Actually I
am a Rocket Scientist!
