Re: [E-devel] efl_add causing confusion

2017-12-25 Thread Carsten Haitzler
On Sun, 24 Dec 2017 09:23:16 + Andrew Williams said: > Hi, > > Yes invalid access is easier to debug than a memory lean, in general. > In this situation we are talking about the possible consistent memory leaks > vs the occasional (race condition) undefined access. The latter is not > easier

Re: [E-devel] efl_add causing confusion

2017-12-25 Thread Carsten Haitzler
On Sun, 24 Dec 2017 09:16:08 + Andrew Williams said: > Are you trolling me now? no. you said its inconsistent. it's consistent. it has a simple rule. http://www.dictionary.com/browse/consistent it consistently adheres to the same principles. i described them. > A method that does two diff

Re: [E-devel] is there a roadmap for future significative improvements/changes

2017-12-25 Thread Carsten Haitzler
On Sun, 24 Dec 2017 22:41:20 + Andrew Williams said: > You're quit right that document is really more of a checklist. Which now I > look more closely is exactly what they called it too. > Their roadmap document is actually > https://wiki.gnome.org/Projects/GTK+/Roadmap . > > Anyhow for clari

Re: [E-devel] efl_add causing confusion

2017-12-25 Thread Carsten Haitzler
On Sun, 24 Dec 2017 09:20:33 + Andrew Williams said: > The proposal has 0 occurrences of “NULL”. it has api examples with parent provided on creation. obviously some objects will not provide a parent (e.g. a toplevel of a tree that has no parents). > Andy > > On Sun, 24 Dec 2017 at 03:33,