$Sir DateNM: Difference between revisions
Jump to navigation
Jump to search
m (1 revision) |
m (1 revision) |
||
Line 30: | Line 30: | ||
<ul> | <ul> | ||
<li>Values returned by <var>$Sir_DateNM</var> will exceed the range that can be represented in a 4-byte integer, so you should probably avoid storing the value in a BINARY or FLOAT4 field. | <li>Values returned by <var>$Sir_DateNM</var> will exceed the range that can be represented in a 4-byte integer, so you should probably avoid storing the value in a BINARY or FLOAT4 field. | ||
<li>To obtain the current date and time in a readable form, use $Sir_Date. | <li>To obtain the current date and time in a readable form, use <var>$Sir_Date</var>. | ||
<li>To convert the number of milliseconds to a readable form, use $Sir_NM2Date. | <li>To convert the number of milliseconds to a readable form, use <var>$Sir_NM2Date</var>. | ||
</ul> | </ul> | ||
Revision as of 21:28, 19 October 2012
Current date and time as number of milliseconds
Most Sirius $functions have been deprecated in favor of Object Oriented methods. The OO equivalent of $Sir_DateNM is CurrentTimeMilliseconds.
The $Sir_DateNM function has no arguments and returns the number of 1/1000th seconds since 1 January, 1900.
Syntax
<section begin="syntax" /> %num = $Sir_DateNM <section end="syntax" />
where
%num | set to the number of 1/1000th seconds (milliseconds) from 1 Jan 1900 12:00 AM to the current date and time. |
---|
For example, the following fragment will print the date and time 1.8 seconds from the current time:
PRINT $Sir_NM2Date($Sir_DateNM + 1800, 'MM/DD/YY HH:MI:SS.XX')
$Sir_DateNM has no error conditions.
Notes:
- Values returned by $Sir_DateNM will exceed the range that can be represented in a 4-byte integer, so you should probably avoid storing the value in a BINARY or FLOAT4 field.
- To obtain the current date and time in a readable form, use $Sir_Date.
- To convert the number of milliseconds to a readable form, use $Sir_NM2Date.