I think the best way to enable Inline::C using #line directives would be to implement an xsubpp (== ExtUtils::ParseXS) option to NOT generate #line directives. That shouldn't be hard.

...

Oops! Turns out that's already done! Check out the linenumbers option. I haven't tested it, though.

This being said, I believe Inline::C is a deployment nightmare and should be avoided outside experiments accordingly.

Once you learned the C and perlapi stuff to write Inline::C, XS is child's play.

Check out the linenumbers option.

What "linenumber options"? Options to what?

I believe Inline::C is a deployment nightmare ... XS is child's play.

Inline::C is a much nicer development environment than XS. Edit -> Run; Edit -> Run.

Just like using your favourite dynamic language except for a somewhat extended delay and some annoying trace output.

The only thing that's missing is a "BUILD_DISTRIBUTION => 1" config flag, then it would be perfect.

In theory, automating the generation of a distribution should be simple. At least for anything that doesn't use external libraries.

---

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.

Thanks for quoting a part of my post when the preceding text makes it clear what the option refers to. Or so I assumed. The answer is, of course, xsubpp / ExtUtils::ParseXS.

As for BUILD_DISTRIBUTION, have you seen InlineX::C2XS InlineX::XS?