#414: [BUG] t/codingstd/c_cppcomments.t reports spurious error at hyperlinks
---------------------+------------------------------------------------------
 Reporter:  jkeenan  |       Owner:               
     Type:  bug      |      Status:  new          
 Priority:  minor    |   Milestone:               
Component:  docs     |     Version:  trunk        
 Severity:  low      |    Keywords:  cpp codingstd
     Lang:           |       Patch:               
 Platform:  all      |  
---------------------+------------------------------------------------------
 The ''c_cppcomments.t'' coding standards test is supposed to detect usage
 of C++-style comments.  Unfortunately, the double forward slashes of such
 comments are also found in hyperlinks that may reasonably appear in POD
 inside C-ish files.

 Suppose we had a file like this named ''some.ops'':
 {{{
 /*$
  * $Id: experimental.ops 37191 2009-03-08 02:37:10Z coke $$
 ** some.ops$
 */$
 $
 VERSION = PARROT_VERSION;$
 $
 =head1 NAME$
 $
 experimental.ops - Experimental Opcodes$
 L<https://trac.parrot.org>$
 $
 =cut$
 }}}
 ... and then we called:
 {{{
    $ perl t/codingstd/c_cppcomments.t some.ops
 }}}
 ... we would get:
 {{{
 1..1
 not ok 1 - no c++ comments
 #   Failed test 'no c++ comments'
 #   at t/codingstd/c_cppcomments.t line 45.
 # C++ comments found in the following files:
 # some.ops
 # That's 1 failed files out of 1 files total.
 # Looks like you failed 1 test of 1.
 }}}

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/414>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to