[Mono-bugs] [Bug 55909][Wis] Changed - Deadlock in ReaderWriterLock.UpgradeToWriterLock()

[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 mono-bug@jerryweb.info.

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

--- shadow/55909	2004-04-13 07:37:59.000000000 -0400
+++ shadow/55909.tmp.3325	2004-04-13 17:07:10.000000000 -0400
@@ -332,6 +332,21 @@
 implementation fixes your bugs, but are you sure that it does not
 break anything else that works with the current implementation? At
 least, two unit tests are failing with your class.
 
 In any case, thanks for your interest. Please, keep reporting.
 
+
+------- Additional Comments From mono-bug@jerryweb.info  2004-04-13 17:07 -------
+OK :). Simply, I was in urgent need to have the ReadWriterLock class
+working, for my own project; and because it showed impossible for me
+to force it to work I voted to spent a half day and to write my own
+code. It was quicker, in that moment. And on condition that the class
+was written - why not to offer it to you? ;)
+BTW, if it is not troubling you, I would be fruitful for me to know
+what unit tests are failing with my code, just to learn about my bugs
+(I was correcting the code for a few times).
+(Generally, your statement that in general it is a better approach to
+fix bugs on anexisting implementation rather than rewriting it, as far
+as the
+existing implementation is based in a correct design and do not have
+major flaws is, naturally, correct and valid.)