go to bug id or search bugs for
The chr function translate a single Byte length integer into it's ASCII value.
When providing a number bigger then 255, it returns the first byte instead of reporting an error about being out of range.
echo chr(1000) . ' ' . ord(chr(1000)) . "\n";
chr must check the numeric boundaries and report on on an error when they are out of the range.
returns the first byte out of the result, making it appear like an integer overflow that the carry flag exception was captured.
Add a Patch
Add a Pull Request
I think this check could be done in user script self.
the document said:
chr convert *ascii* code .. so...
ASCII is 0..127 chars, if they are out of range and also from extended ASCII (128..255), then you must report an error like with normal implementation such as Ruby, Python, Pascal, Perl (with strict bytes) etc...
Not to $value & 255 it.
It seems to be appropriate to point out why this ticket had been
changed to feature request. :)
> Not to $value & 255 it.
Actually, the integer is simply cast to char and used as the first
and only byte of the returned string.
Of course, this behavior is questionable, but changing it would
cause a BC break, so it can't be done in a minor version or even a
patch release without a very good reason. Simply stating "you must
report an error like XYZ" is not a very good reason, in my
opinion. I'd rather fix the docs and maybe change the behavior in
the next major version.
Automatic comment from SVN on behalf of cmb
Log: Address #63510: Integer overflow with chr
Should we close this bug? I'm fine with documentation change.
chr() may have strict option that detects overflow, also.
string chr(long $code [, bool $strict=FALSE])
BTW, we'll have mb_chr()/mb_ord() from PHP 7.2
Merge: 4a3188f 15e32fd
Author: Yasuo Ohgaki <email@example.com>
Date: Wed Aug 10 09:47:27 2016 +0900
Request #65081 mb_chr() and mb_ord()