add ffi-export-predicate #101
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This allows the user to provide a predicate to determine which of the
generated symbols will be exported from the cffi/c2ffi specified
package.
By default no symbols are exported (so the current behaviour is maintained)
The predicate is specified in the fashion as :ffi-type-transformer &
:ffi-name-transformer
```
:ffi-export-predicate "test-c2ffi.ffi::ffi-export-predicate"
```
The predicate function has the following form
```
(defun ffi-export-predicate (symbol)
(alexandria:starts-with-subseq "NK-" (symbol-name symbol)))
```
cbaggers
force-pushed
the
feature-c2ffi-export-predicate
branch
from
a99875b
to
2dbed5f
Compare
|
thanks, merged with a small follow-up commit that makes sure that the predicate accepts &allow-other-keys for future extendability. |
|
Thanks man, that's great :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows the user to provide a predicate to determine which of the generated symbols will be exported from the cffi/c2ffi specified package.
By default no symbols are exported (so that the current behaviour is maintained)
The predicate is specified in same the fashion as :ffi-type-transformer & :ffi-name-transformer
The predicate function has the following form
We also switch to using
uiop'sdefine-packageso that usingasdf:load-system :force tdoesnt throw errors when it hitsdefpackage