Re: PHP6 artifact - binary strings

Hi, > On 8 Feb 2015, at 21:48, Marc Bennewitz <dev@mabe.berlin> wrote: > > Wrapping all in objects isn't an option. This would only add unnecessary overhead and only > move the issue to a different place. I don’t see why not. Objects are generally exempt from type juggling, except for conversion to strings. Surely that’s what you want? >> This would break existing code which was made “PHP 6-ready”. > I don't think so. If a string was declared as binary it should be binary else it is a > wrong declaration and a bug. It already is binary, though. PHP’s strings are binary, they always have been. The reason that we have (binary) is because PHP 6 was going to make (string) a synonym of (unicode) instead. >> Also, we already support bitwise operations on strings, I don’t know what you’re on >> about there... > > Sorry I wasn't clear. > I mean the bitwise shift operators see http://3v4l.org/MBadR That would be a BC break, and the kind of non-obvious evil one Derick doesn’t like much. Though I can’t talk: I already ‘broke’ bitwise shifts with the Integer Semantics RFC. -- Andrea Faulds http://ajf.me/