More options are always welcome, so long as they're easy to specify. Incidentally, I believe there was a problem with placing edge_index_t edge_index in the bundled properties----it only worked when I used the (far uglier) joint internal/bundled property approach. Something else to put on the list.
The intention with regards to properties was never all that clear to me from the documentation, to be honest.
I *thought* that each subgraph would have a local copy of all properties (as they were at subgraph creation time) and the modifying these would not change the properties of the corresponding global vertex/edge, and my code actually relies on this.
Am I going to have to change my code design, either to accommodate the current design or a future fix?
Me neither. This is really my first time digging into subgraph. It makes sense (to me) that each vertex/edge should have only one property, but I can see reasons for localizing properties as well. If both are needed, I can create specializations of property_map that select local/global lookup strategies. Would that be acceptable? Andrew Sutton andrew.n.sutton@gmail.com _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users