I didn't think about the gen-nrconfig change very closely when it was first made, but in retrospect, since NRShort is a general-purpose type with a precision implied by its name, changing its precision is probably a bug in itself.
The correct fix is to replace uses of NRShort that require more precision with a type that provides it -- e.g. NRLong, or better gint32.
Why "better"? What if one day, we need 64 bit precision - do a global search and replace again? The NR* stuff was there exactly for this: a layer of abstraction that allows to change the actual precision quickly - and it was not "a bug" because the typedefs are there for exactly this purpose (and they were not "general purpose" becaue the NR prefix limited their scope pretty narrowly to the NR subsystem). Frankly I don't understand why it was necessary to kill it and replace with hard-coded 32-bit types (I can understand getting rid of nr-config.c, but not this). Anyway, it's not my domain, so please fix it one way or the other, so long as it's fixed :)
_________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2f...