jakarta-oro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel F. Savarese" <...@savarese.org>
Subject Re: [Bug 1346] Changed - substitue gives strange result
Date Fri, 27 Apr 2001 20:25:49 GMT

Sorry for hitting three lists, but it's the only way to root out the
culprit.

Who changed the status of this bug (the one at the end of this message)
to VERIFIED?  Why weren't any comments added?  Unless someone points out
the capturing parentheses in the expression (all appear to be non-capturing)
and addresses my previous comment about the alleged bug and the behavior of
Perl 5.003 capturing parentheses, I am going to change the status back to
RESOLVED and INVALID.  You can't just change the status of a bug without
providing any explanation whatsoever.

First, confirm that there are some capturing parentheses
and point them out.  I can't find any, but the expression is so long maybe
I missed something, but I did in fact use a regular expression to search
for a non-capturing open parenthesis in the expression and could not find one.
Second confirm that the behavior of the substitution is different from that
of Perl 5.003 (not 5.004, 5.005, 5.6 or anything else).  Finally, if there
really is a discrepancy, change the status to verified and provide a full
explanation.  Otherwise there is NO way whatsoever to try to fix the problem
if it is a problem.

Also, is just anyone allowed to change the status of bug reports or
just committers?  Bug tracking is useless if the bug handlers don't
follow reasonable procedures.  Right now someone has changed a bug
from Status: RESOLVED Resolution: INVALID to Status: VERFIFIED
Resolution: INVALID.  At the very least, if you're not going to add
comments put the bug in a state that makes sense.  How can a bug be
both VERIFIED and INVALID?

If you're reading this and you changed the status of this bug please
go back and do the things I suggested and then change the status of
the bug report appropriately and add some helpful comments.  Also,
don't take my crankiness personally.  You'll surely get a chance to
reprimand me about something in the future.

Before I quiet down, I move that no bug report shall have its status
changed without a comment, just as no code change should be committed 
without a log message.

daniel

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1346

*** shadow/1346	Wed Apr 18 14:25:16 2001
--- shadow/1346.tmp.6409	Wed Apr 25 14:28:48 2001
***************
*** 2,8 ****
  | substitue gives strange result                                             
|
  +----------------------------------------------------------------------------
+
  |        Bug #: 1346                        Product: ORO                     
|
! |       Status: RESOLVED                    Version: 2.0.2                   
|
  |   Resolution: INVALID                    Platform: PC                      
|
  |     Severity: Normal                   OS/Version: Linux                   
|
  |     Priority: High                      Component: Main                    
|
--- 2,8 ----
  | substitue gives strange result                                             
|
  +----------------------------------------------------------------------------
+
  |        Bug #: 1346                        Product: ORO                     
|
! |       Status: VERIFIED                    Version: 2.0.2                   
|
  |   Resolution: INVALID                    Platform: PC                      
|
  |     Severity: Normal                   OS/Version: Linux                   
|
  |     Priority: High                      Component: Main                    
|




Mime
View raw message