in reply to Re^2: Why can't I call a C subroutine using Inline-C module?
in thread Why can't I call a C subroutine using Inline-C module?

My guess would be that this is because main is special (the entry point of an executable).

Yes - I was a little surprised that the 'main' name didn't cause problems on Windows. Of course, I haven't tested it out extensively but there's certainly no problem for me (on Win32) with the code you just posted.

I've only just now given it a run on linux. Won't build for me - I get all sorts of bizarre errors that don't even warrant thinking about. (Naming the function "main2" works fine.)

Cheers,
Rob
  • Comment on Re^3: Why can't I call a C subroutine using Inline-C module?

Replies are listed 'Best First'.
Re^4: Why can't I call a C subroutine using Inline-C module?
by BrowserUk (Patriarch) on Mar 05, 2010 at 09:19 UTC

    The reason it works on Windows, is because of the old exports thing that prevents Windows seeing unauthorised Perl APIs.

    Windows doesn't export the I::C subroutines from the DLL, they're all looked up through a single entrypoint (boot_projectName).

    They are look up in the same way under linux, but they are also exported from the .so. And when main is exported, it is special at the linker stage.

    That's probably not the whole story, but I think it is the crux of it.

    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]

In Section Seekers of Perl Wisdom