LocalTime implements the {@link ReadablePartial} interface.To do this, the interface methods focus on the key fields - HourOfDay, MinuteOfHour, SecondOfMinute and MillisOfSecond. However, all time fields may in fact be queried.
Calculations on LocalTime are performed using a {@link Chronology}. This chronology will be set internally to be in the UTC time zone for all calculations.
Each individual field can be queried in two ways:
getHourOfDay() hourOfDay().get() LocalTime is thread-safe and immutable, provided that the Chronology is as well. All standard Chronology classes supplied are thread-safe and immutable. @author Stephen Colebourne @since 1.3
{@code LocalTime} is an immutable date-time object that represents a time,often viewed as hour-minute-second. Time is represented to nanosecond precision. For example, the value "13:45.30.123456789" can be stored in a {@code LocalTime}.
It does not store or represent a date or time-zone. Instead, it is a description of the local time as seen on a wall clock. It cannot represent an instant on the time-line without additional information such as an offset or time-zone.
The ISO-8601 calendar system is the modern civil calendar system used today in most of the world. This API assumes that all calendar systems use the same representation, this class, for time-of-day.
This is a value-based class; use of identity-sensitive operations (including reference equality ( {@code ==}), identity hash code, or synchronization) on instances of {@code LocalTime} may have unpredictable results and should be avoided.The {@code equals} method should be used for comparisons. @implSpec This class is immutable and thread-safe. @since 1.8
LocalTime is an immutable calendrical that represents a time, often viewed as hour-minute-second.
This class stores all time fields, to a precision of nanoseconds. It does not store or represent a date or time zone. Thus, for example, the value "13:45.30.123456789" can be stored in a LocalTime.
LocalTime is immutable and thread-safe. @author Michael Nascimento Santos @author Stephen Colebourne
LocalTime implements the {@link ReadablePartial} interface.To do this, the interface methods focus on the key fields - HourOfDay, MinuteOfHour, SecondOfMinute and MillisOfSecond. However, all time fields may in fact be queried.
Calculations on LocalTime are performed using a {@link Chronology}. This chronology will be set internally to be in the UTC time zone for all calculations.
Each individual field can be queried in two ways:
getHourOfDay() hourOfDay().get() LocalTime is thread-safe and immutable, provided that the Chronology is as well. All standard Chronology classes supplied are thread-safe and immutable. @author Stephen Colebourne @since 1.3
{@code LocalTime} is an immutable date-time object that represents a time,often viewed as hour-minute-second. Time is represented to nanosecond precision. For example, the value "13:45.30.123456789" can be stored in a {@code LocalTime}.
It does not store or represent a date or time-zone. Instead, it is a description of the local time as seen on a wall clock. It cannot represent an instant on the time-line without additional information such as an offset or time-zone.
The ISO-8601 calendar system is the modern civil calendar system used today in most of the world. This API assumes that all calendar systems use the same representation, this class, for time-of-day.
| |
| |
| |