#102790 - 2003-07-11 09:19 PM
Re: Kix Script Methodology
|
Glenn Barnas
KiX Supporter
Registered: 2003-01-28
Posts: 4396
Loc: New Jersey
|
Inside an EXECUTE: (your example modified only to reference a UDF that exists on my system)
code:
;; KixGenerated: 2003/07/11 - 15:15:24
$iRC=EXECUTE('$a=KixVer($b)') ;; ;;====================================================================== ;; ;;FUNCTION KixVer(Minimum [, RETURN, BRC]) ;; ;;ACTION Exits if not running minimum Kix or Beta version ;; ;;AUTHOR Glenn Barnas / FRIT-EROC ;; ;;SYNTAX KixVer(ver [,SoftErr [,BRC]])
Snipped for brevity. As you can see, the function is located and included. Based on the algorithm used, I feel confident that the result will be the same for the KixForms example.
I don't examine the code... that would take a tremendous amount of resources to analyze, not to mention the maintenance related to new versions of Kix. Instead, I look for UDFs on your system in the current dir, ..\kixlib dir, and the dir defined by your KixIncludePath environment var. Then I look at the base files to determine which DEFINED functions are required. Those function files are then reviewed to resolve dependencies, and so on until no further dependencies are found.
That is why there is a disclaimer in the code that says, in effect - this code won't resolve dependencies to UDFs that don't exist in the locations defined for inclusion. That's also why I'm confident that it will work for the KixForm example.
Glenn
_________________________
Actually I am a Rocket Scientist!
|
Top
|
|
|
|
Moderator: Arend_, Allen, Jochen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Mart
|
0 registered
and 667 anonymous users online.
|
|
|