[Moose-dev] Re: Binary import/export in Moose

On Wed, Jan 5, 2011 at 11:15 AM, Simon Denier <simon.denier(a)gmail.com>wrote;wrote: I don't know if it is possible in Fuel, but others serializers outside Smalltalk does that. We can do it at class level or at instance level. I think Fuel can provide that classes implement a class side method #isFuelSerializable The we can implement: Object >> isFuelSerializable ^ true And override for those classes that are yet not supported by Fuel, suppose, Class. THen: Class >> isFuelSerializable ^ false Notice that this is not a programmer choice, but Fuel limitations/decisions. If you try to serialize an instance of any of those classes, you should rise NotSerializableError or something like that. At the same time, we can provide a feature so users can provide what to serialize. Fuel can implement the default: Object >> isFuelTransient ^ false and for those particular classes that you DO NOT want to seriaize, you can implement this way: MyClass >> isFuelTransient ^ true That's at class level. Going to instance level is a little complicated since we don't have the kind of Java definition. But we can implement a class side message that answers the name of the instVa that should be transient. Example: Object >> fuelTransientInstanceVariables ^ () MyOtherClas >> fuelTransientInstanceVariables ^ ( 'name' 'age') blah.... or something like that. What I think it is important is being able to mark transient stuff and non-serializable stuff too. Cheers Mariano