Sisyphus
2012-02-13 00:50:53 UTC
Hi,
Contains an amended Inline::C::ParseRegExp.pm that enables the specification
of the 'void' argument (iff we've also specified that the ParseRegExp parser
is to be used).
That is, in our Inline::C code sections, we no longer have to write:
void greet() {printf("Hello World\n");}
We can now also write:
void greet(void) {printf("Hello World\n");}
but that will only work if we've also specified:
use Inline C => Config =>
USING => 'ParseRegExp';
I've also added a diagnostic warning message in Inline.pm that will appear
only if the M62 fatal error message is about to be invoked.
This might give me something to work with if ever that fatality happens
again. To date I've only seen that error happen with
http://www.cpantesters.org/cpan/report/3287249c-5151-11e1-9dba-4238887bd19e
.
No plans to make another stable release any time soon .... subject to
change, of course :-)
Main aim is to give people plenty of time to try out those ParseRegExp.pm
changes if they so desire.
Cheers,
Rob
Contains an amended Inline::C::ParseRegExp.pm that enables the specification
of the 'void' argument (iff we've also specified that the ParseRegExp parser
is to be used).
That is, in our Inline::C code sections, we no longer have to write:
void greet() {printf("Hello World\n");}
We can now also write:
void greet(void) {printf("Hello World\n");}
but that will only work if we've also specified:
use Inline C => Config =>
USING => 'ParseRegExp';
I've also added a diagnostic warning message in Inline.pm that will appear
only if the M62 fatal error message is about to be invoked.
This might give me something to work with if ever that fatality happens
again. To date I've only seen that error happen with
http://www.cpantesters.org/cpan/report/3287249c-5151-11e1-9dba-4238887bd19e
.
No plans to make another stable release any time soon .... subject to
change, of course :-)
Main aim is to give people plenty of time to try out those ParseRegExp.pm
changes if they so desire.
Cheers,
Rob