> > This seems kind of silly. Can anyone explain to me why this is? > > Because if you do : > > use CGI qw(param); > - It will work > - Implemented the same in every script in every server > - people will understand what you're doing > - it's reusable over and over and over > - it's platform independant > - can still create the hashes you want (for whatever reason you need that, why would you btw?) > > If you do some home brewed parsing (Like we did back in the day) > It ends up: > - Breaks easily > - May need implemented differently on different servers > - Hard to maintain > - Recreating the wheel over and over and over. > - Not portable > - can create the hashes you want but how do you know you're getting the actual form input or some butchery of improperly encoded/unencoded > > That's a just a little input, I'm sure there's lots more than that but I'm busy. > > If you explain why you need the %POST and %GET hashes specifically maybe we can help you do it the best way. > So whjat are you trying to accomplish with those hashes? >
All of what Dan said is correct and very good reasons, but the proof lies in the code. Crank open the CGI.pm's source and look at it yourself, it is the best indication of why you shouldn't. If you think you would have thought of every little possible contingency etc. that is wrapped up in that code then by all means do it yourself.... I suspect your comment about wanting "%POST and %GET" has more to do with the 'and' than the values on either side. If my assumption is correct and you are passing *both* values in the content body and in the url header then I believe you are forming a non-standard HTTP request which is why CGI.pm doesn't have (at least I don' think) a way to pull both sets of data. So the real answer is don't do it that way as it is a poor design issue, however, not all design issues can be fixed, so to hack around it I suspect you could pull out the POST data, then grab the actual full URL then pass it back through CGI's private methods to grab the data that is there also and combine the two... But I am guessing.... http://danconia.org -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
