[Mono-bugs] [Bug 60524][Min] New - Finalize() is OK with "mcs" while is not OK with "csc" (Microsoft's)

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 22 Jun 2004 01:19:32 -0400 (EDT)


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by jimeno@servidor.unam.mx.

http://bugzilla.ximian.com/show_bug.cgi?id=60524

--- shadow/60524	2004-06-22 01:19:32.000000000 -0400
+++ shadow/60524.tmp.15977	2004-06-22 01:19:32.000000000 -0400
@@ -0,0 +1,60 @@
+Bug#: 60524
+Product: Mono: Compilers
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Minor
+Component: C#
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: jimeno@servidor.unam.mx               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Finalize() is OK with "mcs" while is not OK with "csc" (Microsoft's)
+
+Description of Problem:
+
+Ximian's mcs accepts a method called Finalize(), while Microsoft's csc
+refuses to compile the code and suggests to use a destructor (class name
+preceded by "~") instead.
+
+
+Steps to reproduce the problem:
+
+1. Compile the attached program using mcs.
+2. Watch the message "Compilation succeeded" as it appears on the screen.
+3. Comile the attached program using csc.
+4. Watch a message similar to "can't compile. use destructor instead"
+   as it appears on the screen
+
+
+Actual Results:
+
+Both compilers have "different oppinions" on what they consider to be
+compilable. ;-)
+
+
+Expected Results:
+
+Both compilers agreeing in what they consider to be compilable 
+
+
+How often does this happen? 
+
+Always.
+
+
+Additional Information:
+
+This report indicates a difference between the the behaviors of Microsoft's
+"csc" and Ximian's "mcs". It's not for me to tell whether it is a bug in 
+csc  or in  mcs  or maybe neither of them. I guess ECMA's specification
+should be checked thoroughly.
+
+Just another thing: If the correct behaviour ends up being to accept the
+Finalize() method, then I will file another bug since Finalize() should be
+"protected" or "private" but Mono accepts the method to be "public" instead.