jrsmith has asked for the wisdom of the Perl Monks concerning the following question:
I'm working on an average-sized CGI app using CGI.pm and DBI, amidst other less relevant modules. It makes heavy use of tables and class definitions, and I'm currently printing them all out using heredocs.
I'm using CGI.pm to handle cookies and POST variables, but my question is, is there any compelling reason for me to go back through and change all of my working HTML heredocs to their CGI.pm equivalents? Keeping the HTML cross-platform isn't a concern.. This is going to be intranet-only in an all-Microsoft company, and I've been fairly conscious of compatibility issues when coding.
This is something I've always wondered about, since everyone always shouts "Use CGI.pm!!" when a CGI question is asked, and I whole-heartedly agree when it comes to form parsing and cookies, but is it a big deal to just print out your HTML?
I'm using CGI.pm to handle cookies and POST variables, but my question is, is there any compelling reason for me to go back through and change all of my working HTML heredocs to their CGI.pm equivalents? Keeping the HTML cross-platform isn't a concern.. This is going to be intranet-only in an all-Microsoft company, and I've been fairly conscious of compatibility issues when coding.
This is something I've always wondered about, since everyone always shouts "Use CGI.pm!!" when a CGI question is asked, and I whole-heartedly agree when it comes to form parsing and cookies, but is it a big deal to just print out your HTML?
Back to
Seekers of Perl Wisdom