Matreshka provides support for date/time operations, including such complicated things as calendars, time zones, leap seconds, and localization. All complexity is hidden under simple API for applications.
Matreshka provides three types to represent date/time related information in the League.Calendars package:
- Time - represents time inside one day;
- Date - represents date;
- Date_Time - represents date/time information. Unlike two previous types all operations on this type take in sense current or user specified time zone.
These types are used only to store information. Several additional packages are provided to extract components of date/time, to format and parse string representation of date/time and to manipulate by values of objects:
- League.Calendars.ISO_8601 - implements calendar operations as specified by ISO-8601 standard. It is based on proleptic Gregorian calendar with astronomical year numbering.
- League.Calendars.Gregorian - implements most useful mixed Gregorian/Julian calendar. Date of switch from Julian to Gregorian calendars depends from locale. There is no year number zero. Not yet implemented.
Date Format Patterns
A date pattern is a string of characters, where specific strings of characters are replaced with date and time data from a calendar when formatting or used to generate data for a calendar when parsing.
Characters may be used multiple times. For example, if y is used for the year, 'yy' might produce '99', whereas 'yyyy' produces '1999'. For most numerical fields, the number of characters specifies the field width. For example, if h is the hour, 'h' might produce '5', but 'hh' produces '05'. For some characters, the count specifies whether an abbreviated or full form should be used, but may have other choices, as given below.
Two single quotes represents a literal single quote, either inside or outside single quotes. Text within single quotes is not interpreted in any way (except for two adjacent single quotes). Otherwise all ASCII letter from a to z and A to Z are reserved as syntax characters, and require quoting if they are to represent literal characters. In addition, certain ASCII punctuation characters may become variable in the future (eg ":" being interpreted as the time separator and '/' as a date separator, and replaced by respective locale-sensitive characters in display).
Note: the counter-intuitive use of 5 letters for the narrow form of weekdays and months is forced by backwards compatibility.
|Field||Character||Number pf occurrences||Description|
|era||G||1..3||Era - Replaced with the Era string for the current date. One to three letters for the abbreviated form, four letters for the long form, five for the narrow form.|
|year||y||1..n||Year. Normally the length specifies the padding, but for two letters it also specifies the maximum length.|
|Y||1..n||Year (in "Week of Year" based calendars). This year designation is used in ISO year-week calendar as defined by ISO 8601, but can be used in non-Gregorian based calendar systems where week date processing is desired. May not always be the same value as calendar year.|
|u||1..n||Extended year. This is a single number designating the year of this calendar system, encompassing all supra-year fields. For example, for the Julian calendar system, year numbers are positive, with an era of BCE or CE. An extended year value for the Julian calendar system assigns positive values to CE years and negative values to BCE years, with 1 BCE being year 0.|
|quarter||Q||1..2||Quarter - Use one or two for the numerical quarter, three for the abbreviation, or four for the full name.|
|q||1..2||Stand-Alone Quarter - Use one or two for the numerical quarter, three for the abbreviation, or four for the full name.|
|month||M||1..2||Month - Use one or two for the numerical month, three for the abbreviation, or four for the full name, or five for the narrow name.|
|L||1..2||Stand-Alone Month - Use one or two for the numerical month, three for the abbreviation, or four for the full name, or 5 for the narrow name.|
|l||1||Special symbol for Chinese leap month, used in combination with M. Only used with the Chinese calendar.|
|week||w||1..2||Week of Year.|
|W||1||Week of Month.|
|day||d||1..2||Date - Day of the month.|
|D||1..3||Day of year.|
|F||1||Day of Week in Month.|
|g||1..n||Modified Julian day. This is different from the conventional Julian day number in two regards. First, it demarcates days at local zone midnight, rather than noon GMT. Second, it is a local number; that is, it depends on the local time zone. It can be thought of as a single number that encompasses all the date-related fields.|
|week day||E||1..3||Day of week - Use one through three letters for the short day, or four for the full name, or five for the narrow name.|
|e||1..2||Local day of week. Same as E except adds a numeric value that will depend on the local starting day of the week, using one or two letters.|
|c||1||Stand-Alone local day of week - Use one letter for the local numeric value (same as 'e'), three for the short day, or four for the full name, or five for the narrow name.|
|period||a||1||AM or PM|
|minute||m||1..2||Minute. Use one or two for zero padding.|
|second||s||1..2||Second. Use one or two for zero padding.|
|S||1..n||Fractional Second - truncates (like other time fields) to the count of letters.|
|A||1..n||Milliseconds in day. This field behaves exactly like a composite of all time-related fields, not including the zone fields. As such, it also reflects discontinuities of those fields on DST transition days. On a day of DST onset, it will jump forward. On a day of DST cessation, it will jump backward. This reflects the fact that is must be combined with the offset field to obtain a unique local time value.|
|j||1..2||This is a special-purpose symbol. It must not occur in pattern or skeleton data. Instead, it is reserved for use in APIs doing flexible date pattern generation. In such a context, it requests the preferred format (12 versus 24 hour) for the language in question, as determined by whether h, H, K, or k is used in the standard short time format for the locale, and should be replaced by h, H, K, or k before beginning a match against availableFormats data. not supported|
All non-letter character represent themselves in a pattern, except for the single quote. It is used to 'escape' letters. Two single quotes in a row, whether inside or outside a quoted sequence, represent a 'real' single quote.
Below is small example of use of calendar support, it takes current date/time from system clock and output it to console.
with Ada.Wide_Wide_Text_IO; with League.Calendars.ISO_8601; with League.Strings; procedure Main is X : League.Calendars.Date_Time := League.Calendars.Clock; begin Ada.Wide_Wide_Text_IO.Put_Line (League.Calendars.ISO_8601.Image (League.Strings.To_Universal_String ("yyyy-MM-dd HH:mm:ss"), X).To_Wide_Wide_String); end Main;