Hi Andrea,
Le 23/01/2016 22:10, Andrea Faulds a écrit :
Er, ignore what I just said. Negative string offsets are actually
special-cased and always produce an "Unitialized string offset" or
"Invalid string offset" notice. So our current behaviour is in fact
completely useless, not just mostly. :)
Thanks for your comments. Following your suggestion, I just added some examples of negative offset usage.
About BC breaks, the RFC just adds support for currently-invalid values. In every cases, these values would have generated a notice or a warning, and the value would have been considered as zero. So, I consider these BC breaks as minor because of error messages. But determining if such BC breaks are compatible with a minor release will be the main objective of the vote.
Regards
François