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

API: java.util.{Gregorian,}Calendar are in need of fixed API

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Duplicate
    • Icon: P5 P5
    • None
    • 1.2.0
    • core-libs



      Name: clC74495 Date: 09/08/98


      Speaking with much experience now, All the millisecond methods
      in the Calendar classes need to be exposes, like why is "long getTimeInMillis()"
      marked as protected, but "Date getTime()" public? Then I just need to call
      Date.getTime() to get the milliseconds, but this object proliferation is really
      killing my performance, besides it is not very consistant. Also, Why do the
      Calendar classes have to good(tm) ctors ? Like ones that accept a Date or long
      to set the initial time? The same goes with the setTimeInMillis(long) method.
      If you are going to deprecate 3/4 of the Date class, then do it the right way?
       Like why is Date.getTime() almost the only method left ? why didnt that get
      rolled into Calendar ? Makes sense. After this weekend, I dont ever want to
      touch the Calendar classes again.
      (Review ID: 38439)
      ======================================================================

            okutsu Masayoshi Okutsu
            clucasius Carlos Lucasius (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: