You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been working on a set of foreign function APIs for Common Lisp using the CRoaring API.
Just a note that the iterator interface is a bit problematic and would benefit from a couple of additional functions that encapsulate access to the has_value and current_value members of roaring_uint32_iterator_t.
Without a function to access those members, I'm forced to write lisp structures which must model an accurate structure of the C header file declarations so that the offsets of the member variables can be correctly determined. Fortunately lisp let's me do this, but unless I add some kind of header file groveling logic on every use of the lisp API, any change to the C structure could result in improper accesses to the desired member variables.
Note that inline functions (which might be an 'accessor' temptation), mean that there is no symbol in the shared library that can be called, so would not be useful for languages calling CRoaring as a foreign API, so if accessor functions are ever provided they should not be declared 'inline'.
The text was updated successfully, but these errors were encountered:
I've been working on a set of foreign function APIs for Common Lisp using the CRoaring API.
Just a note that the iterator interface is a bit problematic and would benefit from a couple of additional functions that encapsulate access to the
has_value
andcurrent_value
members ofroaring_uint32_iterator_t
.Without a function to access those members, I'm forced to write lisp structures which must model an accurate structure of the C header file declarations so that the offsets of the member variables can be correctly determined. Fortunately lisp let's me do this, but unless I add some kind of header file groveling logic on every use of the lisp API, any change to the C structure could result in improper accesses to the desired member variables.
Note that inline functions (which might be an 'accessor' temptation), mean that there is no symbol in the shared library that can be called, so would not be useful for languages calling CRoaring as a foreign API, so if accessor functions are ever provided they should not be declared 'inline'.
The text was updated successfully, but these errors were encountered: