starting triple braces without ending triple braces throws an error - previously this was swallowing an additional character
math is hard - check the bounds of a string properly when looking to see if a closing } exists
clean up Tokenizer->scan -- add error annotation, spaces between +, strict type checking, and self instead of Mustache_Tokenizer
add test coverage to ensure that custom delimiters don't swallow trailing characters after they close
uneven braces with custom delimiters throws Mustache_Exception_SyntaxException
Merge pull request #209 from smarden1/pr/even_triple_braces

Uneven braces in triples are incorrectly swallowing a character [repost of 208]