blocks|key|1354677|text|getters或setter的要点在于，您仍然可以在一个地方向字段的修改添加逻辑，而不是在想要修改或检索字段的所有地方添加逻辑。您还可以在类级别获得对字段的控制。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1354678|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The point of getters or setters is that you can still add logic to your modifications of the field in one place instead of everyplace you want to modify or retrieve the field. You also gain control at class level what happens with the field.

blocks|key|1569842|text|你有没有考虑过使用魔法函数__set/__get？使用它们，你可以很容易地在两个函数中合并所有的getter/setter函数！|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1569843|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Did you consider to use magic functions __set/__get? Using them you can easily merge all getter/setter function in only 2 functions!

blocks|key|1569877|text|不使用属性访问器的主要问题是，如果您发现以后需要将字段更改为属性-例如，为了使其成为子类中的计算属性-您会破坏API的客户端。对于一个已发布的库来说，这是不可接受的；对于一个内部库来说，只需要做相当多的工作来解决问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1569878|对于私有代码或小型应用程序，只需即兴发挥可能是可行的。IDE+(或文本编辑器)将允许您生成访问器样板，并使用代码折叠将其隐藏。可以说，这使得机械地使用getter和setter相当容易。|1569879|请注意，一些编程语言具有合成默认field%2Bgetter%2Bsetter的功能--+Ruby通过元编程来实现，C#具有自动实现的属性。Python完全避免了这个问题，因为它允许您覆盖属性访问，允许您将属性封装在需要它的子类中，而不必预先操心它。(这是我最喜欢的方法。)|1569880|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The main problem with not using property accessors is that if you find out you ever need to change a field to a property later on – to make it a computed property in a subclass, for instance – you’ll break clients of your API. For a published library, this would be unacceptable; for an internal one, just quite a lot of work fixing things.

For private code or small apps, it could be feasible to just wing it. An IDE (or text editor) will let you generate accessor boilerplate and hide it using code folding. This arguably makes using getters and setters mechanically fairly easy.

Note that some programming languages have features to synthesise the default field+getter+setter – Ruby does it via metaprogramming, C# has auto-implemented properties. And Python sidesteps the issue completely by letting you override attribute access, letting you encapsulate the attribute in the subclass that needs it instead of having to bother with it up front. (This is the approach I like best.)

blocks|key|1569946|text|如果你经常在脚本中访问这些变量，如果你经常更新你的类，你应该使用setter和getter，因为如果你不这样做，当你改进你的类时，你必须更新所有使用这个变量的文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1569947|其次，你这样做的主要原因是你不应该直接访问变量，因为类结构可能会改变，这些数据可以被提供给differently.While，你从类中获取数据，你不应该关心这些数据是如何产生的，.Class必须关心这种数据处理，所以你只需要关心你会得到什么。|1569948|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you access these variable in your script lots of time and if you update yoru class often you should use setters and getter because but if you dont this , when you improve your class you have to update all files which uses this variable .

Secondly main reason why you do this is you should not access variable directly because class structure may change and this data can be providen differently.While you are getting data from class you should not care about how this data is generated .Class have to care about this data proccessing so you only should care what will you get.

blocks|key|1569997|text|我可能不会在这一点上得到太多好评，但就我个人而言，getter和setter对我来说就像是代码的味道。设计应该是行为驱动的，而不是数据驱动的。当然，这只是一种观点。如果您有一个依赖于另一个对象的特定数据字段的对象，这是非常紧密耦合的。相反，它应该依赖于该对象的行为，该行为远没有其数据那么脆弱。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1569998|但确实，像getter和setter这样的属性是直接依赖于字段的一步，正是出于这个原因。它不那么脆弱，并且松散了对象之间的耦合。|1569999|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I am probably not going to get many upvotes on this one, but personally getters and even more so setters feel like a code smell to me. Designs should be behavior driven, not data driven. Of course, this is just an opinion. If you have an object that depends on a particular data field of another object this is very tight coupling. Instead it should depend on the behavior of that object which is far less brittle than its data.

