summaryrefslogtreecommitdiffstats
path: root/Makefile
diff options
context:
space:
mode:
authorKaz Kylheku <kaz@kylheku.com>2017-06-10 10:31:43 -0700
committerKaz Kylheku <kaz@kylheku.com>2017-06-10 10:31:43 -0700
commit8557121c01f072f7e194c93c1e545e0b51ed563d (patch)
tree86789f4605c1c15e5dc91f3308e7ab10de708066 /Makefile
parentec07d15b76092e4fe61198f8d2d9b64d63e2bd23 (diff)
downloadtxr-8557121c01f072f7e194c93c1e545e0b51ed563d.tar.gz
txr-8557121c01f072f7e194c93c1e545e0b51ed563d.tar.bz2
txr-8557121c01f072f7e194c93c1e545e0b51ed563d.zip
ffi: bugfix: string semantics on typedef-d chars.
The problem is that if we have a typedef like (typedef x char) then (array 256 x) will not do string conversion in the manner of (array 256 char). This is because the raw syntax is checked for the symbol char, rather than inspecting the type object. * ffi.c (ffi_type_compile): When checking whether the array element is a char, bchar or wchar, look at the syntax in the compiled type object, not the raw syntax. The compiled type object is the original type pulled from behind the typedef alias and has the symbol char, bchar or wchar as its syntax.
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions