in reply to Re: Weird bug with qr// and named capture buffers? Or just me?
in thread Weird bug with qr// and named capture buffers? Or just me?

Oh! I see, it makes sense. The perlop page says that if you use the options on the qr// and then interpolate the variable on a bigger string on the m// , the options (msi....) get set for the whole thing too.

But it makes sense as you say, that if m wasnt specified when using the qr//, the resulting compiled regex will not "accept" it later at the m//

So yes, it is my fault and trivial - even if a bit obscure, it should have dawned to me before. It is "compiled", after all :-) Thanks!

  • Comment on Re^2: Weird bug with qr// and named capture buffers? Or just me?

Replies are listed 'Best First'.
Re^3: Weird bug with qr// and named capture buffers? Or just me?
by ikegami (Patriarch) on Jun 18, 2008 at 14:21 UTC
    I'll let the developers know about the bad docs.