Skip to content

Conversation

@nielsdos
Copy link
Member

@nielsdos nielsdos commented Jul 8, 2025

This restores the old behaviour.

Copy link
Member

@remicollet remicollet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, old behaviour restored

@remicollet
Copy link
Member

remicollet commented Jul 9, 2025

An alternative way (to follow strictly doc) will be to accept int|string|null for 1st param, and only string for others, but this is probably a BC break.

So this PR seems the right fix.

Thanks for the quick fix

@nielsdos
Copy link
Member Author

An alternative way (to follow strictly doc) will be to accept int|string|null for 1st param, and only string for others, but this is probably a BC break.

Yes I think so as well, since we allowed [null] to behave the same way.
Thanks for checking.

@nielsdos nielsdos closed this in c4183fb Jul 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

setlocale($type, NULL) should not be deprecated

2 participants