Howard, What Erik says is true. Making a UDF of a long named command only gives you a benefit when you use the command more than 3 or so times.

eg:

code:
$=writeprofilestring("c:\filename", "section", "key", "value")
$=writeprofilestring("c:\filename", "section", "key", "value")
$=writeprofilestring("c:\filename", "section", "key", "value")
$=writeprofilestring("c:\filename", "section", "key", "value")
scores 236

versus

code:
function a($section, $key, $value)
   $=writeprofilestring("c:\filename", $section, $key, $value)
endfunction
a("section", "key", "value")
a("section", "key", "value")
a("section", "key", "value")
a("section", "key", "value")
scores 202

each line in the first program scores 59, so after 3 of them, the UDF becomes more economical.

Erik, it would be harder, but not impossible, to make a script to count. I wrote a script that converts KiX code to coloured HTML by doing a lookup of the valid KiX commands. It is too old to use now, but the principle is sound.

KiX uses space and CRLF as command separators, so using SPLIT with these 2 as delimiters makes parsing a KiX script relatively easy...

cj