public interface ChronoPeriod extends TemporalAmount
This interface models a date-based amount of time in a calendar system.
While most calendar systems use years, months and days, some do not.
Therefore, this interface operates solely in terms of a set of supported
units that are defined by the Chronology
.
The set of supported units is fixed for a given chronology.
The amount of a supported unit may be set to zero.
The period is modeled as a directed amount of time, meaning that individual parts of the period may be negative.
Modifier and Type | Method and Description |
---|---|
Temporal |
addTo(Temporal temporal)
Adds this period to the specified temporal object.
|
static ChronoPeriod |
between(ChronoLocalDate startDateInclusive,
ChronoLocalDate endDateExclusive)
Obtains a
ChronoPeriod consisting of amount of time between two dates. |
boolean |
equals(Object obj)
Checks if this period is equal to another period, including the chronology.
|
long |
get(TemporalUnit unit)
Gets the value of the requested unit.
|
Chronology |
getChronology()
Gets the chronology that defines the meaning of the supported units.
|
List<TemporalUnit> |
getUnits()
Gets the set of units supported by this period.
|
int |
hashCode()
A hash code for this period.
|
default boolean |
isNegative()
Checks if any of the supported units of this period are negative.
|
default boolean |
isZero()
Checks if all the supported units of this period are zero.
|
ChronoPeriod |
minus(TemporalAmount amountToSubtract)
Returns a copy of this period with the specified period subtracted.
|
ChronoPeriod |
multipliedBy(int scalar)
Returns a new instance with each amount in this period in this period
multiplied by the specified scalar.
|
default ChronoPeriod |
negated()
Returns a new instance with each amount in this period negated.
|
ChronoPeriod |
normalized()
Returns a copy of this period with the amounts of each unit normalized.
|
ChronoPeriod |
plus(TemporalAmount amountToAdd)
Returns a copy of this period with the specified period added.
|
Temporal |
subtractFrom(Temporal temporal)
Subtracts this period from the specified temporal object.
|
String |
toString()
Outputs this period as a
String . |
static ChronoPeriod between(ChronoLocalDate startDateInclusive, ChronoLocalDate endDateExclusive)
ChronoPeriod
consisting of amount of time between two dates.
The start date is included, but the end date is not.
The period is calculated using ChronoLocalDate.until(ChronoLocalDate)
.
As such, the calculation is chronology specific.
The chronology of the first date is used. The chronology of the second date is ignored, with the date being converted to the target chronology system before the calculation starts.
The result of this method can be a negative period if the end is before the start. In most cases, the positive/negative sign will be the same in each of the supported fields.
startDateInclusive
- the start date, inclusive, specifying the chronology of the calculation, not nullendDateExclusive
- the end date, exclusive, in any chronology, not nullChronoLocalDate.until(ChronoLocalDate)
long get(TemporalUnit unit)
The supported units are chronology specific.
They will typically be YEARS
,
MONTHS
and DAYS
.
Requesting an unsupported unit will throw an exception.
get
in interface TemporalAmount
unit
- the TemporalUnit
for which to return the valueDateTimeException
- if the unit is not supportedUnsupportedTemporalTypeException
- if the unit is not supportedList<TemporalUnit> getUnits()
The supported units are chronology specific.
They will typically be YEARS
,
MONTHS
and DAYS
.
They are returned in order from largest to smallest.
This set can be used in conjunction with get(TemporalUnit)
to access the entire state of the period.
getUnits
in interface TemporalAmount
Chronology getChronology()
The period is defined by the chronology.
It controls the supported units and restricts addition/subtraction
to ChronoLocalDate
instances of the same chronology.
default boolean isZero()
default boolean isNegative()
ChronoPeriod plus(TemporalAmount amountToAdd)
If the specified amount is a ChronoPeriod
then it must have
the same chronology as this period. Implementations may choose to
accept or reject other TemporalAmount
implementations.
This instance is immutable and unaffected by this method call.
amountToAdd
- the period to add, not nullChronoPeriod
based on this period with the requested period added, not nullArithmeticException
- if numeric overflow occursChronoPeriod minus(TemporalAmount amountToSubtract)
If the specified amount is a ChronoPeriod
then it must have
the same chronology as this period. Implementations may choose to
accept or reject other TemporalAmount
implementations.
This instance is immutable and unaffected by this method call.
amountToSubtract
- the period to subtract, not nullChronoPeriod
based on this period with the requested period subtracted, not nullArithmeticException
- if numeric overflow occursChronoPeriod multipliedBy(int scalar)
This returns a period with each supported unit individually multiplied. For example, a period of "2 years, -3 months and 4 days" multiplied by 3 will return "6 years, -9 months and 12 days". No normalization is performed.
scalar
- the scalar to multiply by, not nullChronoPeriod
based on this period with the amounts multiplied
by the scalar, not nullArithmeticException
- if numeric overflow occursdefault ChronoPeriod negated()
This returns a period with each supported unit individually negated. For example, a period of "2 years, -3 months and 4 days" will be negated to "-2 years, 3 months and -4 days". No normalization is performed.
ChronoPeriod
based on this period with the amounts negated, not nullArithmeticException
- if numeric overflow occurs, which only happens if
one of the units has the value Long.MIN_VALUE
ChronoPeriod normalized()
The process of normalization is specific to each calendar system. For example, in the ISO calendar system, the years and months are normalized but the days are not, such that "15 months" would be normalized to "1 year and 3 months".
This instance is immutable and unaffected by this method call.
ChronoPeriod
based on this period with the amounts of each
unit normalized, not nullArithmeticException
- if numeric overflow occursTemporal addTo(Temporal temporal)
This returns a temporal object of the same observable type as the input with this period added.
In most cases, it is clearer to reverse the calling pattern by using
Temporal.plus(TemporalAmount)
.
// these two lines are equivalent, but the second approach is recommended dateTime = thisPeriod.addTo(dateTime); dateTime = dateTime.plus(thisPeriod);
The specified temporal must have the same chronology as this period. This returns a temporal with the non-zero supported units added.
This instance is immutable and unaffected by this method call.
addTo
in interface TemporalAmount
temporal
- the temporal object to adjust, not nullDateTimeException
- if unable to addArithmeticException
- if numeric overflow occursTemporal subtractFrom(Temporal temporal)
This returns a temporal object of the same observable type as the input with this period subtracted.
In most cases, it is clearer to reverse the calling pattern by using
Temporal.minus(TemporalAmount)
.
// these two lines are equivalent, but the second approach is recommended dateTime = thisPeriod.subtractFrom(dateTime); dateTime = dateTime.minus(thisPeriod);
The specified temporal must have the same chronology as this period. This returns a temporal with the non-zero supported units subtracted.
This instance is immutable and unaffected by this method call.
subtractFrom
in interface TemporalAmount
temporal
- the temporal object to adjust, not nullDateTimeException
- if unable to subtractArithmeticException
- if numeric overflow occursboolean equals(Object obj)
Compares this period with another ensuring that the type, each amount and the chronology are the same. Note that this means that a period of "15 Months" is not equal to a period of "1 Year and 3 Months".
equals
in class Object
obj
- the object to check, null returns falseObject.hashCode()
,
HashMap
int hashCode()
hashCode
in class Object
Object.equals(java.lang.Object)
,
System.identityHashCode(java.lang.Object)
Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2014, Oracle and/or its affiliates. All rights reserved.