On Thu, 2004-01-22 at 16:49, Dan Muey wrote: > > > But I see a lot of "don't slurp that" and I was hoping for more > > > clear reasons/situatuions to or not to slurp so people > > positn code can have a better idea why a perosn said: > > > "do(n't) slurp your file here" > > > > > > Basically we need to expalin why more: > > > > > > - Don't slurp this because it's STDIN and it may be huge, > > so huge in > > > fact it could overload your system. > > > - If this is an html file you'd probably be safe slurping > > it up to ease it's processing. > > > > I think it's like using a "no warnings" or "no strict" pragma > > to do some dangerous things because you know what you're > > doing. It's there for people when they get advanced enough > > to need it, but it's not a good idea to encourage its use on > > a beginners list. > > > > Good comparison, I never see advice to use no warnigns and no strict though :)
I've actually seen it a few times in code, but it's usually surrounded by: ###################### ###################### #WARNING!!!!!!!!!!!!!! ###################### # Warnings / Strict turned off here because you know what you're doing, right? :-D -Dan -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
