On Sun, 17 Aug 2014 01:40:25 -0300 Vinícius dos Santos Oliveira <[email protected]> wrote:
> 2014-08-17 1:24 GMT-03:00 Carsten Haitzler <[email protected]>: > > > compile-time for efl itself. you have to build it without checking. > > i'd advise > > against it because efll uses its own objects internally and if efl > > has a mistake in it you just nuked efl's own internal safety. i > > highly suggest not > > doing this. > > > > it may be that we remove the ability to compile without this check > > in the end > > as i an just see it now. gentoo ricers are going to add a use flag > > to turn this > > off and then we will get tonnes of stability complaints because the > > rest of us > > normal people run without turning the safety off. > > > > it's worth keeping this safety on. it doesn't cost much and is > > totally worth > > it. > > > > I'd like to see this checking disabled per call only, not globally. > Then only bindings for safe languages would use it. > > I'll leave the safety checks turned on. They're worth. Also, EFL is > for GUI only and heavy computing sensitive data can be implemented > without negative impact by just not touching EFL (temporally). I disagree with that. Parts of EFL are not specific to GUI stuff, like Eina data structures and the functions to manage them, logging, file manipulation, executable running, etc. Even EFL based thread support. I use EFL in applications that don't have a GUI, using those sorts of things. In fact I do heavy computing using those EFL data structures and threading. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. ------------------------------------------------------------------------------ _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
