Changes between Version 2 and Version 3 of soc/2007/UserFriendlyGraph

Timestamp:

May 11, 2007, 1:57:24 PM (15 years ago)

Author:

Andrew Sutton

Comment:

--

soc/2007/UserFriendlyGraph

@@ -26 +26 @@
 
 A second design approach uses composition as a member rather than private inheritance - not for any particular reason, I'm just more familiar with composition. Now, the prototype looks like this:
-
 {{{
 #!cpp
@@ -61 +60 @@
 On a side note, I started codifying the Boost.Graph graph concepts into a concepts header just to see if I could make it work - I haven't succeeded yet. Still, it's a good excercise and makes you think about concept hierarchies, nested requirements and the like. Also, i don't like the keyword `concept_map`. Not the idea itself - the keyword. If I'm not mistaken, this keyword replaces `model` from earlier proposals. Alas...
 
-Since I've been codigying graph concepts, I should point out that ''IncidenceGraph'' and ''EdgeListGraph'' both define `source()` and `target()` methods, so they're a little redundant. I think it would be appropriate to remove those methods from the requirements of ''EdgeListGraph'' since they don't really have anything to do with the listing or enumerating of edges. Just a thought... 
+Since I've been codigying graph concepts, I should point out that ''!IncidenceGraph'' and ''!EdgeListGraph'' both define `source()` and `target()` methods, so they're a little redundant. I think it would be appropriate to remove those methods from the requirements of ''!EdgeListGraph'' since they don't really have anything to do with the listing or enumerating of edges. Just a thought... 
 
 == Documentation and Other Niceties ==