forked from mono/mono
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[mdoc] Fix export-msxdoc regression, updated expected output.
Commit 44b2b4a completely broke `mdoc export-msxdoc` because EcmaDoc.GetCref() was removed. Expected: <member name="C:Mono.DocTest.DocAttribute(System.String)"> Actual: <member name="Mono.DocTest.DocAttribute..ctor"> i.e. useless. The fix: bring back GetCref(), this time within monodocs2slashdoc.cs. Commit 0ad6ffd changed the HTML-generating stylesheet and moved some @id attributes around, thus breaking the mdoc unit tests (expected output likewise changed). Fix the monodoc XSLTs so that we don't emit id="" attributes (id's with no value). Update mdoc's expected output so that tests pass[*]. [*]: tests will NOT actually pass, as 04bf9ad -- attempted fix for an OS X stackoverflow caused by 3d3fe6a -- results in a gigantic 216MB diff because String.get_Chars() is repeated over and over and over... The updated expected output in this commit is the "ideal" update needed after locally reverting 3d3fe6a and 04bf9ad.)
- Loading branch information
Showing
34 changed files
with
262 additions
and
219 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.