Uploaded image for project: 'Commons CSV'
  1. Commons CSV
  2. CSV-80

CSVLexer.nextToken does not need wsBuf

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      CSVLexer.nextToken carefully saves leading whitespace in wsBuf if leadingSpacesIgnored is true.

      Later on, if leadingSpacesIgnored is false, it adds the contents of wsBuf to the token content field.

      It's not entirely clear what this was intended to do, but at present it achieves nothing; tests pass without it.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              sebb Sebb
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: