[Mono-bugs] [Bug 665144] New: Consider not generating a AvoidRefAndOutParametersRule defect when the method implements a BCL interface

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=665144

https://bugzilla.novell.com/show_bug.cgi?id=665144#c0


           Summary: Consider not generating a AvoidRefAndOutParametersRule
                    defect when the method implements a BCL interface
    Classification: Mono
           Product: Mono: Tools
           Version: 2.10.x
          Platform: 64bit
        OS/Version: Windows 7
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: Gendarme
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: ethan_j_brown at hotmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US)
AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.634.0 Safari/534.16

AvoidRefAndOutParametersRule is a good rule.  However, there are times when
there is no choice but to implement an interface the .NET framework designers
established.

A simple example is System.ServiceModel.Dispatcher.IErrorHandler
http://msdn.microsoft.com/en-us/library/system.servicemodel.dispatcher.ierrorhandler.aspx

There are many instances where ref parameters are used in WCF.

I propose that no defects are generated when the class is implementing
interfaces defined in the BCL.

Reproducible: Always

Steps to Reproduce:
1. Implement a framework interface that uses out or ref parameters.
2.
3.
Actual Results:  
A AvoidRefAndOutParametersRule defect is generated.

Expected Results:  
No defect.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.