- * Access to date and time using fields and units, additional value type classes and - * base support for calendar systems other than the default ISO. + * Access to date and time using fields and units, and date time adjusters. *
** This package expands on the base package to provide additional functionality for @@ -74,8 +73,6 @@ *
@@ -122,8 +119,7 @@ * Applications can also define adjusters by implementing {@code TemporalAdjuster}. *
*- * There are additional interfaces to model addition to and subtraction from a date-time. - * These are {@link java.time.temporal.TemporalAdder} and {@link java.time.temporal.TemporalSubtractor}. + * The {@link java.time.temporal.TemporalAmount} interface models amounts of relative time. *
** In addition to adjusting a date-time, an interface is provided to enable querying - @@ -144,60 +140,9 @@ *
* The ISO calendar system defines an additional week-based division of years. * This defines a year based on whole Monday to Monday weeks. - * This is modeled in {@link java.time.temporal.ISOFields}. + * This is modeled in {@link java.time.temporal.IsoFields}. *
* - *- * The main API is based around the calendar system defined in ISO-8601. - * However, there are other calendar systems, and this package provides basic support for them. - * The alternate calendars are provided in the {@code java.time.calendar} package. - *
- *- * A calendar system is defined by the {@link java.time.temporal.Chrono} interface, - * while a date in a calendar system is defined by the {@link java.time.temporal.ChronoLocalDate} interface. - *
- *- * It is intended that applications use the main API whenever possible, including code to read and write - * from a persistent data store, such as a database, and to send dates and times across a network. - * The "chrono" classes are then used at the user interface level to deal with localized input/output. - *
- *- * Using non-ISO calendar systems in an application introduces significant extra complexity. - * Ensure that the warnings and recommendations in {@code ChronoLocalDate} have been read before - * working with the "chrono" interfaces. - *
- *- * This example creates and uses a date in a non-ISO calendar system. - *
- *
- * // Print the Thai Buddhist date
- * ChronoLocalDate<ThaiBuddhistChrono> now1 = ThaiBuddhistChrono.INSTANCE.dateNow();
- * int day = now1.get(ChronoField.DAY_OF_MONTH);
- * int dow = now1.get(ChronoField.DAY_OF_WEEK);
- * int month = now1.get(ChronoField.MONTH_OF_YEAR);
- * int year = now1.get(ChronoField.YEAR);
- * System.out.printf(" Today is %s %s %d-%s-%d%n", now1.getChrono().getId(),
- * dow, day, month, year);
- *
- * // Enumerate the list of available calendars and print today for each
- * Set<Chrono<?>> chronos = Chrono.getAvailableChronologies();
- * for (Chrono<?> chrono : chronos) {
- * ChronoLocalDate<?> date = chrono.dateNow();
- * System.out.printf(" %20s: %s%n", chrono.getId(), date.toString());
- * }
- *
- * // Print today's date and the last day of the year for the Thai Buddhist Calendar.
- * ChronoLocalDate<ThaiBuddhistChrono> first = now1
- * .with(ChronoField.DAY_OF_MONTH, 1)
- * .with(ChronoField.MONTH_OF_YEAR, 1);
- * ChronoLocalDate<ThaiBuddhistChrono> last = first
- * .plus(1, ChronoUnit.YEARS)
- * .minus(1, ChronoUnit.DAYS);
- * System.out.printf(" %s: 1st of year: %s; end of year: %s%n", last.getChrono().getId(),
- * first, last);
- *
- *
* * Unless otherwise noted, passing a null argument to a constructor or method in any class or interface