Hello friends of KIX !

I'm maintaining a nested set of loginscripts and experience premature (but error-free) script terminations during testdrive with KIX 4.50 RC1. From 4.20 to 4.23 everything worked fine. The scenario:

Startup of loginscript package via batchfile:

KIX32_450rc1.EXE pre\Starter.kix dep\Department.kix post\Finish.kix

All three scriptkompoments contain various CALLs to other script, like:

call 'sub\Constants.kix'
call 'sub\Mappings.kix'
call 'sub\Printer.kix'
... etc. You get the idea.

In order to prepare for the use of pretokenized scripts (great feature !) I modified the CALLs to:

global $suffix
$suffix = '.kix' ; see following text !

call 'sub\Constants' + $suffix
call 'sub\Mappings' + $suffix
call 'sub\Printer' + $suffix

In real life the value of $suffix is dynamically set to '.kix' or '.kx' depending on the KIX version as given by @kix. So I can run the scripts using any KIX version and can dynamically switch between plain text and pretokenized scripts.

Well, KIX 4.50 RC1 with pretokenized scripts terminates silently at the 2nd executed CALL. No error message, no return code set. Single-stepping through the CALLs indicates that the 1st CALL doesn't execute the called scriptcode, stepping over or into the 2nd CALL terminates the whole script run, as seen when run without single-stepping.

Switch back to KIX 4.2x (and to .kix suffix, of course) and everything works as expected.

What goes wrong?

Thanks a lot for any help and/or suggestions.

OlfFart