Signatures for nested classes contain redundant information

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: P2
    • 5.0
    • Affects Version/s: 5.0
    • Component/s: tools
    • b40
    • generic
    • generic

      The signatures generated by the compiler contain redundant information.
      Consider the code:

      package foo
      class Outer<T> {
        class Inner<S> {...}
      }

      and a type expression

      Outer<X>.Inner<Y>

      The signature produced is (as I recall):

      Lfoo/Outer<X>;,Lfoo/Outer/Inner<Y>;

      rather than say

      Lfoo/Outer<X>/Inner<Y>;

      Outer

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

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: