ParseException missing currentToken problem

I have posted a patch to the problem where retrieving data from a
ParseException is throwing a NullPointerException because it does not
have a currentToken object here:

https://sourceforge.net/tracker/?func=detail&aid=803939&group_id=4075&atid=104075

I apologize for the cross-post, but this issue was brought up
separately on the BeanShell Users' and BeanShell Developers' mailing
lists last month.

The data available in the ParseException is sparse because the javacc
ERROR_REPORTING flag is set to false.  Here is the description of this
flag from the javacc documentation
(https://javacc.dev.java.net/doc/javaccgrm.html):

ERROR_REPORTING: This is a boolean option whose default value is
true. Setting it to false causes errors due to parse errors to be
reported in somewhat less detail. The only reason to set this option
to false is to improve performance.



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl