summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Fix the logic: must store 'closure_exec' in the c_data field, and theffi_closure_allocArmin Rigo2015-11-101-15/+26
| | | | 'closure' in some other new field.
* tryArmin Rigo2015-11-103-100/+17
|
* Using the official interface from ffi to get closure memoryArmin Rigo2015-11-100-0/+0
|
* Give a warning instead of crashing; in this way we can call the nextArmin Rigo2015-11-062-4/+9
| | | | | release 1.3.1 as planned and give some advance warning to users relying on this.
* Complain more readily about opaque enums, by refusing to guess whichArmin Rigo2015-11-052-3/+15
| | | | integer type (unsigned/signed, int/long) it is meant to be.
* Add a direct test for _get_common_types()Armin Rigo2015-11-031-1/+6
|
* One of the Windows common types was lost somehow. Add a testArmin Rigo2015-11-032-2/+19
| | | | that at least dependencies are there.
* Show <ctype 'FILE'> instead of <ctype 'struct _IO_FILE'>Armin Rigo2015-11-032-2/+2
|
* Allow different formattings of the underlying "%p"Armin Rigo2015-11-031-1/+2
|
* Issue #228: do the same for "FILE". Only remaining case now is theArmin Rigo2015-11-038-11/+64
| | | | | | | very obscure Windows type UNICODE_STRING. I think it is unlikely that someone hits the case of their cdef not mentioning UNICODE_STRING but their runtime code still wants to use it, so I'll close this issue.
* Issue #228: "bool" not working in out-of-line FFI objects. Same problemArmin Rigo2015-11-0211-260/+334
| | | | | | | with all Windows common types. Mostly fixed by moving the list of common types to C code. The only remaining corner case I can think of is "FILE", which works only if it was mentioned in the cdef while building the out-of-line module.
* Found out that the pycparser problem was fixed between 2.10 and 2.14.Armin Rigo2015-11-021-20/+25
|
* Found a pycparser issue. Work around it by adding some parentheses inArmin Rigo2015-11-023-2/+85
| | | | the csource passed to it, to avoid the buggy cases.
* Propagate "volatile" in addition to "const" and "restrict"Armin Rigo2015-11-023-3/+15
|
* Fix the error we get for 'int f(unknown_type);'Armin Rigo2015-11-022-0/+14
|
* typoArmin Rigo2015-10-241-1/+1
|
* Clarify documentation for ffi.from_buffer(): it also works on read-onlyArmin Rigo2015-10-241-2/+5
| | | | buffer objects
* hg merge release-1.3Armin Rigo2015-10-222-6/+8
|\
| * wchar_t can be signed or not, apparently, even on the same platform (armArmin Rigo2015-10-222-6/+8
| | | | | | | | linux)
* | typoArmin Rigo2015-10-211-1/+1
| |
* | md5/sha1Armin Rigo2015-10-211-2/+2
| |
* | make release branchArmin Rigo2015-10-210-0/+0
|/
* Argh.Armin Rigo2015-10-211-0/+5
|
* Document the trick of re.sub() to remove SAL annotations on WindowsArmin Rigo2015-10-211-9/+25
|
* Backed out changeset fbe55ed7e5e2Armin Rigo2015-10-213-17/+0
| | | | It's probably better written in the docs instead.
* Issue #225: Ignore basic SAL annotations on Windows.Armin Rigo2015-10-203-0/+17
|
* fix corner case of writing "typdef char INT8, *PINT8;" on WindowsArmin Rigo2015-10-182-0/+19
|
* py3 and no-g++ fixesArmin Rigo2015-10-161-2/+2
|
* win32 fixArmin Rigo2015-10-161-1/+2
|
* win32 fixArmin Rigo2015-10-162-2/+9
|
* win64 fixesArmin Rigo2015-10-161-5/+5
|
* win64 fixArmin Rigo2015-10-161-1/+1
|
* win64 fixArmin Rigo2015-10-161-3/+6
|
* win64 fixArmin Rigo2015-10-161-2/+2
|
* win64 libffi issueArmin Rigo2015-10-161-2/+9
|
* win64 fixArmin Rigo2015-10-161-1/+1
|
* win64 fixArmin Rigo2015-10-161-7/+13
|
* Document ffi.memmove()Armin Rigo2015-10-162-11/+36
|
* document this windows changeArmin Rigo2015-10-141-1/+8
|
* try to be more accuratemattip2015-10-142-3/+5
|
* document hack removal, leave hack in place for backward compatability with ↵mattip2015-10-132-1/+16
| | | | verify()
* remove _hack_at_distutils which imports setuptools on win32, it has too many ↵mattip2015-10-111-11/+0
| | | | | | side effects. Not needed since 1.0 since developers can distribute binary packages, even on win32
* Another test (passing)Armin Rigo2015-10-091-0/+6
|
* Test yet another case (for pypy)Armin Rigo2015-10-091-0/+2
|
* Test and fix: a negative size was implicitly converted to a huge size_tArmin Rigo2015-10-092-1/+10
| | | | number
* write a "document me"Armin Rigo2015-10-081-0/+2
|
* Comment out the prints (not py3)Armin Rigo2015-10-082-9/+9
|
* ffi.memmove()Armin Rigo2015-10-086-7/+265
|
* Clarify some detailsArmin Rigo2015-10-071-15/+22
|
* add a direct testArmin Rigo2015-10-071-3/+13
|