Hi,
On Mon, 16 Jun 2025, Marc Bennewitz wrote:
> It's 12.5 years only until the timestamps in PHP on 32bit will not work as
> expected anymore.
>
> The DateTime[Immutable] classes use 64bit integers internally already but
> there are still a couple of places where this is an issue in the API due
On Mon, 16 Jun 2025, Alexandru Pătrănescu wrote:
> On Mon, Jun 16, 2025 at 4:03 PM Marc Bennewitz wrote:
>
> > It's 12.5 years only until the timestamps in PHP on 32bit will not
> > work as expected anymore.
>
> I think that maybe we can already deprecate supporting 32 bit builds.
> And, mayb
On Wed, Jun 18, 2025, at 13:18, Marc Bennewitz wrote:
>
>
> On 16.06.25 19:01, Yogarine wrote:
>> Hi all,
>>
>> On 16 Jun 2025, at 17:24, Rob Landers wrote:
>>> On Mon, Jun 16, 2025, at 16:54, Alexandru Pătrănescu wrote:
On Mon, Jun 16, 2025 at 4:03 PM Marc Bennewitz wrote:
Hi all,
>
On 16.06.25 19:01, Yogarine wrote:
Hi all,
On 16 Jun 2025, at 17:24, Rob Landers wrote:
On Mon, Jun 16, 2025, at 16:54, Alexandru Pătrănescu wrote:
On Mon, Jun 16, 2025 at 4:03 PM Marc Bennewitz wrote:
Hi all,
It's 12.5 years only until the timestamps in PHP on 32bit will not work
as exp
On 16.06.25 17:21, Rob Landers wrote:
On Mon, Jun 16, 2025, at 16:54, Alexandru Pătrănescu wrote:
On Mon, Jun 16, 2025 at 4:03 PM Marc Bennewitz wrote:
Hi all,
It's 12.5 years only until the timestamps in PHP on 32bit will
not work
as expected anymore.
Hi,
I think that
Hi all,
On 16 Jun 2025, at 17:24, Rob Landers wrote:
>
>
>
> On Mon, Jun 16, 2025, at 16:54, Alexandru Pătrănescu wrote:
>>
>>
>>
>> On Mon, Jun 16, 2025 at 4:03 PM Marc Bennewitz wrote:
>> Hi all,
>>
>> It's 12.5 years only until the timestamps in PHP on 32bit will not work
>> as expe
On Mon, Jun 16, 2025, at 16:54, Alexandru Pătrănescu wrote:
>
> On Mon, Jun 16, 2025 at 4:03 PM Marc Bennewitz wrote:
>> Hi all,
>>
>> It's 12.5 years only until the timestamps in PHP on 32bit will not work
>> as expected anymore.
>>
>
> Hi,
>
> I think that maybe we can already deprecate
On Mon, Jun 16, 2025 at 4:03 PM Marc Bennewitz wrote:
> Hi all,
>
> It's 12.5 years only until the timestamps in PHP on 32bit will not work
> as expected anymore.
>
>
>
Hi,
I think that maybe we can already deprecate supporting 32 bit builds.
And, maybe with PHP 9, or PHP 10, or with a future ve
If you use 32bit version of PHP then of course you will run into this
problem. But 32bit versions are used infrequently now, and this is a
known limitation. As far as I know, these functions have no issues
with year 2038 in 64bit. My point is that these functions work fine
and the fact that 32bit i
On 16.06.25 16:16, Kamil Tekiela wrote:
Why do you say that these functions do not work with year 2038?
https://3v4l.org/61VLh
I wouldn't be opposed to deprecating them, but I don't know if we have
a good enough reason to do so.
https://3v4l.org seems to be 64bit now ;) -> https://3v4l.org/1F
Including the EOL versions on that link shows that this occurs on <
5.2.6 only
On 16/06/2025 16:16, Kamil Tekiela wrote:
Why do you say that these functions do not work with year 2038?
https://3v4l.org/61VLh
I wouldn't be opposed to deprecating them, but I don't know if we have
a good enough r
Why do you say that these functions do not work with year 2038?
https://3v4l.org/61VLh
I wouldn't be opposed to deprecating them, but I don't know if we have
a good enough reason to do so.
On Mon, Jun 16, 2025 at 03:01:00PM +0200, Marc Bennewitz wrote:
> Alternatively, zend_long could be migrated to int64_t or arbitrary integers
> like proposed by Andrea Faulds back in 2014
>
> What do you think?
>
https://wiki.php.net/rfc/bigint
+1
--
Alain Williams
Linux/GNU Consultant - Mail
Hi all,
It's 12.5 years only until the timestamps in PHP on 32bit will not work
as expected anymore.
The DateTime[Immutable] classes use 64bit integers internally already
but there are still a couple of places where this is an issue in the API
due to PHP integer limit:
Based on that I pers
14 matches
Mail list logo