But yes, property like getters and setters are a step up from a dependency on a field directly for this very reason. It is less brittle and loosens up the coupling between the objects.

blocks|key|1354956|text|有一种方法可以在不实际使用get/set函数类的情况下模拟get/set，因此您的代码保持整洁：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1354957|$person->name+=+'bob';
echo+$person->name;|code-block|syntax|javascript|1354958|看看我编写的this+class。|offset|length|1354959|通常，当使用这个类时，你会声明你的所有属性都是受保护的(或者私有的)。如果你想在一个属性上添加一个行为，比如在"name“属性上添加strtolower()+%2B+ucfirst()，你所需要做的就是在你的类中声明一个受保护的set_name()函数，这个行为应该会被自动拾取。使用get_name()也可以做到这一点。|1354960|//+Somewhere+in+your+class+(that+extends+my+class).
protected+function+set_name($value)+{+$this->name+=+ucfirst(strtolower($value));+}
//

//+Now+it+would+store+ucfirst(strtolower('bob'))+automatically.
$person->name+=+'bob';|1354961|附注:另一件很酷的事情是，你可以编写不存在的字段，比如|1354962|echo+$person->full_name;|1354963|而不需要这样的字段(只要有get_full_name()函数)。|1354964|entityMap|0|LINK|mutability|MUTABLE|url|http://github.com/marioprudhomme/fractal-php/blob/85b9c8f14d6dc66837e36196458dcdeba188b6eb/public/core/library/model.php^0|0|0|6|A|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|14|8|@]|9|@$I|15|J|16|1|17]]|A|$]]|$1|K|3|L|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1A|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1C|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|11]]]]

There is a way to emulate get/set without actually using get/set function class, so your code remains tidy:

<pre><code>$person-&gt;name = 'bob';
echo $person-&gt;name;
</code></pre>

Take a look at <a href="http://github.com/marioprudhomme/fractal-php/blob/85b9c8f14d6dc66837e36196458dcdeba188b6eb/public/core/library/model.php" rel="nofollow noreferrer">this class</a> I have coded. 

Typically, when using this class, you would declare all your properties protected (or private). In the event where you'd want to add a behaviour on a property, say strtolower() + ucfirst() on the "name" property, all you'd need to do is declare a protected set_name() function in your class and the behavior should get picked up automatically. Same can be accomplished with get_name().

<pre><code>// Somewhere in your class (that extends my class).
protected function set_name($value) { $this-&gt;name = ucfirst(strtolower($value)); }
//

// Now it would store ucfirst(strtolower('bob')) automatically.
$person-&gt;name = 'bob';
</code></pre>

P.S.
Another cool thing is you can make up non-existing fields such as

<pre><code>echo $person-&gt;full_name;
</code></pre>

without having such fields (as long as there is a get_full_name() function).

I'm kind of new in PHP. For some reason in other types of programming languages like JAVA I have no problem with using setters and getters for every single variable, but when I'm programming in PHP probably because it is so flexible it feels kind of like a waste of time. It feels simpler to just set the class attributes as public most of the time and manipulating them like that. The thing is that when I do it like this I feel like I'm doing something wrong and going against OO principles. 

Is it really that wrong not using setters and getters? Why or why not? How do you guys do it most of the time?

Is it really that wrong not using setters and getters?

Python

我对PHP还是个新手。由于某些原因，在其他类型的编程语言(如JAVA )中，对每个变量使用setter和getter都没有问题，但是当我使用PHP编程时，可能是因为它太灵活了，所以感觉有点浪费时间。在大多数情况下，只需将类属性设置为public并像这样操作它们会感觉更简单。问题是，当我这样做的时候，我觉得我做错了什么，...

问不使用setter和getter真的有错吗？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问不使用setter和getter真的有错吗？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问不使用setter和getter真的有错吗？
EN