| |
| |
| |
|
Comments:
<0> hi all ! <1> hi <0> <1> do you speak english ? <1> no
<0> <1> sorry, do you speak russian ? <1> neither <0> ? <0> - - ? <2> What ever happened to PerlCure? <3> What ever happened to bynari? <4> How do I put a reg exp in a hash? Do I need quotes? <5> how so? just the regex itself? what will you do with it? <4> I'll pull it out in a loop and use it agaist a webpage <4> reg1 => '<a href="(.*?)"', <4> and I don't think thats the right way <4> actually its a hash to a hash to the reg exp
<5> mm...i can't say i've tried that before <4> I have, but I totally forget how to do it :P <6> If you're parsing HTML, why aren't you using one of the HTML parsing things on CPAN? <6> generally qr// is preferable for storing regexes <6> And not storing regexps in hash keys may be preferable too. <4> qr//? Hmmm <6> (values have no penalty but keys are always stringified and so can't have precompilation advantages). <4> errr it is a value, isn't it? <4> reg1 would be the key and the regexp would be the value <4> sorry if I'm dumb :P <4> I'm checking content on alot of webpages, so I an easy way of looking up which regexp to use with a certain webpage <6> Only the first part of an s/// is a regex, and qr// is a shorthand for qr/REGEXP/ and variants with other delimiters and s///, m//, qq//, etc. are all similar. <6> If your regexp needs to change based on the values of other data, perhaps you want to store subrefs instead, anyways. <4> hmmm never used subrefs before, lemme look it up <4> haha nm it works, I just was using $_ instead of $1 :P
Return to
#perl or Go to some related
logs:
pal do pal ka shayar hu kitne shayar aaye aakar chale #linux #india #india #linux sudhir gandha #india eric4 gentoo #allnitecafe Dantemi
|
|