Re: Passing Arguments With Perl/Cgi

No No No, listen to chromatic and the others. :) use CGI; It may be uncomfortable using modules, but it IS neccesary for two reasons: 1> no need to reinvent the wheel EVERYDAY for the rest of your life, and 2> you are not at a point where you will right BETTER code than in the modules. One of the most attractive features of the Perl universe is that there are always smarter people out there willing to "hook you up". (= but since I know you won't listen to what I just typed, this will be useful:

$stringNEE=~s/%(..)/pack("c",hex($1))/ge;
$stringNEE=~s/+/ /g;
[download]

Comment on Re: Passing Arguments With Perl/Cgi Download Code

Replies are listed 'Best First'.
Smarter People :) by chromatic (Archbishop) on Mar 19, 2000 at 10:43 UTC
That last one should be: `$stringNEE =~ tr/+/ /;` (It's a LOT faster to use tr/// than s///g.)	[reply] [d/l]
RE: Re: Passing Arguments With Perl/Cgi by ldh (Initiate) on Mar 20, 2000 at 13:42 UTC
while it may be necessary and uncomfortable to use other peoples code, i do belive that it is a good idea to know what the code you are using is doing. When I first used modules I was completely unfamiliar with what I was doing with them, I was just using regurgitations of what other people had done. when I realised what the area of the module that I used a lot did, I became more (ahem)enlightened(sorry.) to what the uses of perl were. so, by questioning the module and asking/researching what it was doing in certain stages I could develop a greater understanding of the language. BTW, I am a fairly extensive module user, but I still sit down and research what one will be doing if I use it a lot.	[reply]