Fix #78609: mb_check_encoding() no longer supports stringable objects

We apply type juggling for other types than array.

Fix #78579: mb_decode_numericentity: args number inconsistency

mb_decode_numericentity() accepts a fourth optional parameter, which is
unused, however. Since this parameter doesn't do a

Fix #78579: mb_decode_numericentity: args number inconsistency

mb_decode_numericentity() accepts a fourth optional parameter, which is
unused, however. Since this parameter doesn't do any harm, and to avoid
the small BC break, we're keeping this parameter for PHP 7, but adjust
the arginfo.

For PHP 8, we will remove this parameter.

show more ...

Fix key leaks in mb_convert_encoding()

Fixed bug #77454

Trim trailing whitespace in source code files

Fix #76704: mb_detect_order return value varies based on argument type

php_mb_parse_encoding_list() and php_mb_parse_encoding_array() are
supposed to return SUCCESS and FAILURE, not 1 an

Fix #76704: mb_detect_order return value varies based on argument type

php_mb_parse_encoding_list() and php_mb_parse_encoding_array() are
supposed to return SUCCESS and FAILURE, not 1 and 0, respectively.

show more ...

year++

year++

Fix proto documents for new global functions

See NEWS and UPGRADING (or arginfo/implementation) for details.

Check for empty string in mb_ord()

Also check for invalid codepoints in mb_ord()

And return false in that case, instead of returning 0x3f...

Return false on invalid codepoint in mb_chr()

Instead of returning the encoding of the current substitution
character. This allows a robust check for the failure case. The
substituti

Return false on invalid codepoint in mb_chr()

Instead of returning the encoding of the current substitution
character. This allows a robust check for the failure case. The
substitution character (especially the default of "?") is also
a valid output of mb_chr() for a valid input (for "?" that would be
0x3f), so it's a bad choice for an error value.

show more ...

Always use Unicode codepoints in mb_ord() and mb_chr()

Previously mb_chr() had two different encoding-dependent behaviors:
* For "Unicode-encodings" it took a Unicode codepoint and retu

Always use Unicode codepoints in mb_ord() and mb_chr()

Previously mb_chr() had two different encoding-dependent behaviors:
* For "Unicode-encodings" it took a Unicode codepoint and returned
its encoded representation.
* Otherwise it returned a big-endian binary encoding of the passed
integer.

Now the input is always interpreted as a Unicode codepoint. If
a big-endian binary encoding is what you want, you don't need
mbstring to implement that.

show more ...

Revert/fix substitution character fallback

The introduced checks were not correct in two respects:
* It was checked whether the source encoding of the string matches
the internal

Revert/fix substitution character fallback

The introduced checks were not correct in two respects:
* It was checked whether the source encoding of the string matches
the internal encoding, while the actually relevant encoding is
the *target* encoding.
* Even if the correct encoding is used, the checks are still too
conservative. Just because something is not a "Unicode-encoding"
does not mean that it does not map any non-ASCII characters.

I've reverted the added checks and instead adjusted mbfl_convert
to first try to use the provided substitution character and if
that fails, perform the fallback to '?' at that point. This means
that any codepoint mapped in the target encoding should now be
correctly supported and anything else should fall back to '?'.

show more ...

Revert/fix mb_substitute_character() codepoint checks

The introduced checks did not treat "non-Unicode" encodings correctly,
because they treated the passed integer as encoded in the int

Revert/fix mb_substitute_character() codepoint checks

The introduced checks did not treat "non-Unicode" encodings correctly,
because they treated the passed integer as encoded in the internal
encoding in that case, while in actuality the substitute character
is always a Unicode codepoint.

Additionally checking the codepoint against the internal encoding
is not correct in any case, because the substitution character must
be mapped in the *target* encoding of the conversion, which does
not necessarily coincide with the internal encoding (the internal
encoding is the default *source* encoding, not *target* encoding).

This reverts the checks back to simple range checks, but in a way
that still resolves #69079: Characters outside the Basic
Multilingual Plane are now accepted and Surrogate Codepoints are
rejected. A distinction between UTF-8 and non-UTF-8 encodings is
not made for surrogate checks (as in the original patch), as
surrogates are always illegal on their own. Specifying a surrogate
as substitution character would only make sense if you could
specify a substitution string with more than one character --
however we do not support that.

show more ...

Fix Bug #75001: Wrong reflection on mb_eregi_replace

Fix use after free in mb_send_mail

Remove superfluous allocation checks around ZMM-based functions

Drop unnecessary allocator return value checks

Deprecate mbstring.func_overload

Deprecate mb_parse_str() without second argument

Update copyright headers to 2017

Update copyright headers to 2017

Update copyright headers to 2017

Removed IS_TYPE_IMMUTABLE (it's the same as COPYABLE & !REFCOUED)