Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4471250

revise use of final classes, members in serialization implementation

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P5 P5
    • 1.4.0
    • 1.4.0
    • core-libs
    • None
    • beta2
    • generic
    • generic
    • Verified

      Use of the "final" keyword in current (merlin) serialization code is
      somewhat arbitrary--many private or package-private nested classes are declared
      final though they need not be (in these cases, "final" was originally added
      under the mistaken impression that it could help performance); many fields
      which hold immutable state are not declared final even though they should be.
      Declaring as final those fields which store "final" state would make the code
      easier to maintain.

            mwarressunw Michael Warres (Inactive)
            mwarressunw Michael Warres (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: