Hi Jeremy. As long as I have your attention, I'll take this opportunity to ask a question. Why do you think assuming EdgeContainer::size_type is independent of the edge type is a better solution than simply defining edges_size_type as unsigned long or size_t? I think your assumption is likely to be valid, but wouldn't unsigned long be large enough to hold the number of edges in every case? Maybe I'm answering my own question, but the only case I can think of where unsigned long might not be large enough is if the adjacency_list user specialized container_gen for some custom container where size_type is a "big integer" class. Is this the scenario you had in mind? Thanks, Daniel On Saturday 22 April 2006 17:39, Jeremy Siek wrote:
I made the assumption that instantiating the edge container, whatever it may be, on a dummy type, will have the same size_type as the edge container instantiated on the edge property.
Cheers, Jeremy
On Apr 22, 2006, at 5:32 PM, Daniel Mitchell wrote:
On Saturday 22 April 2006 08:44, Jeremy Siek wrote:
Good idea. I've added edges_size_type and vertices_size_type to adjacency_list_traits in CVS.
Hmm... I can't see your changes since they aren't showing up in webcvs, but I'd like to know what you did, given that edges_size_type depended on the type of edge properties.
Daniel _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users