Thanks all for your valuable input.
I think my situation falls into David's category c. And if I
understand the difference between 'use' and 'require' here, the former
forces the module to be loaded at compile time, while the latter does
not. Is that correct?
On Tue, Jun 29, 2010 at 4:21 PM, Eri
# from David Golden
# on Tuesday 29 June 2010 13:17:
>>... and each appender can be individually toggled on or off ...
>> ... whether I want the issue detected at compile time or run time I
>> suppose, but is generally frowned upon to put imports down inside
>> class methods?
>
>I tend to think ab
On Tue, Jun 29, 2010 at 2:37 PM, Matt Grimm wrote:
> For example, I have a logger class wrapped around Log4perl that
> supports screen, email, and syslog appenders, and each appender can be
> individually toggled on or off. Is it better to force the dependencies
> on the underlying syslog and emai
Quoth matt.t.gr...@gmail.com (Matt Grimm):
> What is the conventional wisdom (if any) for handling conditional
> dependencies in modules?
>
> For example, I have a logger class wrapped around Log4perl that
> supports screen, email, and syslog appenders, and each appender can be
http://xkcd.com/754/
On Tue, Jun 29, 2010 at 11:37 AM, Matt Grimm wrote:
> What is the conventional wisdom (if any) for handling conditional
> dependencies in modules?
>
> For example, I have a logger class wrapped around Log4perl that
> supports screen, email, and syslog appe
What is the conventional wisdom (if any) for handling conditional
dependencies in modules?
For example, I have a logger class wrapped around Log4perl that
supports screen, email, and syslog appenders, and each appender can be
individually toggled on or off. Is it better to force the dependencies
