ISerializable interface #2
Replies: 1 comment 3 replies
-
|
FWIW I've wondered about exactly the same thing with stdVBA. My conclusion was that the dependency wasn't worth it, and an IDispatch based standard made more sense for serialisables. For instance if I wanted to use this library and stdVBA I'd then need to implement said interface on all stdVBA classes I wanted to serialise... I'm really torn on this. I think more generally a It should also be noted that interfaces are not compatible between projects.(In the sense that |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Interface
ISerializable:In advance of the serializer, should this library allow objects that are not
CollectionorDictionary?This would require the above interface and basically each such object is responsible to
Implement ISerializableand to return aDictionaryinstance via thePrivate ISerializable_GetData() As Dictionaryimplemented method. The upcomingSerializermethod would then serialize the returnedDictionary.The benefits are obvious, however this will add the extra class to all users codebases, even if not used.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions