try Perl_warn(...
I did. But have you ever looked at what lies behind that seemingly simple call? Debugging tools need to be simple and reliable, and Perl_warn() is neither.
When the simple act of adding the trace statement to a routine can cause it to go belly up, and the only way to track down why involves /E and wading through megabytes of post-processed C code to work out what actual code gets run, sticking to printf() is infinitely preferable.
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.
| [reply]
[d/l] |