Improved parsing of braces in Geas (patch included)

[GoogleCodeExporter]

The parsing of statements between braces fails if there is no space between the 
opening brace and the content or no space between the closing brace and the 
content. In the former case, if a conditional statement follows immediately, 
the substitution on its expression is not performed in preprocessing step 1. In 
the latter case, the last character of the content is cut off when run_script() 
calls itself recursively.

The original run_script() implementation would treat consecutive opening braces 
as a single brace, which makes no sense. I changed it to process one opening 
brace at a time.

Original issue reported on code.google.com by mthuu...@gmail.com on 27 Jan 2012 at 7:36

Attachments:

• geas-braces.diff

[GoogleCodeExporter]

Thanks for this patch as well!

Original comment by bcressey@gmail.com on 7 Feb 2012 at 7:47

• Changed state: Accepted

[GoogleCodeExporter]

Resolved in r590.

Original comment by bcressey@gmail.com on 7 Feb 2012 at 7:50

• Changed state: Fixed