Error message about "empty package" should be "unnamed package"

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P5
    • 1.4.0
    • Affects Version/s: 1.4.0
    • Component/s: tools
    • None
    • beta
    • generic
    • solaris_7
    • Verified

      We sometimes generate diagnostics like

      NestedInnerClassNames.java:19: NestedInnerClassNames is already defined in empty package
      class NestedInnerClassNames {} // ERROR
      ^

      (This example is from a regression test).

      The name "empty package" is misleading. The package is not empty. There is no language concept
      of an "empty package". The proper language term is "unnamed package" (7.4.2).

      Please correct the diagnostics. The reference file for the regression test NestedInnerClassNames
      will have to be updated as well.

      neal.gafter@Eng 2001-03-15

            Assignee:
            Neal Gafter (Inactive)
            Reporter:
            Neal Gafter (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: