[Mono-bugs] [Bug 51506][Wis] Changed - System.Environment.TickCount should only return nonnegative values

[bugzilla-daemon@bugzilla.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 gonzalo@ximian.com.

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

--- shadow/51506	2003-11-30 02:39:18.000000000 -0500
+++ shadow/51506.tmp.4343	2003-11-30 11:57:59.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 51506
 Product: Mono/MCS
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Wishlist
 Component: Misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: mass@akuma.org               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -24,6 +24,10 @@
 only be negative half the time, changing every 25 days.
 
 also per the MSDN documentation, the value "overflows to zero", I suspect
 this ambiguous statement means that the high bit is just always clear and
 the # wraps at 24.8 days, not that between 25 and 50 days after reboot the
 value returned is always zero.
+
+------- Additional Comments From gonzalo@ximian.com  2003-11-30 11:57 -------
+It's easy to reproduce. Just get the piece of code in TickCounts and
+return the values you thing are wrong after casting them to uint.