Revert previous patch generated by badnull.cocci script, and apply the new one.
The main difference is that assert and assert-like functions are not touched
anymore.
SVN revision: 51650
Apply badzero.cocci, badnull.coci and badnull2.cocci
This should convert all cases where there's a comparison to NULL to simpler
forms. This patch applies the following transformations:
code before patch ||code after patch
===============================================================
return a == NULL; return !a;
return a != NULL; return !!a;
func(a == NULL); func(!a);
func(a != NULL); func(!!a);
b = a == NULL; b = !a;
b = a != NULL; b = !!a;
b = a == NULL ? c : d; b = !a ? c : d;
b = a != NULL ? c : d; b = a ? c : d;
other cases:
a == NULL !a
a != NULL a
SVN revision: 51487
Bad news, I also discovered in the same time that we introduced an
API/ABI breakage in 1.3.0. This patch does prevent it from coming
again, sadly, it imply an ABI break that I didn't find a proper
way to work around. So recompile eet and all the program that use
it after that commit.
SVN revision: 51080
* Remove vim modelines:
find . -name '*.[chx]' -exec sed -i '/\/\*$/ {N;N;/ \* vim:ts/d}' \{\} \;
find . -name '*.[chx]' -exec sed -i '/\/[\*\/] *vim:/d' \{\} \;
* Remove leading blank lines:
find . -name '*.[cxh]' -exec sed -i '/./,$!d'
If you use vim, use this in your .vimrc:
set ts=8 sw=3 sts=8 expandtab cino=>5n-3f0^-2{2(0W1st0
SVN revision: 50816
now on. you may run indent on code and convert to your own formatting
if you want.. but all code MUST be "uncrustified" before being
cxommitted to svn or before generating patches. time to get the
formatting monster under control.
SVN revision: 50563
Eet_Data now use more common code when doing dump/decode. This
provide new functionnality, you can now do a list/array/hash of string.
make test/coverage are now passing without problem with 79% of the code
covered (mainly need to update test suite for fixed point). This rewrite
is also a first for script langage to directly manipulate Eet_Data (more
patch comming). It's also a cleanup of the Eet_Node API that could now
be used just fine.
Note: Previous dump will not be compatible with this update, but
Eet_Data will.
PS: I did some extensive test here with enlightenment, elementary_test,
editje, elixir and eyelight. If you experience any weird behaviour that
could be linked with eet_data (well almost anything that use the EFL),
please report to me as soon as possible.
SVN revision: 45059
- Array layout would be broken or worse not possible to reload at all if you put NULL pointer in it.
- Array of string now work.
- Fix a double free issue with array on double load.
* Add the test to detect this case.
SVN revision: 37051
* Add a test case for that one.
Problem was simple type inlining in complex structure (like list/hash/array) is
just a hack. We are creating a subtype with the data chunk. That work with INT
or SHORT for example, but not with STRING because it's a pointer to a STRING and
not directly the STRING. This result in a double pointer dereferencing where it
shouldn't. In fact STRING is not really like other simple data type. So we
should handle it differently.
Still need to fix Array and Hash.
SVN revision: 37024
* put documentation related files in doc, remove gendoc and
add a doc rule to create the documentation and a doc tarball
named eet-doc-$(version).tar.bz2
* minor cleanup in the autotools
SVN revision: 36706
You can use eet -s to sign a eet file and eet -c to check its signature. The
current code doesn't check any certificate trust path, only if the signature
match the certificate and that the certificate could be loaded. If that's not
the case, eet_open will fail. If the file is not signed, eet_open will just
continue to succeed.
SVN revision: 35882