I'm working on a system of plug-ins where I'm going to have interpreted bytecode stored in a database "module", but now I'm exploring storing the same thing in a resource database format as an alternative. The main reason for that is expandability of the database... instead of bumping up the version number for the database when I add something to the system and having the interpreter change the offsets of where to look for things in that database, I just add a resource type and add code to the interpreter to deal without it if that new resource isn't there. That way, the code that determines where to look for what doesn't have to change.
My question is this... is there any additional overhead (as far as dynamic memory consumed) for a resource database as opposed to a regular database? Thanks. ----------------------------------------------------------------------- Brian Smith // avalon73 at arthurian dot nu // http://www.arthurian.nu/ Software Developer // Gamer // Webmaster // System Administrator In the beginning there was nothing. And the Lord said, "Let there be Light!" And there was still nothing. But you could see it. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
