[Mono-bugs] [Bug 32336][Wis] Changed - We are using callvirt on the closest method, rather than the defining method

[bugzilla-daemon@rocky.ximian.com]

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 miguel@ximian.com.

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

--- shadow/32336	Wed Oct 16 00:28:37 2002
+++ shadow/32336.tmp.27762	Wed Oct 16 00:31:12 2002
@@ -10,13 +10,13 @@
 Component: Misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: vladimir@pobox.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
-Summary: base.* doesn't work for properties
+Summary: We are using callvirt on the closest method, rather than the defining method
 
 /* t16.cs */
 using System;
 
 public class FooBase {
     int i;
@@ -85,6 +85,12 @@
 problem:  The MS compiler generates a callvirt in main to FooBase.Frob, 
 and we are generating a callvirt to Foo.Frob.
 
 I do not know if this has side effects though.
 
 CCing Paolo to get his opinion.
+
+------- Additional Comments From miguel@ximian.com  2002-10-16 00:31 -------
+Btw, in the past we thought that .NET created a method signature for
+the parent, but this gives me the impression that we were wrong
+before.  We do not need the parent, we need the method that introduced
+the definition.