Feature Description
right now, cksp automatically tries to fix all possible memory exhausted errors by wrapping code in if 1=1. The Kontakt errors happen when a specific number of tokens in a code block is exceeded and are probably caused by a Bison Parser setting used in the Kontakt Interpreter.
Possible difficulty: when turning it off the compiler should stop optimizing away already present if 1=1 blocks written by the user but still somehow optimize other if-conditions...
Problem it Solves
The implementation of the automatic cksp pass does not work in all cases and still sometimes causes memory exhausted errors in Kontakt. This happens especially often when all optimizations are turned off (see the-score.ksp script with optimization set to 'none')
Feature Description
right now, cksp automatically tries to fix all possible
memory exhaustederrors by wrapping code inif 1=1. The Kontakt errors happen when a specific number of tokens in a code block is exceeded and are probably caused by a Bison Parser setting used in the Kontakt Interpreter.Possible difficulty: when turning it off the compiler should stop optimizing away already present if
1=1blocks written by the user but still somehow optimize other if-conditions...Problem it Solves
The implementation of the automatic cksp pass does not work in all cases and still sometimes causes
memory exhaustederrors in Kontakt. This happens especially often when all optimizations are turned off (see the-score.ksp script with optimization set to 'none')