cffi-devel August 2017

cffi-devel@common-lisp.net

4 participants
2 discussions

foreign-type-size implementation
by james anderson 25 Aug '17

25 Aug '17

while profiling code which depends on foreign sizes, i observed that foreign-type-size was doing most of the work. this (so it seems) due to the circularity check. is there some reason that there is no logic to decide to push the process into compile-time where it is possible? something like: (define-compiler-macro foreign-type-size (&whole form type) (cond ((or (keywordp type) (typep type '(cons (eql :struct)))) (foreign-type-size type)) ((and (symbolp type) (constantp type)) (foreign-type-size (symbol-value type))) (t form)))

3 5

Hello.
by mike thomas 11 Aug '17

11 Aug '17

Hi there. Thanks for all the great work you do here. I had a problem loading cl-libuv from Quicklisp on Windows because the default installation location for the development package sits in C:/Program Files/libuv, which broke the grovel compilation. The include path list is split by the code below, fixed by removing the space from the separator list per the patch. It wasn't clear to me what parse-command-flags was meant to do, given the definitions in grovel.lisp of cl-libuv which control the header search paths. Is there a place to lodge bug reports on github for cffi? Maybe one needs to be a contributor? Cheers Mike @@ -33,7 +33,7 @@ ;;; Utils (defun parse-command-flags (flags) - (let ((separators '(#\Space #\Tab #\Newline #\Return))) + (let ((separators '(#\Tab #\Newline #\Return))) (remove-if 'emptyp (split-string flags :separator separators)))) (defun parse-command-flags-list (strings)

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

cffi-devel August 2017