Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

samtragar has answered the question, but to be able to discover this for yourself, you'll need to add some options to the build process so that the intermediate files are retained and you can inspect them. Something like this is useful:

use Inline 'NoClean', 'FORCE', 'INFO' ; use Inline Config => WARNINGS => 4; use Inline 'C' => <<CEND, NAME =>'yourname'; ...

Note: I've also attempted to enable warnings above. It doesn't work, or at least they are not displayed when the program is built. If they were, the C compiler would have warned that you were assigning a SV** to an SV*.

The only way I have found to get the warning displayed on my system is to deliberately include a fatal error. A line like fred; will give an error

test.xs(13) : error C2065: 'fred' : undeclared identifier

And the warnings will also be displayed.

There has to be a better way, but I haven't found it.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re: Inline::C - object accessor failure by BrowserUk
in thread Inline::C - object accessor failure by fireartist

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (3)
As of 2023-09-26 19:12 GMT
Find Nodes?
    Voting Booth?

    No recent polls found