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
Is your feature request related to a problem? Please describe.
All OSAL objects share a basically common pattern for finalization after creation and deletion. For creation the finalization was consolidated into a OS_ObjectIdFinalizeNew routine, but the deletion finalization is basically repeated as it only involved clearing a single global.
Describe the solution you'd like
Even though deletion is currently trivial, it is beneficial to consolidate this code as it could become less trivial, as in issue #540
This is a necessary prerequisite in order to implement any sort of common/generic handling without repeating the code everywhere. It also makes deletion more of a mirror-image of creation, which is really the way it should be.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
Remove repetitive clearing of the global ID and unlocking
global table and replace with common implementation in the
idmap code. In addition to removing repeated logic, this
makes deletion more like an inverse of creation, and provides
a common/single point where additiona deletion-related
logic can be added.
Remove repetitive clearing of the global ID and unlocking
global table and replace with common implementation in the
idmap code. In addition to removing repeated logic, this
makes deletion more like an inverse of creation, and provides
a common/single point where additiona deletion-related
logic can be added.
Remove repetitive clearing of the global ID and unlocking
global table and replace with common implementation in the
idmap code. In addition to removing repeated logic, this
makes deletion more like an inverse of creation, and provides
a common/single point where additiona deletion-related
logic can be added.
Is your feature request related to a problem? Please describe.
All OSAL objects share a basically common pattern for finalization after creation and deletion. For creation the finalization was consolidated into a
OS_ObjectIdFinalizeNew
routine, but the deletion finalization is basically repeated as it only involved clearing a single global.Describe the solution you'd like
Even though deletion is currently trivial, it is beneficial to consolidate this code as it could become less trivial, as in issue #540
Additional context
This was split from #540
This is a necessary prerequisite in order to implement any sort of common/generic handling without repeating the code everywhere. It also makes deletion more of a mirror-image of creation, which is really the way it should be.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: