NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
A question then... (Score:1)
At least, that is where I think I saw it...
Re:A question then... (Score:1)
Yep, it's part of the standard header in all of his programs, not just his CGI ones. (If you read more than one of his columns, he copies and pastes that explanation.)
I think it's an unnecessary pessimization in terms of clarity and performance. Most of the time, buffering isn't a problem. Only change the default when it is.
only when necessary (Score:1)
This seems like an excellent rule of thumb even for a more general context. Maybe I'll leave "use strict; use warnings;" out of my templates and only put them in code while its tests aren't passing.
(I'm only about 20% serious.)
Reply to This
Parent
Re:only when necessary (Score:1)
Ah, but my default rule of thumb has an implicit "Assuming the default is good and useful..." preface. I can see now that my buffering rule of thumb is one of the 20% of cases where that clause should be explicit.