Forum: IronRuby Fix for issue #4946

Posted by Charles Strahan (charles-strahan)
on 2010-08-27 23:00
(Received via mailing list)
Here's my fix for issue #4946 
<http://ironruby.codeplex.com/workitem/4946>:
da1abbdba748f0ebdb52<http://github.com/cstrahan/ironruby/commit/da1abbdba748f0ebdb5282f8557549bf260ffd61>

However, I'm curious if that's just sidestepping another problem with 
the
Silverlight build.  Before the change, CreateObject will always raise an
exception in Silverlight if the baseType implements ISerializable - 
after
the change, it won't throw when the baseType is RubyObject.  Shouldn't
we *always
*ignore the ISerializable attribute in the Silverlight build and instead
default to the second part of the if/else (the part where we use 
*theclass**
.Context.SetInstanceVariable*)?

-Charles
Please log in before posting. Registration is free and takes only a minute.
Existing account (Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
No account? Register here.