Warp escreveu:
> Nicolas Alvarez <nic### [at] gmail com> wrote:
>> Warp wrote:
>>> It breaks modularity badly. The whole idea of data hiding is that the
>>> private part should be completely opaque to the outside. The second it
>>> isn't, outside code will start making assumptions, and you can't change
>>> the implementation of the class anymore.
>
>> You CAN change the implementation of the class. It's not your problem if you
>> break code that made assumptions.
>
> I don't think that's a good programming principle.
Me neither. But that's a bad programming principle by the dumbass
accessing stuff it shouldn't. It's not your fault as the module
provider and is beyond your control.
Post a reply to this message
|
