[YANGTOOLS-739] ObjectRegistration should not allow null objects Created: 27/Jan/17 Updated: 10/Apr/22 Resolved: 29/Jun/17 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Robert Varga | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 7698 |
| Description |
|
Null references are overall evil and allowing them to pass through registration objects results in unpredictable failures in code executing after the registration is done. Do not allow AbstractObjectRegistration to be instantiated with a null object and document ObjectRegistration as returning non-null instance. |
| Comments |
| Comment by Robert Varga [ 27/Jan/17 ] |