Also, a char is not guaranteed to be signed, so it would probably be preferable to use int8_t for tri-state options. See http://stackoverflow.com/a/2054941 for some background.
On Jul 29, 2012, at 2:42PM, Eduardo Silva wrote: > in general a char "should be (but not mandatory for all architectures) > 1 byte, i would suggest to force it in an explicit way > > On Sun, Jul 29, 2012 at 4:49 AM, Lauri Kasanen <[email protected]> wrote: >> On Sat, 28 Jul 2012 11:32:25 -0600 >> Eduardo Silva <[email protected]> wrote: >> >>> i meant... Xint8_t family. >>> >> >> OK, but why? None of the existing state uses those, it has the normal "int"s >> and "short int"s, not int32_t and int16_t. >> >> Why break from the existing style? >> >> - Lauri > > > > -- > Eduardo Silva > http://edsiper.linuxchile.cl > http://www.monkey-project.com > _______________________________________________ > Monkey mailing list > [email protected] > http://lists.monkey-project.com/listinfo/monkey _______________________________________________ Monkey mailing list [email protected] http://lists.monkey-project.com/listinfo/monkey
