I apologize if I'm too blunt. I think there's a point that needs to be made clearly here.

Let me ask a few questions, please. Have you tried POD? Have you found it lacking in some way? If POD is an issue, does your text editor not allow you to automatically insert hash signs at the beginning of a line?

Please don't take this the wrong way, but I'm honestly not sure if the quality of your code is all that important. Perl has both its own comment syntax and an expanded comments standard that can automatically be turned into documentation (POD).

While it's true that TIMTOWTDI, bringing in C, Pascal, C++, Basic, and COBOL methods of making comments and adding runtime complexity to projects in order to avoid becoming comfortable with Perl's own strengths and customs seems like overkill.

While I do think there could be a use for your module, I think that use would be simply to guide C programmers who are new to Perl into their own programming backwater that discourages them from using POD. They and the Perl community would be poorer for that happening.

Basically, not only are you trying to solve a solved problem, but your module could actually have a negative impact both on the projects using it and the programmers who find it before they take the minimal time involved in learning basic POD skills.

I applaud your desire to help out and the work you put into making this a CPAN module. I just think this particular module was a little misguided.