The problem is not one of information storage length, but of flag
collision.
Ints are fine as primary keys on a lookup table, or constant values
for internal flags that will never be extensible. For things we know
people will build on -- like node types, or node build modes --
strings are the only way to avoid collisions when module developers
start expanding.
--Jeff
On May 18, 2009, at 3:27 PM, Karoly Negyesi wrote:
Ints, strings, these are just ways to express bits of information.
Each character of a string will have approx 5 bit of info (or a bit
less, 26 english chars, underscore, thats 27 not 32 but lets say 32).
It also must be noted that its unlikely you will use all possible
combinations, I bet XRNQW will not be used for example...
I am with Peter, his proposal makes sense to me and can code more
possibilities than strings.
