Uploaded image for project: 'BlueJ'
  1. BlueJ
  2. BLUEJ-46

incorrect error message in codepad

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Low
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.0.2
    • Component/s: CodePad

      Description

      I type Integer.parseInt("37") in the CodePad and get 37, as expected.
      I type Integer.parseInt("37.6") in the CodePad and get a NumberFormatException,
      as expected.
      I type Integer.parseInt(37) in the CodePad; I would expect to get an error
      message saying "wrong type argument" or "no such method found", but in fact I
      get "semicolon expected".

      ----
      Comment !BLUEJ-1 From Davin McCall 2006-08-31 02:24:31
      ----

      Yes, this is not ideal (currently anything which doesn't compile as an
      expression is treated as a statement, and as statements must end with a
      semicolon, the error message demands one). For a simple case like the example
      given, we should be able to do better.

        Attachments

          Activity

            People

            • Assignee:
              davmac Davin McCall
              Reporter:
              mik Michael K├Âlling
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: