You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes when writing C code inline you want to make a 'private' function which will be called only from C code and not from Perl. You can stop Inline::C from seeing it by changing to K&R declaration style or other manoeuvres that stop the parser recognizing it. But it would be cleaner to have an explicit way:
/* no Inline */ void foo(int x) { ... }
The text was updated successfully, but these errors were encountered:
Having never used K&R style declarations until today, I didn't realize they had that effect - it's handy to know:
/* unbound */ void foo(x) int x; { ... }
That seems good enough for short argument lists - a bit tedious for lengthy argument lists, I guess.
Sometimes when writing C code inline you want to make a 'private' function which will be called only from C code and not from Perl. You can stop Inline::C from seeing it by changing to K&R declaration style or other manoeuvres that stop the parser recognizing it. But it would be cleaner to have an explicit way:
/* no Inline */ void foo(int x) { ... }
The text was updated successfully, but these errors were encountered: