[Mono-bugs] [Bug 76685][Min] Changed - [/doc] XML doc does not support reference to indexer.

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon Nov 14 04:49:17 EST 2005


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 gert.driesen at pandora.be.

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

--- shadow/76685	2005-11-13 18:16:28.000000000 -0500
+++ shadow/76685.tmp.21294	2005-11-14 04:49:17.000000000 -0500
@@ -183,6 +183,42 @@
 
 Again, let me know if you want a separate bug report for this.
 
 ------- Additional Comments From atsushi at ximian.com  2005-11-13 18:16 -------
 The difference is nothing; there is NO reason that we must take int
 one instead of string one.
+
+------- Additional Comments From gert.driesen at pandora.be  2005-11-14 04:49 -------
+Including transcript of private email conversation (as requested by 
+Atsushi):
+
+==== Gert ====
+
+I'm not sure I understand your last remarks for this bug:
+
+"The difference is nothing; there is NO reason that we must take int 
+one
+instead of string one."
+
+I don't see why you say that there is no difference. The generated 
+doc will
+be different when built using mcs, as the cref will point to another
+overload.
+
+I ran into this as part of a (offline) test suite I have for catching
+regressions in Mono.
+
+Thanks for fixing the /doc bugs so fast !
+
+=== Atsushi ===
+
+There is no reason that /doc support must prefer this[int] over
+this[string] when cref just references "this", as long as it
+corresponds to what the warning message tells users. I return
+the first item from FindMembers(). It's like expecting ordered
+items from Hashtable. This is what we call implementation details.
+
+BTW it should be no problem that this talk goes on the bugzilla
+itself. Private talk contributes nothing to public.
+
+Oh, and also thanks for you too for filing many bugs, as usual.
+


More information about the mono-bugs mailing list