A late thought, but since I am one of thow whose' keen on the
print,next if /stgh/;
Ouch. I hadn't thought of that. I'm a big fan of litering loops with
discard(),next if dontCareBecause(); # it don't matter here
type constructs. I was going to suggest
print and next if /stgh/;
but there is a difference that will probably bite you when you least expect it. You could say
(print or 1) and next if /stgh/;
but not we are in the areas of pointlessy ugly hacks. I could live with
do{print;next} if /stgh/;but the do just feels over verbose. So do the braces. Can next be used in numeric context?
(print) + (next) if /stgh/;
hmm. ug. Never mind. Oh! I've got it!
eval "print;next" if /stgh/;
no. That as bad as do, 'cept differnt. I give up.
Dan
