As I stated, these routines were written before CGI.pm became a standard module and we also have > 250K lines of perl code built on top of it just for one installation I reviewed.

Anyway, for people wanting a non-CGI.pm way to do things, we've used this routine for billions upon billions of page views. That's what he asked for, that's what I sent him.

PerlCMS (where this routine came from), is our framework. I hope to open source it sooner rather than later for many reasons, one of them being that it solves a lot of problems that other frameworks do not. The other being, as you said, being able to get people that are trained in it. The foremost being that peer review and other people adding to the code is beneficial to everyone.

However, with regards to people trained in one library or another, fundamentally my view is that programming is a state of mind, not a language. A "real" programmer should be able to come up to speed easily in about a week in almost any programming language with a little bit of source code to look at, a peer to point him in the correct directions and a few syntax books for reference.

Regards,
KAM

----- Original Message ----- From: "Perrin Harkins" <[EMAIL PROTECTED]>
To: "Kevin A. McGrail" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <modperl@perl.apache.org>
Sent: Thursday, August 31, 2006 2:09 PM
Subject: Re: Receiving user input


On Thu, 2006-08-31 at 12:45 -0400, Kevin A. McGrail wrote:
Attached is our function that we use both under mod_perl and standard
perl.

No offense, but you'd be much better off using one of the standard
parsers, like CGI.pm or libapreq.  These get a lot of peer review and
the bugs have been pretty well shaken out over the years.  If you think
it's easy to get these things right, take a look at the CGI.pm
changelog.

- Perrin


Reply via email to