[Mono-bugs] [Bug 58844][Nor] Changed - InvokeMember with 'InvokeMethod | GetField' fails to find field

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sat, 22 May 2004 04:38: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 timsuth@ihug.co.nz.


--- shadow/58844	2004-05-22 04:25:03.000000000 -0400
+++ shadow/58844.tmp.9581	2004-05-22 04:38:32.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 58844
 Product: Mono: Class Libraries
 Version: unspecified
+OS: unknown
 OS Details: 
 Status: NEW   
+Severity: Unknown
 Priority: Normal
 Component: CORLIB
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: timsuth@ihug.co.nz               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -30,6 +30,20 @@
 Tested on Mono
 ------- Additional Comments From timsuth@ihug.co.nz  2004-05-22 04:25 -------
 Created an attachment (id=7791)
 Program that gets MissingMethodException
+------- Additional Comments From timsuth@ihug.co.nz  2004-05-22 04:38 -------
+I should also mention that InvokeMember finds the field in Microsoft's
+implementation. (I haven't tested the exact attachment I've posted
+here, but I've previously tested similar code.)
+Being able to specify that the thing you are invoking is either a
+method, field or property is useful in my case because I have written
+a library which allows Ruby code to use .NET libraries, and Ruby
+doesn't differentiate between methods, fields and properties. (So when
+I have Ruby code "foo.Something", I don't know what Something will be.
+Of course, I could try method and then catch the exception.)
+(I don't know what the ECMA specification says, sorry.)