You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/lectures/oop/properties.md
-8Lines changed: 0 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -259,8 +259,6 @@ The benefit of this notation is that read-only properties can easily be integrat
259
259
+ «get» Radius : decimal
260
260
```
261
261
262
-
<!--
263
-
264
262
## Properties and Security
265
263
266
264
*The following discussion is related to the general topic of [`try-catch-finally` scope](../misc/exceptions#scoping-in-try-catch-finally-statements) but can be read independently.*
@@ -294,9 +292,3 @@ Where the last line indicate that the attribute *was set to `"Forbidden word"`!*
294
292
295
293
The correct fix is to **first test, then set**, so that an incorrect value would **never be assigned**.
296
294
In the previous example, simply moving `sensibleData = value;` to the end of the `set` would fix this issue.
0 commit comments