On 01.07.2013 05:36, Stas Malyshev wrote: > Hi! > >> This is not correct. Some functions in IntlCalendar also use this >> direct representation of UDate, see e.g. >> >> http://pt2.php.net/manual/en/intlcalendar.getnow.php >> http://pt2.php.net/manual/en/intlcalendar.gettime.php > > OK, I see.
> I am just surprised we have an API that works differently from all other > APIs in PHP, and for what seems to be not better reason that > compatibility with internal representation of the library (which we > don't preserve in many other cases). > > Re-reading the mail thread back when it was merged, I recall now I was > surprised by that back then too. Could we at least have some > documentation for it so that it could be clear what's going on and how > these functions go together? Since we had no RFC for this functionality > at all, and still no docs except for skeletal ones more than a year > after merge, it makes it really hard to understand what's going on. > Converting between php based timestamps (s based) and javascript timestamps (s/1000 based) is confusing enough. If PHP introduces s/1000 based timestamps, I think it's best to have a consistent set of functions/classes that all accept the same. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: l...@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
signature.asc
Description: OpenPGP digital signature
