-
Notifications
You must be signed in to change notification settings - Fork 23
Closed
Labels
🐣EnhancementThings that make it work betterThings that make it work better
Description
There could be some advantages to supporting multiple implementations down the road. Examples:
Win32::APImay provide better performance or features on Windows platforms- GNU
ffcallmay support some platforms thatlibffidoes not (skeptical) - Alternate implementations of Perl, such as p2, gperl or moe or even Perl 6
I had this in mind when I was designing the interface, but I haven't been implementing it in a particularly pluggable way unfortunately. Tasks include:
- Moving the libffi specific Perl code into
FFI::Platypus::Impl::Libffi FFI::Platypusbecomes a subclass ofFFI::Platypus::Impl::...- split the XS and C code into libffi specific stuff and non-libffi specific stuff. For example
ffi_platypus_call.his decidedly libffi specific. The record code should not be. - Remove the libffi objects from the structs in
ffi_platypus.h. Right now we are using the size and type fields for logic. This is probably the most significant task.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
🐣EnhancementThings that make it work betterThings that make it work better