Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68027
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain b1-systems.de designates 84.200.69.220 as permitted sender)
Message-ID: <51D12790.106@b1-systems.de>
Date: Mon, 01 Jul 2013 08:54:08 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: internals@lists.php.net
References: <51D0AA4C.9020805@sugarcrm.com> <2e3d0947cdbe7832ec27295eadad9b5d@nebm.ist.utl.pt> <51D0E896.10300@sugarcrm.com> <d9af685a6e261684b4bbcedd458a4e58@nebm.ist.utl.pt> <51D0F93E.4080505@sugarcrm.com>
In-Reply-To: <51D0F93E.4080505@sugarcrm.com>
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="----enig2AWFQKFDMDSENRSPEUTQC"
Subject: Re: [PHP-DEV] Re: IntlTimeZone::getOffset?
From: lang@b1-systems.de (Ralf Lang)

------enig2AWFQKFDMDSENRSPEUTQC
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 01.07.2013 05:36, Stas Malyshev wrote:
> Hi!
>=20
>> This is not correct. Some functions in IntlCalendar also use this=20
>> 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
>=20
> OK, I see.

> I am just surprised we have an API that works differently from all othe=
r
> 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).
>=20
> 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.
>=20

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.


--=20
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: lang@b1-systems.de
B1 Systems GmbH
Osterfeldstra=C3=9Fe 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537


------enig2AWFQKFDMDSENRSPEUTQC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlHRJ5AACgkQCs1dsHJ/X7CIaACgpZPCy5VEiVF1bpIAmoFtawzf
OkUAoLdJWyNmZi6bGF+sAttVPzddGIlm
=UXSK
-----END PGP SIGNATURE-----

------enig2AWFQKFDMDSENRSPEUTQC--