From: "Westgate, Jared" <[EMAIL PROTECTED]> > In fact, I occasionally find myself frustrated with the brevity of > many responses to people's questions. I think a lot of people are > using this list to learn, not just to be told what to do. I'm not > saying to write a novel out of each response, but a little detail can > be nice. You have to remember, a lot of people who are learning Perl > (and even many who are learning English) are using this list.
Than what's easier than to speak up and ask for more details and longer explanation? :-) It's hard to guess how verbose do you need to be so if you find someone too verbose let us all know. > > I dont think the parser is broken, I KNOW it is ;0). Among > > other things, > > this: > > > > > > > @in = split(/&/,$in); > > > > is 'bad, bad, bad, bad, ' x 100_000_000 > > Why is this bad? Don't get me wrong... I'm not saying you are > incorrect, because frankly I don't know. Is it because he is using a > scalar with the same name as the array he is assigning it to? Oh > well, I don't even remember the rest of the code that was posted :) I don't rememer what did the rest of the parser look like, but I don't see anything wrong about this line per-se. (They do declare the @in with my() somewhere above right?) I occasionaly use the same name for scalars, arrays and hashes myself if it makes sense. The problem with parsing CGI query oneself instead of using a module is that the task is a little more complex that it looks at the first glance. And it's easy to think you are safe while you are not. I don't remember the exact problems myself but a little search turned out this: http://www.perlmonks.org/index.pl?node_id=34089 Jenda ===== [EMAIL PROTECTED] === http://Jenda.Krynicky.cz ===== When it comes to wine, women and song, wizards are allowed to get drunk and croon as much as they like. -- Terry Pratchett in Sourcery -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
