Re: Re: Re^2: Private method variations

        $self.bar()           # calls public bar, not private.
[download]

This seems to imply that you can have both public and private methods/attributes with (almost) the same name. Sounds like trouble to me.

duff

Comment on Re: Re: Re^2: Private method variations Download Code

Replies are listed 'Best First'.
Re: Re: Re: Re^2: Private method variations by TimToady (Parson) on Mar 02, 2004 at 00:46 UTC
Gee, you can have scalars and arrays and hashes with (almost) the same name too. Somehow people manage to keep those straight... Really, I think it's a much worse problem to put public and private methods into the same namespace, because then not only do you have to keep the names straight, but anyone who inherits from you has to keep them straight. Private names should not show up in the public interface at all. Even within the class, it's vitally important to be able to distinguish when you're calling yourself privately from when you're calling yourself through the public interface. C++ style rules just make things completely ambiguous, visually speaking. Drives me nuts.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re^2: Private method variations
by TimToady (Parson) on Mar 02, 2004 at 00:46 UTC

Really, I think it's a much worse problem to put public and private methods into the same namespace, because then not only do you have to keep the names straight, but anyone who inherits from you has to keep them straight. Private names should not show up in the public interface at all. Even within the class, it's vitally important to be able to distinguish when you're calling yourself privately from when you're calling yourself through the public interface. C++ style rules just make things completely ambiguous, visually speaking. Drives me nuts.

[reply]