Search pattern not terminated
in [Perl]
|
From: jidanni on 8 May 2010 23:12 Is this really a search pattern, or do they need a better error message about the typo of $++m for ++$m? $ perl -we '$r=$++m' Search pattern not terminated at -e line 1.
From: Uri Guttman on 8 May 2010 23:27 >>>>> "j" == jidanni <jidanni(a)jidanni.org> writes: j> Is this really a search pattern, or do they need a better error message j> about the typo of $++m for ++$m? j> $ perl -we '$r=$++m' j> Search pattern not terminated at -e line 1. that is parsed as $+ + m the m starts an m// regex but it never finds the terminator. hell, it should have even found the starting delimiter. uri -- Uri Guttman ------ uri(a)stemsystems.com -------- http://www.sysarch.com -- ----- Perl Code Review , Architecture, Development, Training, Support ------ --------- Gourmet Hot Cocoa Mix ---- http://bestfriendscocoa.com ---------
From: C.DeRykus on 9 May 2010 07:19 On May 8, 8:27 pm, "Uri Guttman" <u...(a)StemSystems.com> wrote: > >>>>> "j" == jidanni <jida...(a)jidanni.org> writes: > > j> Is this really a search pattern, or do they need a better error message > j> about the typo of $++m for ++$m? > > j> $ perl -we '$r=$++m' > j> Search pattern not terminated at -e line 1. > > that is parsed as $+ + m > > the m starts an m// regex but it never finds the terminator. hell, it > should have even found the starting delimiter. Search pattern not terminated at -e line 1 (#1) (F) The lexer couldn't find the final delimiter of a // or m{} construct. Remember that bracketing delimiters count nesting level. Missing the leading $ from a variable $m may cause this error. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^.... Looks like this latter scenario triggered the error since the lexer didn't find a starting delimiter for m{}. -- Charles DeRykus
|
Pages: 1 Prev: FAQ 5.21 How can I lock a file? Next: interesting perl question |