[CSV-81] Token.Type.isReady could perhaps be removed

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Assignee: Unassigned
• Reporter: Sebb
• Created: 22/Mar/12 18:41
• Updated: 22/Mar/12 19:04
• Resolved: 22/Mar/12 19:04

Description

The isReady field is written in lots of places, but only read in 2 places:

1) CSVParser.getRecord() uses it to determine if there was any data found at EOF
2) CSVLexer.nextToken uses it to determine when to exit the loop, but could equally probably check for type == INVALID

It ought to be possible to simplify this considerably since the only usage external to the Lexer is to distinguish the EOF case.