|Problems? Is your data what you think it is?|
Re^2: Using stderr from Inline::C: (part deux)by BrowserUk (Pope)
|on May 23, 2013 at 12:05 UTC||Need Help??|
(IIRC, you're not a big fan of the perlio layer.)
I'm not a fan of anything that imposes itself on me. Even less so when it is done by overriding standard names with text macros.
The latter wouldn't be so bad if it was only done if I explicitly requested it. Say, by adding: #include <perlIO.h> or similar.
It would also not be so bad if it was documented what extra these PerlIO equivalent were doing for me (as opposed to just their existence.). One assumes they must be doing something extra, otherwise there would be no benefit for the cost of all those extra indirections; but I have yet to see what that is documented.
Talking of control, is it possible to avoid/prevent I::C from automatically adding the standard Perl/XS headers to my I::C code?
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.