4 ms·

I couldn't agree more. As someone who deals with implementing and customising 3rd party libraries a lot, it's highly frustrating when things are private just fo

I couldn't agree more. As someone who deals with implementing and customising 3rd party libraries a lot, it's highly frustrating when things are private just for the sake of it. Things should be made private when there's a specific way of accessing/altering that variable, not because you don't think anyone will need it.

phaylon 16y ago
Not sure I agree. As soon as something is public, it's part of the interface. That means the usual rules of stability/back-compatibility will apply to it as well. If you don't want that, or you're not sure you want that, then that's a valid reason to make something private in my opinion.