Re: [boost] [Property Map] LvaluePropertyMapConcept problem

Hi Stephan, The immediate problem is that you should be using the Mutable_LvaluePropertyMapConcept instead of LvaluePropertyMapConcept. However, I think there may also be a problem with the concept design. Comparing to the iterator concepts, we always have the Mutable version of the concept be a refinement of the not-necessarily mutable version. I think it would be appropriate to change LvaluePropertyMapConcept to require the reference to be convertible to the const&, but not require same type. Cheers, Jeremy __________________________________ Jeremy Siek <siek@cs.colorado.edu> Visiting Assistant Professor Department of Computer Science University of Colorado at Boulder

Hi Jeremy, 2006/9/5, Jeremy Graham Siek <jsiek@osl.iu.edu>:
Hi Stephan,
The immediate problem is that you should be using the Mutable_LvaluePropertyMapConcept instead of LvaluePropertyMapConcept.
This solves the initially posted example, thanks. [snip]
I think it would be appropriate to change LvaluePropertyMapConcept to require the reference to be convertible to the const&, but not require same type.
This would be nice. I'm using that check in the maxflow algorithm where I get some of the property maps as consts. Btw, that's how I came to that problem. Your suggestion solves that. Thank you! Cheers, Stephan
participants (2)
-
Jeremy Graham Siek
-
Stephan Diederich