#166: Revamp util::complex --------------------------+------------------------------------------------- Reporter: levill_r | Owner: levill_r Type: enhancement | Status: new Priority: major | Milestone: Olena 1.0 Component: Milena | Version: 1.0 Resolution: | Keywords: --------------------------+------------------------------------------------- Old description:
* As for images, use a `tracked_ptr` to handle the data of the complex, i.e. split the `complex` classe in two: * the complex « shell(s) », holding `tracked_ptr` to shared data; and * the actual complex data (vertices and egdes). Also, handle complexes directly from `p_complex` instead of using a `tracked_ptr`, as copying complexes will become cheap (as for images). * Move complex-related types and routines from `mln/core/` to `mln/topo/`.
New description: * As for images, use a `tracked_ptr` to handle the data of the complex, i.e. split the `complex` classe in two: * the complex « shell(s) », holding `tracked_ptr` to shared data; and * the actual complex data (vertices and egdes). Also, handle complexes directly from `p_complex` instead of using a `tracked_ptr`, as copying complexes will become cheap (as for images). * Move complex-related types and routines from `mln/core/` to `mln/topo/`. * Split files; see `FIXME`s in * source:branches/cleanup-2008/milena/mln/core/complex.hh * source:branches/cleanup-2008/milena/mln/core/face.hh * Address other `FIXME`s in those files (don't hesitate to populate this ticket with their content!). Comment (by levill_r): More to-do. -- Ticket URL: <https://trac.lrde.org/olena/ticket/166#comment:1> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.