[OpenBSD]

Manual Page Search Parameters
STRPTIME(3) Library Functions Manual STRPTIME(3)

strptime —
converts a character string to a time value

#include <time.h>

char *
strptime(const char *buf, const char *format, struct tm *tm);

The strptime function parses the string buf according to the specified format and fills matching data into the structure tm (described in mktime(3)).

The format string consists of zero or more directives. A directive is composed of either one or more whitespace characters as defined by isspace(3), an ordinary character (neither ‘%’ nor a whitespace), or a conversion specification. A conversion specification consists of a percent sign (‘%’) followed by one or two conversion characters which specify the replacement required. There must be whitespace or other non-alphanumeric characters between any two conversion specifications.

The LC_TIME category defines the locale values for the conversion specifications. The following conversion specifications are supported:

the day of week, using the locale's weekday names; either the abbreviated or full name may be specified.
the same as %a.
the month, using the locale's month names; either the abbreviated or full name may be specified.
the same as %b.
the date and time, using the locale's date and time format.
the century number [0,99]; leading zeros are permitted but not required. Note that the converted value is added to the current value of the tm_year field (in order that the "%y" conversion be useful).
the day of month [1,31]; leading zeros are permitted but not required.
the date as %m/%d/%y.
the same as %d.
the date as %Y-%m-%d (the ISO 8601 date format).
the year corresponding to the ISO week number, without the century.
the year corresponding to the ISO week number, with the century.
the same as %b.
the hour (24-hour clock) [0,23]; leading zeros are permitted but not required.
the hour (12-hour clock) [1,12]; leading zeros are permitted but not required.
the day number of the year [1,366]; leading zeros are permitted but not required.
the same as %H.
the same as %I.
the month number [1,12]; leading zeros are permitted but not required.
the minute [0,59]; leading zeros are permitted but not required.
any whitespace.
the locale's equivalent of “AM” or “PM”.
the time as %I:%M:%S %p.
the time as %H:%M.
the seconds [0,60]; leading zeros are permitted but not required.
the number of seconds since the Epoch, UTC (see mktime(3)).
any whitespace.
the time as %H:%M:%S.
the day of the week as a decimal number, where Monday = 1.
the week number of the year (Sunday as the first day of the week) as a decimal number [0,53]; leading zeros are permitted but not required. All days in a year preceding the first Sunday are considered to be in week 0.
the ISO 8601 week number as a decimal number. If the week (starting on Monday) that contains January 1 has more than three days in the new year, then it is considered the first week of the year. If it has fewer than four days in the new year, then it is considered the last week of the previous year. Weeks are numbered from 1 to 53.
the weekday as a decimal number [0,6], with 0 representing Sunday; leading zeros are permitted but not required.
the week number of the year (Monday as the first day of the week) as a decimal number [0,53]; leading zeros are permitted but not required. All days in a year preceding the first Monday are considered to be in week 0.
the date, using the locale's date format.
the time, using the locale's time format.
the year within the current century. When a century is not otherwise specified, values in the range 69-99 refer to years in the twentieth century (1969 to 1999 inclusive); values in the range 00-68 refer to years in the twenty-first century (2000 to 2068 inclusive). Leading zeros are permitted but not required.
the year, including the century (i.e., 1998).
an ISO 8601 or RFC 5322 timezone specification. This is one of the following: the offset from Coordinated Universal Time (‘UTC’) specified as: “[+-]hhmm”, “[+-]hh:mm”, or “[+-]hh”; ‘UTC’ specified as: “GMT” (‘Greenwich Mean Time’), “UT” (‘Universal Time’), or “Z” (‘Zulu Time’); a three character US timezone specified as: “EDT”, “EST”, “CDT”, “CST”, “MDT”, “MST”, “PDT”, or “PST”, with the first letter standing for ‘Eastern’ (“E”), ‘Central’ (“C”), ‘Mountain’ (“M”) or ‘Pacific’ (“P”), and the second letter standing for ‘Daylight’ (“D” or summer) time or ‘Standard’ (“S”) time; a single letter military timezone specified as: “A” through “I” and “K” through “Y”.
timezone name or no characters when timezone information is unavailable.
A `%' is read. No argument is converted.

There is no way to specify whether Daylight Saving Time is in effect when calling strptime. To use the resulting tm structure with functions that check the tm_isdst field, either set it to a negative value, which will cause mktime(3) to attempt to divine whether Daylight Saving Time would be in effect for the given time, or compute the value manually.

For compatibility, certain conversion specifications can be modified by the E and O modifier characters to indicate that an alternative format or specification should be used rather than the one normally used by the unmodified conversion specification. As there are currently neither alternative formats nor specifications supported by the system, the behavior will be as if the unmodified conversion specification were used.

Case is ignored when matching string items in buf, such as month and weekday names.

If successful, the strptime function returns a pointer to the character following the last character parsed. Otherwise, a null pointer is returned.

mktime(3), strftime(3)

The strptime() function conforms to X/Open Portability Guide Issue 4, Version 2 (“XPG4.2”).

The ‘%G’, ‘%g’, ‘%s’, ‘%u’, ‘%V’, ‘%Y’, and ‘%Z’ conversion specifications are extensions.

The %Z format specifier only accepts timezone abbreviations of the local timezone, or the value “GMT”. This limitation is caused by the ambiguity of overloaded timezone abbreviations, for example EST is both Eastern Standard Time and Eastern Australia Summer Time.
January 21, 2019 OpenBSD-current