Changes between Version 9 and Version 10 of Notifications
- Timestamp:
- Jun 21, 2015, 4:58:17 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Notifications
v9 v10 22 22 As usual, the deleted items is the tricky part. My proposal is this: The deleted items is a set containing all the individual Python objects that had already been created at the time they were deleted. There would also be an accompanying integer noting the total number of deleted items. My reasoning is that no code is going to care about individual deleted Python objects that had never been created at the time they were deleted. Keep in mind that collections automatically contract when their members are deleted. I propose we add a callback API to collections so that interested code can respond to such a contraction if desired. 23 23 24 Also keep in mind that i s possible to ask individual objects if they are "dead" since their C++ pointer will be NULL, so some code may not even look at the set of deleted items and will instead just cull their own lists/etc. based on that criteria.24 Also keep in mind that it is possible to ask individual objects if they are "dead" since their C++ pointer will be NULL, so some code may not even look at the set of deleted items and will instead just cull their own lists/etc. based on that criteria.