New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document suggestion to use libffi for simple library bindings #16671
Comments
From @GrinnzPerl XS is a vastly complex tool that isn't always needed where libffi For simple bindings to C libraries as well as other machine code libraries, -Dan |
From @GrinnzPatch attached. |
From @Grinnzperlxs_ffi.patchdiff --git a/dist/ExtUtils-ParseXS/lib/perlxs.pod b/dist/ExtUtils-ParseXS/lib/perlxs.pod
index 1419ee0ddf..e9b2ef3e32 100644
--- a/dist/ExtUtils-ParseXS/lib/perlxs.pod
+++ b/dist/ExtUtils-ParseXS/lib/perlxs.pod
@@ -79,6 +79,11 @@ Note: For some extensions, Dave Beazley's SWIG system may provide a
significantly more convenient mechanism for creating the extension
glue code. See L<http://www.swig.org/> for more information.
+For simple bindings to C libraries as well as other machine code libraries,
+consider instead using the much simpler
+L<libffi|http://sourceware.org/libffi/> interface via CPAN modules like
+L<FFI::Platypus> or L<FFI::Raw>.
+
=head2 On The Road
Many of the examples which follow will concentrate on creating an interface
|
From @xsawyerx+1 from me. On 08/25/2018 02:54 AM, Dan Book via RT wrote:
|
The RT System itself - Status changed from 'new' to 'open' |
From @xsawyerx+1 from me. On 08/25/2018 02:54 AM, Dan Book via RT wrote:
|
From @mohawk2Might it also be worth mentioning the small CPAN Module NativeCall? |
From [Unknown Contact. See original ticket]Might it also be worth mentioning the small CPAN Module NativeCall? |
From @GrinnzOn Sat, 25 Aug 2018 15:03:51 -0700, etj@cpan.org wrote:
I considered this but it's only a P6-inspired wrapper of FFI::Platypus, I think pointing people to the two options for libffi usage is sufficient for core perldocs. |
Migrated from rt.perl.org#133474 (status was 'open')
Searchable as RT133474$
The text was updated successfully, but these errors were encountered: