Re^3: "Accessors (don't always) break encapsulation"

[Ovid]

Actually, I wasn't referring to those modules at all. Ignoring potential issue with premature optimization -- issues that I feel are more significant in Perl as it's rather slow and we don't have lazy evaluation -- if a logging module is there to allow the user to log stuff, then of course we need to figure out whether or not it's appropriate to call the method. In the example I used, it was a hypothetical example regarding something the programmer shouldn't have to worry about. In your example, you present an external API that the programmer should decide whether or not to call because that's the entire rationale behind the module.

Sorry if I wasn't clear.

[diotalevi]

We sure do have lazy evaluation!

$obj->log_error( promise { Dumper($some_very_large_structure) } );

package Promises;
use overload( '""' => sub { $_[0]->() } );
sub promise (&) { return bless $_[0], __PACKAGE__ }