On Fri, 29 Aug 2014 09:41:35 +0900 Carsten Haitzler (The Rasterman) <[email protected]> wrote:
> On Thu, 28 Aug 2014 22:23:03 +0100 Tom Hacohen <[email protected]> said: > > > On Thu, Aug 28, 2014 at 7:51 PM, Cedric BAIL > > <[email protected]> wrote: > > > > > On Aug 28, 2014 6:10 PM, "Daniel Kolesa" <[email protected]> > > > wrote: > > > > > > > > 2014-08-28 17:06 GMT+01:00 Cedric BAIL <[email protected]>: > > > > > > > > > Hello, > > > > > > > > > > On Thu, Aug 28, 2014 at 5:12 PM, Tom Hacohen > > > > > <[email protected]> wrote: > > > > > > It's been ages since we last complained about the existence > > > > > > of Eina_Bool. We all hate it and think it's useless. It's > > > > > > too long to > > > type, > > > > > > and redundant. "bool" has been available for ages now. Same > > > > > > goes for "true" and "false". I think we should kill > > > > > > Eina_Bool and start using those. It doesn't have to be a > > > > > > sed (though we could sed it out from > > > all > > > > > > of our sources), it can be gradual. > > > > > > > > > > > > If someone thinks there's a platform out there that doesn't > > > > > > have > > > "bool", > > > > > > we can just add a platform check and define it if missing. > > > > > > > > > > > > What do you think? > > > > > > > > > > That it is globally a bad idea. The bool type should not be > > > > > used in any of our public header (due to how poor the > > > > > standard define it). It also should not be used in any of our > > > > > bitfield as nobody knows its size. So starting to use it is > > > > > sure to trigger a mess at some point. So if it's just an > > > > > issue of typing, make a macro in your editor and be done with > > > > > it. > > > > > > > > > > > > > For API it's fine. For bitfields it sucks but we can just > > > > replace all Eina_Bool bitfields with unsigned char. > > > > > > It's not. It break ABI. There's no compatibility between compiler > > > on its size. No ffi also. And yes, it would break bitfield. > > > > > > > As I was telling Quaker, it's less about getting rid of Eina_Bool, > > and more about getting rid of EINA_TRUE and EINA_FALSE in favour of > > their nicer counterparts. Those are the ones we type all the time, > > not Eina_Bool itself. > > i always liked 0 and 1... nice and short. :) to me they represent > false and true (but then i spent much of my life doing assembly > before c and thus to me numbers have meaning - especially small short > simple ones) Sooo, as well as efalse and etrue, just for raster we can define O and I macros. B-) -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/
_______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
