AUTOLOAD

[Luis Motta Campos]

On Jan 18, 2007, at 6:54 PM, Daniel Barlow wrote:
> Luis Motta Campos wrote:
>> I wish I could just say
>> something like
>>
>>   use shotgun ':when needed';
>>
>>   and have perl shoot down uneducated code. For example, preventing
>> people from accessing my private methods (tagged as ":private" on sub
>> declaration),
>
> See, I don't understand why you'd care.  I don't mind if people access
> my private methods: I'm not infallible, they may well have a  
> problem to
> solve that can't be done otherwise and that didn't occur to me when I
> designed the public interface.  Perhaps they could send me a patch and
> wait for me to incorporate it into a newer version, but my guess is  
> that
> they'd rather work to their priorities not mine.
>
> I *do* mind if they come whinging to me if/when a later version breaks
> their code.  I told them the method was private, they're on their  
> own if
> they decide to use it anyway.  But that's mostly a social problem,  
> not a
> technical one.

   This is also a technical problem, because I have trouble keeping  
developers away from my private methods at my current job. And this  
means that I will be called in the middle of the night to solve a  
problem that I didn't created. This is annoying, and maybe the best  
solution was just find another job, but this is not solving the problem.

   I won't mind about someone that grabs a module I published on CPAN  
and does nasty things like this. They're on they on, and are supposed  
to know what they are doing.

   I guess you're not totally wrong after all: mine is a liability  
problem: I won't to be liable for one's faults, and would like to  
keep the good job I do (and like doing). This is, at last, a social  
problem.
--
Luis Motta Campos is software engineer,
perl fanatic evangelist, and amateur {cook, photographer}