> > Given how muddy the waters already are IMO this type of breakage is > > only of interest to golfers. And is likely to involve only a mere > > handful of scripts who probably aren't going to upgrade anyway. Anyone > > sane puts a space after a regex and its modifiers anyway IMO. That is not an argument I can accept. The "nobody sane would do this" strawman is a great way to get a kneejerk reaction out of me. > > And I will note that the introduction of /p was achieved without > > anyone reporting any problems like this. > > And in fact historically we DID have IMO a more worrying construct > added, and I suspect it also was harmless. I speak specifically of the > /x modifier. "We did it wrong before and nobody freaked out" is the same sort of thing. Neither of those arguments suggest that this is a case when we should break backward compatibility gratuitously. We may well be unable to do this cleanly and sanely. But that's a very different sort of argument. -JesseThread Previous | Thread Next