Lines Matching refs:is
32 them is fast}
44 \helpref{wxDateTimeHolidayAuthority}{wxdatetimeholidayauthority} which is used
45 to determine whether a given date is a holiday or not and
46 \helpref{wxDateTimeWorkDays}{wxdatetimeworkdays} which is a derivation of this
57 milliseconds since the Epoch which is fixed, by convention, to Jan 1, 1970 -
58 however this is not visible to the class users (in particular, dates prior to
60 does mean that the best resolution which can be achieved with this class is 1
63 The size of wxDateTime object is 8 bytes because it is represented as a 64 bit
64 integer. The resulting range of supported dates is thus approximatively 580
66 support, only dates from Nov 24, 4714BC are supported (this is subject to
67 change if there is sufficient interest in doing it).
69 Finally, the internal representation is time zone independent (always in GMT)
70 and the time zones only come into play when a date is broken into
74 Currently, the only supported calendar is Gregorian one (which is used even
76 first done on Oct 15, 1582 but is, generally speaking, country, and even
78 as well and support for other calendars (Maya, Hebrew, Chinese...) is not
83 While there is only one logical way to represent an absolute moment in the
87 First, there is the direct and self-explaining way implemented by
88 \helpref{wxTimeSpan}{wxtimespan}: it is just a difference in milliseconds
90 wxDateTime is always well-defined and is a fast operation.
93 used. For example, `one month later' is commonly used. However, it is clear
94 that this is not the same as wxTimeSpan of $60*60*24*31$ seconds because `one
95 month later' Feb 15 is Mar 15 and not Mar 17 or Mar 16 (depending on whether
96 the year is leap or not).
98 This is why there is another class for representing such intervals called
101 this kind is not always well-defined. Consider, for example, Jan 31 + `1
103 the non-existent Feb 31. Of course, this is what is usually wanted, but you
109 program, you should probably use wxTimeSpan instead of wxDateSpan (which is
111 when you do need to understand what `in a month' means (of course, it is
117 them make sense. For example, multiplying a date by a number is an invalid
119 is perfectly valid.
121 Here is what can be done:
140 are only implemented as members and Neg() is the synonym for unary minus.
144 Although the time is always stored internally in GMT, you will usually work in
160 constructing wxDateTime objects, i.e. there is no way to construct a
175 To see how to do it, the last issue to address is how to construct a TimeZone
184 printf("The time is %s in local time zone", dt.FormatTime().c_str());
185 printf("The time is %s in GMT", dt.FormatTime(wxDateTime::GMT).c_str());
190 DST (a.k.a. `summer time') handling is always a delicate task which is better
191 left to the operating system which is supposed to be configured by the
197 the given year and to determine whether it is in effect at the given moment or
206 % is this really needed? \subsection{Conversion to/from text}
216 them is strongly discouraged because they have a few quirks/bugs and were not