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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=80240 --- shadow/80240 2006-12-12 12:49:33.000000000 -0500 +++ shadow/80240.tmp.26570 2006-12-12 20:03:57.000000000 -0500 @@ -76,6 +76,17 @@ ------- Additional Comments From [EMAIL PROTECTED] 2006-12-12 12:49 ------- You know you can't depend on the internal representation of DateTime, right? You should get date.Ticks and pass the 64 bit integer, then with the returned value create a new DateTime. Your code is bound to break with the MS runtime, too, sooner or later. + +------- Additional Comments From [EMAIL PROTECTED] 2006-12-12 20:03 ------- +Paolo, + +I don't think your comments are relevant to the code I'm using as I'm +not using any internal represention of System.DateTime. I'll post the +code shortly and then you can see. All the modifications to the +DateTime object are being done in the managed world, using the +official DateTime api. What I am doing is passing the DateTime +instance between the managed and unmanaged world as a managed ref type +which is just an unmanaged void * pointer on the managed side. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
