in reply to Re^4: Warning. No Inline C functions bound to Perl
in thread Warning. No Inline C functions bound to Perl

But no warning appears if there are both valid and invalid bindings. Ouch.

I agree - you should be told the name of any function that didn't bind. If that information included the name of the package (ie 'package_name::function'), and it was provided irrespective of the setting of $^W, then I think all of the shortcomings covered in this thread will have been addressed.

I'm no expert on the internals of Inline, but I believe all of that should be do-able - and I'm happy to volunteer to let Ingy know.

Ooops .... afterthought .... what if the C section of your script contains a function (not intended to bind to perl) that is needed by one of the other Inline C functions ? Under those circumstances it would be a bit annoying to be told that the function doesn't bind to perl.

Cheers,
Rob
  • Comment on Re^5: Warning. No Inline C functions bound to Perl