On 20th of January (2006) I took the latest trunk from SVN, and tried it against some Velocity templates I am just working on. I came across two bugs, which I am reporting here, along with patches:
1. When #stop is issued from within #parse, the processing of subsequent #parse directives does not stop. Since expressions are no longer being rendered after a #stop, the parameter to #parse can be an empty string, resulting in an unexpected exception that confuses the user. I am attaching an example that reproduces this (stop3.vm, stop3-include.vm), with a patch
2. I came across a string-out-of-bounds exception which happened because string length was not being checked. Patch is attached.