strptime
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | strptime [2009/06/14 20:54] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | # $EPIC: strptime.txt, | ||
+ | ======Synopsis: | ||
+ | $__strptime__("< | ||
+ | |||
+ | ======Technical: | ||
+ | * If the < | ||
+ | * If the < | ||
+ | * If the < | ||
+ | * If your < | ||
+ | * If your < | ||
+ | * The first argument is a dword describing (in strftime(3) format) what format your human-readable string is in. | ||
+ | * The rest of the argument(s) are taken as a string which matches < | ||
+ | * The return value of the function is the specified time converted into a unix timestamp. | ||
+ | * Avoid using system-specific strftime(3) formats for portability reasons. | ||
+ | |||
+ | ======Practical: | ||
+ | You should refer to your system' | ||
+ | for exact details of what a strftime format looks like, because describing | ||
+ | them is beyond the scope of a help file. =) But this function is very | ||
+ | useful for converting timestamps in different formats into a unix timestamp. | ||
+ | |||
+ | The behavior of strptime in epic is highly dependent upon the strptime(3) | ||
+ | implementation of the system it is running on. If you intend to use this | ||
+ | function in portable scripts you should avoid the use of system-specific | ||
+ | format strings. | ||
+ | |||
+ | On systems with a 32 bit time_t this function is only practical for describing | ||
+ | dates between Fri Dec 13 20:45:52 1901 and Tue Jan 19 03:14:07 2038. | ||
+ | |||
+ | ======Returns: | ||
+ | The number of seconds since the epoch, which is typically 1970 Jan 1, 00:00 UTC. | ||
+ | |||
+ | ======Examples: | ||
+ | < | ||
+ | $strptime(" | ||
+ | $strptime(" | ||
+ | $strptime(" | ||
+ | $strptime(" | ||
+ | </ | ||
+ | |||
+ | ======History: | ||
+ | This function first appeared in epic5-0.3.6. | ||
strptime.txt · Last modified: 2009/06/14 20:54 by 127.0.0.1