summaryrefslogtreecommitdiff
path: root/c/test_c.py
Commit message (Collapse)AuthorAgeFilesLines
* Fix testArmin Rigo2017-01-031-1/+5
|
* readd two lines accidentaly removedRichard Plangger2017-01-031-0/+2
|
* do not allow unicode to directly be passed to from_bufferRichard Plangger2016-12-091-2/+2
|
* allow from_buffer for buffer and memoryview even when they point to ↵Richard Plangger2016-12-091-5/+3
| | | | bytes/unicode
* pypy now can get a raw address from a StringBuffer, modify testRichard Plangger2016-12-091-7/+13
|
* update to 1.9.1Armin Rigo2016-11-121-1/+1
|
* Bump version number to 1.9.0Armin Rigo2016-11-021-1/+1
|
* Fix: the condition "offsetof == sizeof" for being a var-sized arrayArmin Rigo2016-10-291-0/+27
| | | | | is bogus. See test for a case where it is not the case because of alignment.
* Decided to fix ffi.sizeof() too. Update the documentation.Armin Rigo2016-10-271-0/+3
|
* Fix what is hopefully the last remaining issues with ↵Armin Rigo2016-10-251-2/+1
| | | | calculate_variable_array_length
* Tweaks, and add extra tests, which fail for now :-/Armin Rigo2016-10-191-2/+19
|
* Merged in coronafire/cffi/calculate_variable_array_length (pull request #71)Armin Rigo2016-10-191-4/+9
|\ | | | | | | Track and use length of variable length structs and their varsized array
| * Detect and mark the final variable array in a varsized struct with ↵calculate_variable_array_lengthAndrew Leech2016-09-141-1/+1
| | | | | | | | | | | | BS_VARSIZESTRUCT_ARRAY Use this when returning this field/arrtibute of said struct
| * Add some initial test assertions to check length details on variable length ↵Andrew Leech2016-09-131-3/+8
| | | | | | | | structs
* | Improve testArmin Rigo2016-10-141-0/+2
| |
* | update to 1.8.4 and add whatsnewArmin Rigo2016-09-201-1/+1
| |
* | Document the new warningArmin Rigo2016-09-151-0/+2
| |
* | bump version number to 1.8.3Armin Rigo2016-09-151-1/+1
| |
* | Warn when implicitly casting between "char *" and a different pointerArmin Rigo2016-09-151-0/+22
|/ | | | type, like C does (there is no special-case of "char *" in C)
* A direct testArmin Rigo2016-09-061-0/+19
|
* Update and document v1.8.2Armin Rigo2016-09-061-1/+1
|
* Bump version number to 1.8.1Armin Rigo2016-09-031-1/+1
|
* Give an error when subtracting two pointers and the division's result isArmin Rigo2016-08-151-0/+13
| | | | | not exact (in gcc, we get nonsense, so it means it is undefined behavior for C, which is best handled by raising in cffi)
* Update the version number to 1.8Armin Rigo2016-08-061-1/+1
|
* The null_byte_after_str branch of PyPy makes ffi.from_buffer(str)Armin Rigo2016-08-021-1/+6
| | | | possible.
* Support dir(p), where p is a struct or pointer-to-struct, to obtainArmin Rigo2016-06-061-2/+22
| | | | the list of field names.
* update version number to 1.7Armin Rigo2016-06-051-1/+1
|
* Add a test for another use caseArmin Rigo2016-06-031-0/+7
|
* Slice assignment with bytearray as sourceArmin Rigo2016-06-031-4/+6
|
* From PyPy 5.2, bytearray buffers can fetch a raw pointer, soArmin Rigo2016-06-031-6/+16
| | | | there is no reason any more to prevent from_buffer(bytearray()).
* an extra testArmin Rigo2016-05-071-0/+1
|
* Issue #255: `bool(ffi.cast("primitive", x))` is now True or FalseArmin Rigo2016-05-071-3/+8
| | | | | depending on whether the value is zero or not. It used to always be True for any value.
* update the version number to 1.6Armin Rigo2016-04-171-1/+1
|
* Oops. In this case, unpack(p) returns a list of <cdata struct> thatArmin Rigo2016-04-171-1/+2
| | | | are each inside 'p'. So 'p' must be kept alive
* There is no reason to restrict ffi.unpack() to primitives.Armin Rigo2016-04-171-1/+23
|
* Remove again ffi.rawstring(), and implement instead ffi.unpack().Armin Rigo2016-04-161-12/+39
| | | | | | | | | | | | | Pre-documentation notes: (hi Amaury :-) * ffi.unpack(<cdata 'char'>, n) == ffi.buffer(<cdata 'char'>, n)[:] but I hope it is a little bit more natural * ffi.unpack(<cdata 'wchar_t'>, n): this is the original motivation, because it has no previous equivalent * ffi.unpack(<cdata 'int'>, n) == list(<cdata 'int'>[0:n]) but should be much faster on CPython
* Python3 compatArmin Rigo2016-04-151-4/+4
|
* Also accept arrays of int8_t or uint8_t, like ffi.string()Armin Rigo2016-04-151-0/+4
|
* Add a test hereArmin Rigo2016-04-151-0/+15
|
* Update versionArmin Rigo2016-02-131-1/+1
|
* bump the version numberArmin Rigo2016-02-091-1/+1
|
* bump version number to 1.5.0Armin Rigo2016-01-151-1/+1
|
* Update the version numbers and make sure the _cffi_backend module isArmin Rigo2016-01-011-1/+1
| | | | a version that supports embedding!
* bump to 1.4.2 (reason in issue #239)Armin Rigo2015-12-211-1/+1
|
* bump version numberArmin Rigo2015-12-171-1/+1
|
* bump version number to 1.4.0Armin Rigo2015-12-111-1/+1
|
* update version to 1.3.1Armin Rigo2015-11-141-1/+1
|
* Add a direct test for _get_common_types()Armin Rigo2015-11-031-1/+6
|
* Another test (passing)Armin Rigo2015-10-091-0/+6
|
* Test yet another case (for pypy)Armin Rigo2015-10-091-0/+2
|
View Lorry Controller Status