Re: [Ironruby-core] IronRuby's Marshal.dump doesn't work with CLR types, or ruby types backed by a CLR type

2011-10-25 Thread Orion Edwards
For dealing with Clr-backed objects such as Exception should we just create special cases in the Marshal to dump and load them? Is there any way I can find out what other ruby objects are actually CLR objects other than Exception types and the basic int, double, float types? My experiments with

Re: [Ironruby-core] IronRuby's Marshal.dump doesn't work with CLR types, or ruby types backed by a CLR type

2011-10-25 Thread Tomas Matousek
I think we should NOT serialize non-Ruby types for now. The implementation isn't quite working so I'd prefer we delete all code that deals with ISerializable, clean up the marshaller and if .NET serialization is needed in future implement it fully and correctly. Marshal.dump has to output exact

[Ironruby-core] IronRuby's Marshal.dump doesn't work with CLR types, or ruby types backed by a CLR type

2011-10-25 Thread Orion Edwards
Backstory: I'm trying to use DRb for some in-house utility code. DRb itself seems to work fine, but I found that when I misspelled a method name, instead of reporting back a NoMethodError, the IronRuby process crashed immediately to the console. This is using a relatively recent build of IronRu