Skip to content

Commit d0d7cd5

Browse files
committed
After #2791 fix
1 parent 07dffb4 commit d0d7cd5

File tree

1 file changed

+4
-9
lines changed

1 file changed

+4
-9
lines changed

doc/Language/nativecall.pod6

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -653,15 +653,10 @@ say $esponja;
653653
654654
NativeCall also supports native functions that take functions as arguments. One
655655
example of this is using function pointers as callbacks in an event-driven
656-
system. When binding these functions via NativeCall, one should need only provide the
657-
equivalent signature as L<a constraint on the code parameter|/type/Signature#Constraining_signatures_of_Callables>:
658-
659-
# See below--this syntax does not work on Rakudo currently
660-
use NativeCall;
661-
# void SetCallback(int (*callback)(const char *))
662-
my sub SetCallback(&callback:(Str --> int32)) is native('mylib') { * }
663-
664-
However, in the case of NativeCall, currently Rakudo requires a space between the
656+
system. When binding these functions via NativeCall, one needs only provide the
657+
equivalent signature as
658+
L<a constraint on the code parameter|/type/Signature#Constraining_signatures_of_Callables>.
659+
In the case of NativeCall, however, as of Rakudo 2019.07, a space between the
665660
function argument and the signature, and the colon of a normal Signature
666661
literal is ommitted, as in:
667662

0 commit comments

Comments
 (0)