Post Made Community Wiki by Dale
2 added 433 characters in body
source | link

I'd hope that anything that the IDE developed by the company that develops your programming language auto generates doesn't violate the "Principles of Object Orientation".

That being said, any time you've got a public scoped variable, use a getter and a setter and you're golden. Seems to me to be the necessary element of the extremely object oriented principle of encapsulation - even if it just looks like a lot of junky code.

The reason to use them is that the proper encapsulation may yet take place and so long as you've abstracted away the layer that lets the person monkeying with your object feel your object, you can take that object away without him even knowing right?

Suffice it to say, a house divided cannot stand, one of the tenants of OO isn't going to turn on itself and you can't serve both encapsulation and premature optimization.

I'd hope that anything that the IDE developed by the company that develops your programming language auto generates doesn't violate the "Principles of Object Orientation".

That being said, any time you've got a public scoped variable, use a getter and a setter and you're golden. Seems to me to be the necessary element of the extremely object oriented principle of encapsulation - even if it just looks like a lot of junky code.

I'd hope that anything that the IDE developed by the company that develops your programming language auto generates doesn't violate the "Principles of Object Orientation".

That being said, any time you've got a public scoped variable, use a getter and a setter and you're golden. Seems to me to be the necessary element of the extremely object oriented principle of encapsulation - even if it just looks like a lot of junky code.

The reason to use them is that the proper encapsulation may yet take place and so long as you've abstracted away the layer that lets the person monkeying with your object feel your object, you can take that object away without him even knowing right?

Suffice it to say, a house divided cannot stand, one of the tenants of OO isn't going to turn on itself and you can't serve both encapsulation and premature optimization.

1
source | link

I'd hope that anything that the IDE developed by the company that develops your programming language auto generates doesn't violate the "Principles of Object Orientation".

That being said, any time you've got a public scoped variable, use a getter and a setter and you're golden. Seems to me to be the necessary element of the extremely object oriented principle of encapsulation - even if it just looks like a lot of junky code.