On Tue, May 26, 2009 at 3:06 PM, Basil Gasser <[email protected]> wrote: > Hi John, > This is really a bit arbitrary but you are right with the assumption that we > use an array behind the scence. Assuming that we write arrays from left to > right we have: (for example int 7) > ArrayIndex 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 > Value 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 > which seems to me to be intuitive but if many find this confusing or it > forces people to manually invert the arrays, I think it would be worth > discussing this issue and thinking about changing this. > > ++ Basil
I think anchoring the LSB at bit 0 would be more intuitive but that might just be me. Actually, now that I think about it, what is the motivation to expose twoBit like it's a bit vector? IIRC the intent is for twoBit to be a (restricted range) integer type, not a bitVector (there's a separate type for bitVector). Perhaps this is completely internal to your library? If so, I hereby lose interest in the question :-) -- John. ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ llrp-toolkit-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/llrp-toolkit-devel
