[Mono-bugs] [Bug 697296] gmcs generates incorrect //member/@name value for arrays of arrays

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=697296

https://bugzilla.novell.com/show_bug.cgi?id=697296#c4


Jonathan Pryor <jonpryor at vt.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FEATURE                     |

--- Comment #4 from Jonathan Pryor <jonpryor at vt.edu> 2011-06-01 19:00:32 UTC ---
After following up with Pilchie (developer in Visual Studio) on
##csharp/irc.freenode.net, here's what happened.

Someone filed
http://fairyengine.blogspot.com/2011/05/android-experiment-porting-my-xna-game.html
.

In someone else's infinite wisdom, Microsoft decided to fix that for CSC 4.0,
thus "departing" from CSC <= 3.5 behavior.

After further testing, CSC 4.0 _also_ departed from VB.NET 10 and C++/CLI 16 --
VB.NET and C++/CLI generate XML member references as CSC 3.5 did, not as CSC
4.0 does.

Finally:

14:53 <Pilchie> jonp: okay - bug filed to have the next compiler revert back to
what 3.5 did.

So the next CSC version will revert to the CSC 3.5 behavior instead of
continuing current 4.0 behavior.

Consequently, could dmcs now follow CSC 3.5 behavior for array + XML member
generation? It's The Right Thing To Do™.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.