demerphq wrote: >First, the problem of qr// raises its head. You construct a pattern >one context with your new pragma in effect, and then embed it in >another pattern somewhere else and the magicness of the pattern is >lost. Or vice versa, of course. This means that for a pattern to be freely embeddable you need to avoid all the constructs whose behaviour depend on the pragma. This is no worse than the current situation, where you need to avoid those constructs because they're broken, but for that class of situation it's no better either. And how many people are actually going to think about the pragma when they write their exportable regexps? The existence of a pragma with this class of effects is a problem. I also don't think we should be supporting buggy behaviour by any mechanism. The old behaviour isn't just legacy, it's a bug, and any code that invokes it is buggy. Please just fix the bug, don't bless it. -zeframThread Previous