Consistent use of shared_ptr
Registered by
Anders Logg
The use of shared_ptr in the C++ interface is inconsistent. We should strive to use boost:shared_ptr uniformly throughout all classes, but provide simplified constructors (reference_
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
GNW: Simplified reference constructors should be minimised since they require hand-modification of the SWIG layer, which it not done will cause Python memory errors.
(?)