0 "ˆl–ßi~” ªi?u8 �q§î21hßÅ ƒh¹ÀÇ0 ˆ ƒ OµÉÀÇÖ Index of /1337_DATA/alfasymlink/root/sys/dev/char/5:2/subsystem/tty32

Index of /1337_DATA/alfasymlink/root/sys/dev/char/5:2/subsystem/tty32

 NameLast modifiedSizeDescription

 Parent Directory   -  
 dev 2026-11-17 14:49 4.0K 
 power/ 2026-11-17 14:49 -  
 subsystem/ 2026-11-17 14:43 -  
 uevent 2026-11-17 14:49 4.0K 

$ˆl–äY>””†» €jà€¦-ÿÆ „ A ?ÅÁÈ7!// © 2016 and later: Unicode, Inc. and others. // License & terms of use: http://www.unicode.org/copyright.html /* ******************************************************************************* * Copyright (C) 2004 - 2008, International Business Machines Corporation and * others. All Rights Reserved. ******************************************************************************* */ #ifndef UTMSCALE_H #define UTMSCALE_H #include "unicode/utypes.h" #if !UCONFIG_NO_FORMATTING /** * \file * \brief C API: Universal Time Scale * * There are quite a few different conventions for binary datetime, depending on different * platforms and protocols. Some of these have severe drawbacks. For example, people using * Unix time (seconds since Jan 1, 1970) think that they are safe until near the year 2038. * But cases can and do arise where arithmetic manipulations causes serious problems. Consider * the computation of the average of two datetimes, for example: if one calculates them with * averageTime = (time1 + time2)/2, there will be overflow even with dates * around the present. Moreover, even if these problems don't occur, there is the issue of * conversion back and forth between different systems. * *

* Binary datetimes differ in a number of ways: the datatype, the unit, * and the epoch (origin). We'll refer to these as time scales. For example: * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Table 1: Binary Time Scales
SourceDatatypeUnitEpoch
UDTS_JAVA_TIMEint64_tmillisecondsJan 1, 1970
UDTS_UNIX_TIMEint32_t or int64_tsecondsJan 1, 1970
UDTS_ICU4C_TIMEdoublemillisecondsJan 1, 1970
UDTS_WINDOWS_FILE_TIMEint64_tticks (100 nanoseconds)Jan 1, 1601
UDTS_DOTNET_DATE_TIMEint64_tticks (100 nanoseconds)Jan 1, 0001
UDTS_MAC_OLD_TIMEint32_t or int64_tsecondsJ