summaryrefslogtreecommitdiff
path: root/src/lib/eo/eo_add_fallback.c (follow)
AgeCommit message (Collapse)Author
2018-01-12mmap memory allocation - do not used when under valgrindCarsten Haitzler (Rasterman)
we can't sensibly use things like massif to track memory if we bypass itr with mmaping -1 fd anonymous memory... so if built with valgrind support and running under valgrind, use malloc/calloc and free so these tools actually do something useful for these bits of memory.
2016-12-06all: use void if we really want to make sure we do not accept parametersStefan Schmidt
In C we need this to make clear that we really do not accept parameters. Found by the smatch source code matcher. I had run and fixed this before but it seems to creep in again over time.
2016-11-23eo: Fix leak during shutdown()Jean-Philippe Andre
2016-09-05Rename efl_self to efl_addedTom Hacohen
It has been discussed on the ML (thread: "[RFC] rename efl_self") and IRC, and has been decided we should rename it to this in order to avoid confusion with the already established meaning of self which is very similar to what we were using it for, but didn't have complete overlap. Kudos to Marcel Hollerbach for initiating the discussion and fighting for it until he convinced a significant mass. :) This commit breaks API, and depending on compiler potentially ABI. @feature
2016-08-15Eo: Finish the renaming of Eo to the EFL.Tom Hacohen
This renames all the rest of the API to the EFL namespace except for Eo_Event that will follow soon. Obviously breaks both API and ABI.
2016-03-29Eo: Implement the fallback eo_add implementation.Tom Hacohen
The current eo_add uses a (very useful) gcc extension that is only available in gcc compatible compilers (e.g clang). Until this commit we just temporarily ignored this fact. This adds a fallback implementation that can be used interchangeably with the non portable one. This means that the same binary can call either at any point in time and the code will work. Breaks ABI.