Re^3: differences between parsing qr, qq, and q string contents

So, it's ok to pay a price each and every time code is compiled, just so *debugging* during development may become easier? It also means you're paying the price if you do know your patterns, and write them correct the first time.

It's a very small price to pay.

And it's not a price at all if you're using mod_perl and so compile time is not a consideration.

And if it is a price, then just change your qr{}'s to qq{}'s and done.

Comment on Re^3: differences between parsing qr, qq, and q string contents

Replies are listed 'Best First'.
Re^4: differences between parsing qr, qq, and q string contents by JavaFan (Canon) on May 02, 2011 at 09:16 UTC
It's a very small price to pay. I've already indicated that my experience that sometimes, the price isn't small. And if it is a price, then just change your qr{}'s to qq{}'s and done. That isn't so easy. Changing `qr{$foo\d}` to `qq{$foo\d}` isn't going to work. But if it's so easy, you could start with `qq{}`, and change to `qr{}` only if you cannot debug your errors. Which would require no changes if you did things correctly the first time.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^4: differences between parsing qr, qq, and q string contents
by JavaFan (Canon) on May 02, 2011 at 09:16 UTC

It's a very small price to pay.

And if it is a price, then just change your qr{}'s to qq{}'s and done.

qr{$foo\d}

qq{$foo\d}

But if it's so easy, you could start with qq{}, and change to qr{} only if you cannot debug your errors. Which would require no changes if you did things correctly the first time.

[reply]
[d/l]
[select]