> Looks good to me, although I'm not sure how you're going to go from a string
> argument to Log::Any::import() to creating a lexical in the calling packing
> and then snagging a reference to it. Evil PAD manipulation? Source
> filters? Or will you simply use a package global instead? (That'd be fine
> with me.)
The latter - in the case of
use Log::Abstract qw($log $log_is_debug);
both $log and $log_is_debug will be imported as package globals. It
seems like a reasonable trade-off for the convenience.
Then, we have to keep track of every $log_is_debug type variable that
we've handed out, so we can change it on the fly if necessary. People
would have to refrain from copying or passing this variable around by
value, lest it lose its "dynamic" property. Also not ideal, but the
best we can do and still preserve optimal performance.
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
