gnash-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnash-commit] gnash/server/asobj Date.cpp


From: Martin Guy
Subject: [Gnash-commit] gnash/server/asobj Date.cpp
Date: Wed, 28 Feb 2007 11:20:14 +0000

CVSROOT:        /sources/gnash
Module name:    gnash
Changes by:     Martin Guy <martinwguy> 07/02/28 11:20:14

Modified files:
        server/asobj   : Date.cpp 

Log message:
        Fix garbled commentary

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnash/server/asobj/Date.cpp?cvsroot=gnash&r1=1.28&r2=1.29

Patches:
Index: Date.cpp
===================================================================
RCS file: /sources/gnash/gnash/server/asobj/Date.cpp,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -b -r1.28 -r1.29
--- Date.cpp    27 Feb 2007 23:47:25 -0000      1.28
+++ Date.cpp    28 Feb 2007 11:20:14 -0000      1.29
@@ -49,17 +49,16 @@
 //     It changes to/from daylight saving time according to its own rules.
 //     We use the operating system's localtime routines.
 //
-// For portability it may be useful to convert this to use libboost's
-// date_time stuff http://www.boost.org/doc/html/date_time.html but the
-// mapping between Flash's perverse behaviour and date_time's coherent
-// behaviour.
-// Plus:
+// It may be useful to convert this to use libboost's date_time stuff
+// http://www.boost.org/doc/html/date_time.html
+// Pros:
 // *   OS portability is done by libboost, not here;
-// *   extends correct date handling from POSIX to 1 Jan 1400 - 31 Dec 9999
-// Minus:
+// *   it extends correct date handling from POSIX to 1 Jan 1400 - 31 Dec 9999
+// Cons:
 // *   it doesn't handle fractions of milliseconds (and who cares?);
-// *   using it to implement this class's methods is more tricky,
-//     including the need to handle all boundary cases and exceptions
+// *   mapping between boost's coherent date_time methods and Flash's
+//     ideosyncratic ones to implement this class' methods is more tricky;
+// *   it brings the need to handle all boundary cases and exceptions
 //     explicitly (e.g. mapping of 38 Nov to 8 Dec, mapping negative
 //     month/day-of-month/hours/min/secs/millisecs into the previous
 //     year/month/day/hour/min/sec and so on).




reply via email to

[Prev in Thread] Current Thread [Next in Thread]