Fixed GH-9763: DateTimeZone ctr mishandles input and adds null byte if the argument is an offset larger than 100*60 minutes

Fixed bug #80047 (DatePeriod doesn't warn with custom DateTimeImmutable)

Revert "Fixed #80047: DatePeriod doesn't warn with custom DateTimeImmutable"

This reverts commit 973c3f6e241227ffc14c3608c774d7636b798cec.

Fixed #80047: DatePeriod doesn't warn with custom DateTimeImmutable

Fixed bug #78139 (timezone_open accepts invalid timezone string argument).

Fixed bug #74671 (DST timezone abbreviation has incorrect offset)

Fixed bug #76963 (Null-byte injection in createFromFormat)

Fixed GH-8471: Segmentation fault when converting immutable and mutable DateTime instances created using reflection

Use the new RETURN_THROWS() instead of just returning NULL

Return early when the timezone info is NULL.

The guess_timezone function does throw an error, but throwing an error doesn't
immediate make the PHP_FUNCTION return.

This check is

Return early when the timezone info is NULL.

The guess_timezone function does throw an error, but throwing an error doesn't
immediate make the PHP_FUNCTION return.

This check is really only necessary for distributions that patch PHP's timelib
to use system tzdata, but not correct enough to account for their
implementation to guarantee to return a timezone.

show more ...

Refactor code to avoid duplication

style/readability updates

GH-7979: iterator advances when checking if valid

Fix #81500: Interval serialization regression since 7.3.14 / 7.4.2

While it may not be desired, `DateInterval::$f` supports negative
values, at least with regard to calculations. We sti

Fix #81500: Interval serialization regression since 7.3.14 / 7.4.2

While it may not be desired, `DateInterval::$f` supports negative
values, at least with regard to calculations. We still need to guard
from assigning double values which are out of range for signed 64bit
integers (which would be undefined behavior). zend_dval_to_lval() does
this by returning `0` instead of triggering UB. This way we can avoid
setting the invalid marker, which doesn't work as expected anyway.

We must not do that only for unserialization, but also when the property
is set in the first place.

We need to adapt some of the existing tests wrt. this behavior. In
particular, we check for an arbitrary value in bug79015.phpt, to cater
to differences between 32bit and 64bit architectures.

Closes GH-7575.

show more ...

Move date timezone cache destruction to post deactivate

Some extensions try to use the date features in their own shutdown,
most notably some logging functions. Because of that, move the

Move date timezone cache destruction to post deactivate

Some extensions try to use the date features in their own shutdown,
most notably some logging functions. Because of that, move the
cache tear down until after these resources have been cleaned up.

show more ...

Promote a few forgotten warnings to exceptions

Closes GH-6211

Add some ValueErrors to ext/date

Closes GH-5613

Slightly improve error handling in DatePeriod::__construct()

Fixed bug #80057 (DateTimeImmutable::createFromFormat() does not populate time)

Fix build warnings after timelib update

Don't assert when comparing uninit DateTimeZone objects

Nothing guarantees that the objects are initialized here... just
check as usual.

Fix leak on failed DatePeriod initialization

We need to free not only p here, but also b and e.

Add some missing DatePeriod initialization checks

Prefer strtoll over atoll

Both are specified by C99, but strtoll has specified overflow
behavior while atoll does not, so prefer using it.

datetime: new format "p", same as "P" but returning "Z" for UTC