altoviso/bdParse — Issue #5: Parser failure when EOF exists where semicolon is expected at end of statement
Author: csnover
Created: 2011-10-21 21:38:40+00:00
State: open

EOF should be considered a valid statement terminator, but currently it generates an error. For example, given the following code:

```javascript
foo()
```

the following error is generated: `[2, 5]unexpected token (tEof:'EOF'); expected ;`