1 email, 2 replies. > Thats just silly. It seems rather annoying to get. Rather, just > use an int array, that holds 1 or zero. Use short if your concerned about > space or something. But if you think about it, an int has the sizeof 4, > short 2, char spot is 1. So short isn't much more efficent than using a > char, if you want to use arrays.
Using an array of integer types where each integer represents a flag seems wasteful of memory. At any given time, I have roughly 15,000 flag lists allocated in my MUD, most of these holding around 40 flags. Using shorts to hold flags, this would be over 1 MB of memory just for flags. Using bits, it's around 30 KB of memory. > The reason she used character was listed she wanted a way to not changed the > existing structure of the files. > She also provided a solution which i think was a good thing she as > contributing. > I for one will not attack someone who gives back. I don't see how keeping forward compatibility with areas has anything to do with what integer type you use to store the flags. I agree giving back is a good thing, but I don't see any reason to look at it as an attack. If you tell me I did something the stupid way, I won't take it personally. --Palrich.
