----- Original Message -----
From: "Erik Hollensbe" <[EMAIL PROTECTED]>
.
.
Technically I have a working product at this point, however I'd
really prefer to not use a heredoc. I imagine it's something very subtle
(e.g., I snipped the POD in the document but there is an __END__ in there,
maybe that's confusing Inline). I've got some other matters to attend to
today and will give it a solid try in a few hours.
A couple of other things (which you may already be aware of):
To the Inline CPP config options add
BUILD_NOISY => 1,
CLEAN_AFTER_BUILD => 0,
The first will let you see any compiler warnings that are issued during the
compilation phase - otherwise you only get to see them if the compilation
fails.
The second will allow you to go into the build directory and take a look at
the files (especially the .xs and .def files) that inline wrote - otherwise
those files get cleaned up when the compilation has succeeded.
Neither of these options will probably help all that much in this particular
case - though the "CLEAN_AFTER_BUILD => 0," will at least enable you to
verify that the XS files that are being written in both cases are the same.
I think they'll be different. Typically, one (the "file" version) will
terminate with "PROTOTYPES: DISABLE" and the other ("heredoc" version) will
have stuff below the "PROTOTYPES: DISABLE" line. (That's just a guess - and
it doesn't really say anything useful about how to fix the problem :-)
Cheers,
Rob