[Mono-devel-list] Re: Fixes to XSLT
andrews at mainsoft.com
Tue Feb 8 07:39:20 EST 2005
Atsushi Eno wrote:
>> Class1.cs catches all the exceptions and prints the text of them into
>> the results file, if I understand correct your question.
> Then, it should have been reported as differences, but I could not
> find that specific test case.
Yes, I fished this example from the diff. How did you search this
specific test case?
> There is no "catalog.xml" in testsuite/TESTS/MSFT_Conformance_Tests
> in that OASIS test archive, unless I am specially filtered ;-)
> catalog.xml is only in testsuite/TESTS/Xalan_Conformance_Tests in
> that archive, but I don't know if there used to be catalog.xml in
> MS test dir in their old archives. In short, am afraid that you have
> possiblly older archive.
If you download this zip:
there is catalog.xml in testsuite/TESTS directory. That's the one I used.
> BTW it would be very nice if you split the patches per individual
> problem you fixed. Also, "svn diff" format would be better.
Hmm, I used diff -Naur to produce a patch. What's the way to make a
patch in "svn diff" format?
> What I am really afraid is that the bug will result in incorrect
> listing (as I wrote in MSDN feedback) of the enum type on reflection
> based code editor like MonoDevelop. It is clear and present danger.
Hm, MonoDevelop then has to solve this problem somehow. What will happen
if a user defines her own enum where few members have an equal value?
Then you must go further and forbid such enum members in the language
like you forbid duplicated cases in switch statement.
More information about the Mono-devel-list