summaryrefslogtreecommitdiff
path: root/testing/cffi0
Commit message (Expand)AuthorAgeFilesLines
* Fix for Python 2.6Armin Rigo2016-02-131-0/+3
* Issue #244: parse_type() calls the Parser logic but self._options usedArmin Rigo2016-01-311-0/+5
* issue #243: explicitly complain if ffi.def_extern() is called on theArmin Rigo2016-01-191-0/+4
* OS/X fix: clang has got a warning enabled by default hereArmin Rigo2016-01-161-2/+2
* Delay changing this to 1.6 (1.5 is very soon after 1.4)Armin Rigo2016-01-151-2/+2
* more tweaks; tests needed...Armin Rigo2015-12-301-0/+7
* Removal of the deprecation is deferred to 1.5Armin Rigo2015-12-151-2/+2
* refactor the lazy-loading in dlopen() lib objects; add __dir__().Armin Rigo2015-12-081-1/+13
* py3k compatArmin Rigo2015-12-071-1/+6
* hg merge defaultArmin Rigo2015-11-232-1/+33
|\
| * issue #233: ffi.init_once()Armin Rigo2015-11-231-0/+32
| * fixArmin Rigo2015-11-171-1/+1
* | Write one error message directly to stderr instead of sys.stderr. ThisArmin Rigo2015-11-181-27/+5
* | Fix cparserArmin Rigo2015-11-181-8/+22
* | Parsing CFFI_CALL_PYTHON in the cdefArmin Rigo2015-11-121-0/+14
|/
* Give a warning instead of crashing; in this way we can call the nextArmin Rigo2015-11-061-0/+3
* Complain more readily about opaque enums, by refusing to guess whichArmin Rigo2015-11-051-1/+10
* Allow different formattings of the underlying "%p"Armin Rigo2015-11-031-1/+2
* Issue #228: "bool" not working in out-of-line FFI objects. Same problemArmin Rigo2015-11-021-27/+5
* Found a pycparser issue. Work around it by adding some parentheses inArmin Rigo2015-11-021-0/+35
* Fix the error we get for 'int f(unknown_type);'Armin Rigo2015-11-021-0/+7
* wchar_t can be signed or not, apparently, even on the same platform (armArmin Rigo2015-10-221-3/+4
* Backed out changeset fbe55ed7e5e2Armin Rigo2015-10-211-7/+0
* Issue #225: Ignore basic SAL annotations on Windows.Armin Rigo2015-10-201-0/+7
* fix corner case of writing "typdef char INT8, *PINT8;" on WindowsArmin Rigo2015-10-181-0/+6
* win32 fixArmin Rigo2015-10-161-1/+2
* win32 fixArmin Rigo2015-10-161-1/+4
* win64 fixArmin Rigo2015-10-161-2/+2
* win64 fixArmin Rigo2015-10-161-1/+1
* win64 fixArmin Rigo2015-10-161-7/+13
* Comment out the prints (not py3)Armin Rigo2015-10-081-6/+6
* ffi.memmove()Armin Rigo2015-10-081-0/+53
* remove the debug printfsArmin Rigo2015-10-061-12/+12
* Fix remaining testsArmin Rigo2015-10-061-1/+1
* more of the sameArmin Rigo2015-10-061-4/+4
* Aargh, WINAPI is not a macro??Armin Rigo2015-10-061-9/+21
* more test fixesArmin Rigo2015-10-061-7/+25
* Another passing testArmin Rigo2015-10-061-6/+33
* Fix testArmin Rigo2015-10-061-38/+31
* start to fix testsArmin Rigo2015-10-062-27/+27
* Support directly __stdcall or WINAPI (or __cdecl, ignored) insideArmin Rigo2015-10-061-0/+14
* in-progress, but found a problemArmin Rigo2015-10-061-18/+125
* check that the function types are really incompatibleArmin Rigo2015-10-051-0/+7
* non-windows fixesArmin Rigo2015-10-051-4/+6
* Starting, with exactly two function types: no-abi (i.e. cdecl on windows), or...Armin Rigo2015-10-051-8/+12
* A branch to implement "__stdcall" more completely on Windows. Initial testsArmin Rigo2015-10-052-1/+45
* ARM is documented to have 'unsigned int' as the wchar_t typeArmin Rigo2015-10-051-2/+2
* Fix tests to run on more 32-bit x86esArmin Rigo2015-10-011-0/+3
* test fixArmin Rigo2015-09-301-1/+1
* add a passing testArmin Rigo2015-09-301-0/+13