Re: [E-devel] efl_add causing confusion

2017-12-24 Thread Andrew Williams
Are you trolling me now? A method that does two different things depending on some magic value / null flag is a code smell (see Clean Coders if this is not familiar). Consider this method: ptr get_mem(string poolname, long bytes) { If (poolname == NULL) return malloc(bytes); // MUST be freed else

Re: [E-devel] efl_add causing confusion

2017-12-24 Thread Andrew Williams
The proposal has 0 occurrences of “NULL”. Andy On Sun, 24 Dec 2017 at 03:33, Carsten Haitzler wrote: > On Sat, 23 Dec 2017 11:26:42 + Andrew Williams > said: > > > Hi, > > > > Thanks for posting that poll. Very useful. > > If I may I wish to contradict your assertion that this has all been

Re: [E-devel] efl_add causing confusion

2017-12-24 Thread Andrew Williams
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 to debug. And if we did find the line at error it would look (using t

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

2017-12-24 Thread Andrew Williams
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 clarity what I feel we are missing in our "roadmap" is: * What are we aimin