On Thu, 19 Apr 2012 06:27:23 +1000 David Seikel <[email protected]> said:
> I'm not seeing anywhere in the docs a description of the eet integer > data type sizes. The float types include their size in the name - actually those are fixed point, not float. theres FLOAT and DOUBLE for floating point... no sizes specified. > EET_T_F16P16. What size are EET_T_CHAR, EET_T_SHORT, EET_T_INT, and > EET_T_LONG_LONG? I would guess 8, 16, 32, and 64 bits, but a quick > look at the code seems to suggest they are compiler dependant. At the > very least it should be documented. And easily found if it IS > documented. lol they are compiler dependent... but NOTE... that there is no LONG, .. LONG_LONG, but not LONG. there is a reason for this. all of EFL assumes the following: CHAR=8 SHORT=16 INT=32 FLOAT=32 DOUBLE=64 LONG_LONG=64 and the wiggly bit - why LONG is skipped: LONG=32/64 (depending on arch) if your compiler or architecture doesn't conform to this - EFL doesn't work, so it's not documented because it is part of the base architecture assumption. no sane modern architecture in the *NIX world that is commonly in use violates the above assumption. ints don't magically become 16bit or 64bit based on architecture. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
