Perhaps a simple link to the repository would have been more useful
XS.c is a file that's generated during 'make', so it's quite likely not sitting in a publicly available repository.
But, yes - it's a pity the closing </code> was omitted.
Doing a diff -EBwbu detects a difference, but without the formatting of the OP's XS.c, I've no idea where that difference lies.
I'm certainly curious to know what the difference is ... though I don't assume that such knowledge will prove to be useful.
I take it that there's no easy way for me to view the file correctly formatted, and that I just have to wait for the OP to insert the missing </code>.
Please correct me if I'm wrong.
Cheers,
Rob | [reply]
[d/l]
[select] |
I suppose if I had read a bit more carefully, I would have been alert to the fact that XS.c is an on-the-fly file generated during build.
Unfortunately, the vast, unreadable nature of the post was just what would tempt me to make a hasty, grumpy reply, hit the downvote button and move on. I was tempted and I fell. Maybe in future I'll be more likely to investigate further before responding irascibly. :)
Give a man a fish: <%-{-{-{-<
| [reply]
[d/l] |
