timezone : string; the name of a time zone

The Date object represents a particular date and time in the Gregorian calendar. It represents a particular "view" of the a system UTC time, as represented by a Time object associated to the system UTC clock.

You can create a Date object by calling the Date constructor in several different ways.

Called without arguments, the Date() command returns the current date (and time of day) as reported by the system clock.

You can also pass an explicit UTC Time object t by calling the Date constructor in the form Date( t ).  This produces a Date object that represents the Time object t.

A Date object d can be passed to the Date constructor in the form Date( d ), producing a new Date object that represents the same moment in time as the original Date object d.  This is most useful when used in conjunction with the timezone= option to convert between different time zones.

The Date constructor also takes specific components: year, month, day, hour, minute, second and millisecond. These must be passed in the stated order, but all components after the year are optional in the sense that any initial sub-sequence of these may be passed with the values for omitted components being set to their default values. The default values for components after the year are all $0$, except for hour, for which the default values is $12$ (representing noon). However, you cannot specify any particular component without specifying all the components before it in the sequence. For example, to pass the hour component, you must also specify the year, month and day components (in that order) first.

The year value year must be in the range $\mathrm{-9223372036854775808}\le \mathrm{year}\le 9223372036854775807$ on $64$-bit platforms. On $32$-bit platforms, the year is limited to the range $\mathrm{-4294967296}\le \mathrm{year}\le 4294967295$.

Date objects support a number of methods.

The Year( d ) command returns the (integer) year of the Date object d.

The Month( d ) command returns the numeric month of the Date object d. This is an integer in the range 1 .. 12, with $1$ denoting January, $2$ denoting February, and so on.

The (integer) day of the month of the Date object d is returned by the command DayOfMonth( d ).  This is a positive integer, no larger than the last day of the month represented by d.

The HourOfDay( d ) command returns an integer in the range 0 .. 24 denoting the hour of the day represented by d (that is, a $24$-hour clock). Note that an hour equal to $24$ is equivalent to the $0$th hour of the next day.

The minute of the hour represented by d is returned by the command Minute( d ).

The Second( d ) command returns the number of seconds after the minute of d.

The default time zone of a Date object is the local time zone. The TimeZone( d ) command returns the time zone of d, which may be set explicitly via the timezone = T option.

Since a Date object is just a particular view onto a moment in time, represented by a Time object stored within the Date, it has an associated precision, which is equal to the precision of the underlying clock. In this case, the clock is the SystemUTCClock. The Precision( d ) command returns the precision associated with the Date object d.

In addition to the command-like methods listed above, arithmetic with Date objects is supported, as are comparisons using the operators < and <=.

To compute the length of time between two dates represented by Date objects d1 and d2, use the expression d1 - d2. More generally, a rational combination of Date objects with coefficients that sum to $0$ returns a unit expression of the time dimension.

Similarly, the midpoint between two Date objects d1 and d2 can be computed using the expression (d1 + d2) / 2. Again, more general rational combinations of Date objects with coefficient summing to $1$ return a new Date object representing a generalized "average" of those dates.

Other combinations of Date objects return unevaluated.

Note that leap seconds are ignored in all date and time arithmetic.

$\mathrm{today}≔\mathrm{Date}\left(\right)$

$\mathrm{today}≔\mathrm{<Date:\; 2024-03-01T04:27:09.383\; GMT>}$

$\mathrm{Year}\left(\mathrm{today}\right)$

$2024$

$\mathrm{Month}\left(\mathrm{today}\right)$

$3$

$\mathrm{Minute}\left(\mathrm{today}\right)$

$27$

$\mathrm{today}≔\mathrm{Date}\left(\mathrm{Now}\left(\mathrm{SystemUTCClock}\right)\&comma;'\mathrm{timezone}'=\mathrm{Calendar}:-\mathrm{HostTimeZone}\left(\right)\right)$

$\mathrm{today}≔\mathrm{<Date:\; 2024-03-01T04:27:09\; GMT>}$

$d≔\mathrm{Date}\left(1967\&comma;7\&comma;1\&comma;3\&comma;42\right)$

$d≔\mathrm{<Date:\; 1967-07-01T03:42:00\; GMT>}$

$\mathrm{today}-d$

$1788309909401⟦\mathrm{ms}⟧$

$\mathrm{d1}≔\mathrm{Date}\left(1999\&comma;3\&comma;14\&comma;24\right)$

$\mathrm{d1}≔\mathrm{<Date:\; 1999-03-15T00:00:00\; GMT>}$

$\mathrm{d2}≔\mathrm{Date}\left(1999\&comma;3\&comma;15\&comma;0\right)$

$\mathrm{d2}≔\mathrm{<Date:\; 1999-03-15\; GMT>}$

$\mathrm{d1}-\mathrm{d2}$

$0$

$\mathrm{d1}≔\mathrm{Date}\left(1939\&comma;9\&comma;1\&comma;4\&comma;45\&comma;'\mathrm{timezone}'=''Europe/Berlin''\right)$

$\mathrm{d1}≔\mathrm{<Date:\; 1939-09-01T04:45:00\; Germany\; Time>}$

$\mathrm{d2}≔\mathrm{Date}\left(1945\&comma;9\&comma;2\&comma;9\&comma;'\mathrm{timezone}'=''Asia/Tokyo''\right)$

$\mathrm{d2}≔\mathrm{<Date:\; 1945-09-02T09:00:00\; Japan\; Time>}$

$\mathrm{tdiff}≔\mathrm{d2}-\mathrm{d1}$

$\mathrm{tdiff}≔189461700000⟦\mathrm{ms}⟧$

$\mathrm{convert}\left(\mathrm{tdiff}\&comma;'\mathrm{units}'\&comma;'\mathrm{days}'\right)$

$\frac{70171}{32}⟦d⟧$

$\mathrm{convert}\left(\mathrm{tdiff}\&comma;'\mathrm{units}'\&comma;'\mathrm{years}'\right)$

$6.003807364⟦\mathrm{yr}⟧$

The Date command was introduced in Maple 2018.

For more information on Maple 2018 changes, see Updates in Maple 2018.