Looks like the internal bug got closed as By Design as well, I've reactivated
it. Maybe it's not clear to them that their making a distinction based upon
what assembly the struct is defined in. I added the below repro snippet to the
internal bug:
using System;
using System.Reflection;
class foo {
public void bar(out ParameterModifier x) {
}
}
vs:
using System;
class foo {
public void bar(out ParameterModifier x) {
}
}
// ParameterModifier from mscorlib has the same members:
struct ParameterModifier
{
private bool[] _byRef;
}
The 1st doesn't require assignment yet the 2nd does.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sanghyeon Seo
Sent: Wednesday, October 17, 2007 6:58 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Compilation error
2007/10/6, Dino Viehland <[EMAIL PROTECTED]>:
> BTW my simple repro is bogus - it contains no members and section 5.3 of the
> C# spec defines value types as being definitely assigned when all their
> members are assigned. The real issue seems to be when the value-type is
> defined in another assembly and all the members are private. Once those
> conditions are met csc then doesn't require the assignment.
>
> I'm still waiting for a response on that last bit.
Gert Driesen from Mono project reported this as Feedback 304489 at
Microsoft Connect.
http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=304489
After 3 days, it was marked "Resolved (By Design)", without any
explanation. I'm still curious.
--
Seo Sanghyeon
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
