search for: fcdac33

...> return $ret; > } Except I can't even figure out how to expose nbdkit_set_error (hmm, I named it set_error instead of set_errno in my v2 series) to the perl code. In fact, with just this change to example.pl: diff --git i/plugins/perl/example.pl w/plugins/perl/example.pl index fcdac33..64f6de3 100644 --- i/plugins/perl/example.pl +++ w/plugins/perl/example.pl @@ -1,4 +1,5 @@ use strict; +use POSIX (); # Example Perl plugin. # @@ -80,6 +81,8 @@ sub pwrite my $buf = shift; my $count = length ($buf); my $offset = shift; + my $err = POSIX::EPERM; substr (...

Requires patch 1 and 2 of the python series: https://www.redhat.com/archives/libguestfs/2017-January/msg00126.html This is the perl implementation along the same lines. We still haven't decided if patch 1 of the python series should change OCaml to report errno as reliable or not, but perhaps we can commit that patch as-is now and then touch things up further when we actually get set_error

On 01/24/2017 05:38 AM, Richard W.M. Jones wrote: > On Mon, Jan 23, 2017 at 09:13:23PM -0600, Eric Blake wrote: >> Begin the language binding followups to my new .zero callback, since >> Rich was indeed correct that we want them. >> >> I'm more familiar with python and perl (at least to the point that >> I was able to modify the appropriate example files and