[Mono-bugs] [Bug 43687][Nor] Changed - incorrect code when using null where a pointer is expected

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
Fri, 4 Jul 2003 18:51:10 -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 miguel@ximian.com.


--- shadow/43687	Tue May 27 04:46:42 2003
+++ shadow/43687.tmp.11573	Fri Jul  4 18:51:10 2003
@@ -1,13 +1,13 @@
 Bug#: 43687
 Product: Mono/MCS
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: NEW   
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Normal
 Component: Misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: miguel@ximian.com               
 QAContact: mono-bugs@ximian.com
@@ -46,6 +46,9 @@
 instead of the broken ldnull mcs produces.
 I would also hope that kind of code to be removed from our sources,
 since it is exceptionally ugly: using IntPtr as the argument type and
 IntPtr.Zero instead of null would make for cleaner code and not
 require the use of /unsafe.
+------- Additional Comments From miguel@ximian.com  2003-07-04 18:51 -------
+Fixed on CVS.