HTTP/1.1 -1 Read error in cache disk data: SuccessContent-Type: text/tab-separated-values; charset="utf-8" Last-Modified: Sat, 22 Jan 2022 02:58:54 GMT Content-length: 1185 Connection: Close Proxy-Connection: Close X-Cache: HIT from web1.osuosl.org Server: ProxyTrack 0.5 (HTTrack 3.49.2) id summary reporter owner description type status priority milestone component version severity resolution keywords cc lang patch platform 414 [BUG] t/codingstd/c_cppcomments.t reports spurious error at hyperlinks jkeenan "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$ $ =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. }}}" bug closed minor docs trunk low fixed cpp codingstd newbie all me/common/css/report.css" type="te