optimize persistence?

BlitzMax Modules Forums/Brucey's Modules/optimize persistence?

The forum is locked. These are the original blitzbasic.com forums, kept so they can still be read. No new topics, replies or edits can be made here. To join in, head over to the Blitz3D+ forums.

Fixed a bug with serializing TMap - some nodes refer to a private "nil" global node, which wasn't de-serializing to point to the current nil node object. This could cause issues when using the TMap after loading.


Which is a bit of a bugger really. Don't really want to add type-specific handling to this, but in some cases there's not much I can do about it.
I suppose a preferred option would be to have some kind of pluggable interface where Joe Coder would be able to add his own type-handling for special cases... which all seems a wee bit over-the-top for a simple object persistence module. argh...