|Do you know where your variables are?
I'm wondering what performance penalty I'm paying for including documentation in my Perl CGI scripts, using either =pod or sequential #'s. A new project has grown to the point where good docn will be essential for ongoing maintainability. An obvious solution would be to compile the Perl into e.g. C executables, but I've no experience with this, or any similar technique. Would those with experience in this area kindly care to comment for both my own enlightenment and that of other Supplicants? With thanks for any replies.
In reply to Performance penalties of in-Perl docn vs compiled CGIs. by phirun