MaXML 2.0 Released!

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.

John J.

skidracer: You're right - adding a pointer to the xmlDocument seems to fix it. But there's something I don't understand - how is the garbage collector deleting something before the program is done with it? Isn't it supposed to check if there are any references to an object before deleting it? (and therefore removing the possibility of the garbace collector deleting an object before the program is done with it like what has happened here)?

Update: Version 2.19 will hopefully fix any problems related to debug/release inconsistancies.