nativetest

root@testperl6:~/piko/nativecall-typediag# perl6 -I lib t/func.t 
ok 1 - Taking a pointer is fine
ok 2 - Taking a CStruct is fine
ok 3 - Taking a CArray is fine
In 'badclass' routine declaration - Not an accepted NativeCall type for parameter [1] $a : B
-->For Numerical type, use the appropriate int32/int64/num64...
ok 4 - Taking a Perl6 class is NOT fine
ok 5 - Taking a int32 is fine
In 'badint' routine declaration - Not an accepted NativeCall type for parameter [1] $a : Int
-->For Numerical type, use the appropriate int32/int64/num64...
ok 6 - Taking a Int is NOT fine
In 'badint2' routine declaration - Not an accepted NativeCall type for parameter [1] $a : int
-->For Numerical type, use the appropriate int32/int64/num64...
ok 7 - Taking a int is NOT fine
ok 8 - Taking a num32 is fine
In 'badnum' routine declaration - Not an accepted NativeCall type for parameter [1] $a : Num
-->For Numerical type, use the appropriate int32/int64/num64...
ok 9 - Taking a Num is NOT fine
In 'badnum2' routine declaration - Not an accepted NativeCall type for parameter [1] $a : num
-->For Numerical type, use the appropriate int32/int64/num64...
ok 10 - Taking a num is NOT fine
ok 11 - Taking a Str is fine
ok 12 - FIXME: Taking a str is buggy but should be fine?
ok 13 - Returning a pointer is fine
ok 14 - Returning a CStruct is fine
ok 15 - Returning a CArray is fine
ok 16 - Returning a int32 is fine
The returning type of 'badretint' --> int is errornous. You should not return a non NativeCall type (like Int inplace of int32), truncating errors can appear with different architectures
ok 17 - Returning a Int is NOT fine
The returning type of 'badretint2' --> Int is errornous. You should not return a non NativeCall type (like Int inplace of int32), truncating errors can appear with different architectures
ok 18 - Returning a int is NOT fine
ok 19 - Returning a num32 is fine
The returning type of 'badretnum' --> num is errornous. You should not return a non NativeCall type (like Int inplace of int32), truncating errors can appear with different architectures
ok 20 - Returning a Num is NOT fine
The returning type of 'badretnum2' --> Num is errornous. You should not return a non NativeCall type (like Int inplace of int32), truncating errors can appear with different architectures
ok 21 - Returning a num is NOT fine
ok 22 - Returning a bool is fine
ok 23 - FIXME: Returning a Bool maybe be bugged
ok 24 - Taking an encoded Str is fine
ok 25 - Returning an encoded Str is fine
1..25