Hi all,
REALbasic 2005r4
Mac OS X 10.3.9
We already have this discussion here sometimes ago, so please, do not arg about
the pros and the cons of aDate2 = aDate1.
In a current project (that I finished now ?), I use two Date Classes object: now
as a Window Global Property and theDate as a local Method variable. *
When the time to add the second and local Date Class come, I remember the aDate1
= aDate2 discussion (for once that I remember something !) and used the code
below instead:
theDate.Day = now.Day
theDate.Month = now.Month
theDate.Year = now.Year
OK: I could use "theDate.TotalSeconds = now.TotalSeconds" instead, but it seems
for me crystal clear this way and I only needed Day, Month and Year ;)
BTW: what was the purpose of this mail ? Oh, I recall now !
The Language Reference pdf for REALbasic 2006r1 (Version 2006R1, January, 2006)
does not talks / warn about the result of aDate2 = aDate1 (what will goes into
aDate2).
???
Emile
* This allows me to avoid some bugs / remove if .../... end if code to squash
thoses bugs (or cases if you prefer, these are not bugs per se, but calendar
special cases).
PS: who's birthday is on 1954-02-10 ?
Mine is some days later...
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|