I think that a bitset array is not going to be an integral type in RELOAD. Instead, it will be a blob with a couple wrapper functions:
GetBitsetBit(Node as Nodeptr, bit as integer) as integer SetBitsetBit(Node as Nodeptr, bit as integer, v as integer) Maybe one to spawn a bitset from an existing integer array. The bitset functions would automagically manage the size by growing the blob as necessary. ------Original Message------ From: Mike Caron To: OHR List Subject: Re: [Ohrrpgce] reload wishlist: bitset array Sent: May 14, 2010 3:56 PM On 14/05/2010 3:51 PM, James Paige wrote: > I am on the verge of starting the new save format, and I am thinking > about how to store tags. > > I could store them as a bunch of named integer tags that could be 0 or > 1. > > I could store them as a bunch of named tags which either exist or don't > exist. > > I could store them as a bunch of 16 bit ints, exactly like their > internal representation in-memory in the tag() array. > > I could nicely ask Mike to implement a bitset data type ;) > (or I could do it myself, I guess) Hmm. I think the pragmatic approach would be the named tags. (<tag1/>, <tag2/>, etc). However, I can see how having thousands of unique tags may be a problem :) Give me an hour or two, and I'll start working on this... > --- > James > _______________________________________________ > Ohrrpgce mailing list > [email protected] > http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org -- Mike -- Mike Caron _______________________________________________ Ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
