Jeffrey Friedl writes: > When it comes to these not-yet-existant tools, I'm worse than a novice > because I don't even have them at my disposal to play with. That no one has > been able to use them is not a reason to not consider them. FWIW, it took me ages to sort out the cut in 5.6 REs because I was expecting it to abort bumpalong. I'd support a bumpalong-cutting cut. The counter-argument is that every time we permit finer control over the behaviour of the RE engine, we remove freedom to reimplement and improve that engine. Already we have seemingly bizarre things: "hello, world" =~ /(.)(?{ print $1 })o/; Naively you'd think it'd print hel showing the RE engine trying those places, until (.) matched 'l' and o matched 'o'. But the fixed-string optimization causes it to jump straight to the 'l' and immediately match. The more we think we're writing programs for the RE engine, the more we risk having those programs perturbed by optimizations. Each new RE engine feature must be weighed and balanced. NatThread Previous | Thread Next