bstr?
don't remember... kinda pointer?

anyway, if I have reverse-engineered kix's way in my mind correctly, I know where it does fail.

I thought there could be 2 possibilities:
- kixtart reads the string and allocates mem by it
- kixtart does not care what it has inside unless needed thus it could have whatever inside, even binary data

these are kinda pseudo thoughts as that is not fully as it really goes.
now, what I've heard from you, it seems that kix uses the first approach which in all means seems worse.
1) it removes ability to have whatever data stored in kix-vars
2) the unneeded scan of the data slows things up which will show up in many milliseconds after some days of hard script execution
3) you name it

now, if kix's lack of support for the other types of data depends of using old routines which depend on some old c-library it should be easy to fix that.
also the logic of pre-tokenized might have a hit but don't think it could in any way reduce the speed nor make it too much more complex to have...

well, once again my thoughts...
as you see, I have hard time of taking your word for it but as am too lazy to play with it, I just keep using my mouth [Big Grin]

k, me of now...
_________________________
!

download KiXnet