Minor bug in regex used in match_comp_content_call_end (Lexer.pm)?

Alex Robinson <[email protected]> Thu, 18 Oct 2007 19:43:45 +0100
Newsgroups gmane.comp.web.mason.devel
Message-ID <p06230906c33d569ef549@[192.168.6.105]>
I think I found a very minor bug in Lexer.pm

match_comp_content_call_end, line 453
>>>>
     if ( $self->{current}{comp_source} =~ m,\G</&(.*?)>,gc )
<<<<

Shouldn't the modifier flags be 'gcs' as is the case with 
match_comp_content_call?


Currently, the following causes a compilation error

====================================================
<&|
Wrap
&>
Hello
</&
Wrap
>
Goodbye

<%def Wrap>
[Wrap start] <% $m->content %> [Wrap end]
</%def>
====================================================

But I'm assuming the fact that the opening component with content 
call can be broken on to multiple lines and that 
match_comp_content_call_end attempts to do a tr on the content of the 
matched end call for the line count means that it shouldn't...

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/