[Mono-bugs] [Bug 79312][Nor] Changed - returning a struct by value giving unexpected results

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Sep 8 14:51:52 EDT 2006


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 james.eberle at comcast.net.

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

--- shadow/79312	2006-09-08 06:16:18.000000000 -0400
+++ shadow/79312.tmp.12747	2006-09-08 14:51:52.000000000 -0400
@@ -418,6 +418,23 @@
 it should eventually (and perhaps you can help implement it if desired ;-)
 
 ------- Additional Comments From vargaz at gmail.com  2006-09-08 06:16 -------
 It is possible that this is caused by a bug in the PPC JIT, i.e.
 it does not support returning vtypes in registers.
 
+
+------- Additional Comments From james.eberle at comcast.net  2006-09-08 14:51 -------
+I took a look at the SafeHandle class. As I'm just starting out w/
+Mono, I'm probably not the best person to tackle it! Looks pretty
+involved.
+
+Call it minimalism, but I think the best solution to this problem
+(IMHO) is the ability to define enums as intptrs. So:
+
+enum EventLoopRef : intptr {}
+
+This way you get type-checking, clear marshaling semantics, and clear
+object behavior (it isn't one).
+
+Of course "intptr" is not a C# type, so this suggestion is a long ways
+off.
+


More information about the mono-bugs mailing list