|
Well, I don't contend that I'm smarter - better looking perhaps.
NULL and CHR(0) are not actually no-nos in KiXtart, it's just that there is limited support in native variable types and no functions that you can manipulate them with complete success.
You can use KiXtart variable references to store NULL and CHR(0) and pass them on to automation objects that know how to handle them, just be aware that it is futile to use them with KiXtart intrinsics except in a very limited sense.
NULL is probably the easier to handle as it is a simple entitiy that is more of a state than a value. In KiXtart a NULL acts like an undefined value so behaviour will in most cases be what you'd expect.
Chr(0) however is a problem, and your example code demonstrates it quite well. When you catenate the strings in '? "[" + $chr0 + "]"' it's not actually doing what you think it is. It does not see $chr0 as an object with a Chr(0) in it, it sees it as a zero length string. You can demonstrate this better by trying for example to create and use a string like "A"+Chr(0)+"B"+Chr(0)+"C"
| 
