Re: [Parseperl-discuss] New Perl::Critic policies

[Chris D. <ch...@cl...>]

Peter,

Thanks for the report.  Those are now fixed in PPI SVN revision  
1054.  Amusingly, *= and /= were two unrelated bugs.

Chris

On Sep 21, 2006, at 11:18 AM, Peter Guzis wrote:

> Hello Chris,
>
> PPI doesn't properly parse some multi-character operators such as  
> *= and /=, even though the POD says these are supported.  Instead,  
> the aforementioned operators are recognized separately as *, =, /,  
> and =.
>
> I got the policy working with a very simple fix, so I did not  
> submit another PPI bug report. My workaround was to concatenate  
> adjacent operators ( e.g. *, =) and skip processing the second  
> operator (=) separately. If you want to fix PPI instead, that would  
> be an even better solution.
>
> Let me know if you need more information.
>
> Thanks,
>
> Peter
>
> On 9/21/06, Chris Dolan <ch...@cl... > wrote:
> Hey Peter,
>
> I was just looking over the ProhibitMismatchedOperators policy and
> saw these lines:
>
>      # work around PPI operator parsing bugs
>
>      return if $prev_elem->isa('PPI::Token::Operator');
>
> What's that all about?  Anything I can try to fix?
>
> Chris
>

-- 
Chris Dolan, Software Developer, Clotho Advanced Media Inc.
608-294-7900, fax 294-7025, 1435 E Main St, Madison WI 53703
vCard: http://www.chrisdolan.net/ChrisDolan.vcf

Clotho Advanced Media, Inc. - Creators of MediaLandscape Software  
(http://www.media-landscape.com/) and partners in the revolutionary  
Croquet project (http://www.opencroquet.org/)