[Lemon-devel] Renaming basic classes

Balazs Dezso deba at inf.elte.hu
Tue Sep 18 16:04:42 CEST 2007


Hi,

I think we could step into the finalization of the renaming debate. The 
current state of names:

Graphs:
Graph, Ugraph, Bigraph

Items:
Node, Arc, Edge, Anode, Bnode

Edge end-node query:
either(), other()

Any opposition?

I got an issue about the Anode is meaningful word and therefore it might be a 
bad choice. In addition I would like to revise my proposal about other(), 
either()... I thought it will be refused because I was not sure that these 
are proper names. The main problem is that they do not denote that it gives 
back the end node of the edge. Eventually, I think that these are the best 
names (after anode(), bnode() but these are quite antipathic for you), and 
the complete signature of the function express the meaning of these 
functions.

Has somebody additional issue about graph redesign, i.e. the graph iterators 
and maps get out from the graphs and the most of the extender functionalities 
are unnecessary? (the alteration notifiers should be stay in the graphs, 
member data!) Who want it and who refuse it?

I would like to start an other topic about we would like to have a complete 
wikipedia page. Could somebody make it? (Peter, please...)
The main points of the wikipedia site could be:
1) Introduction:
Graph Library, open source, bsd-style license, network optimization
2) Design:
Generative programming, C++ templates, concepts, concept checking, algorithm 
classes
3) Algorithms:
As in the modules page + Approximation algorithms + Heuristics + LP/MIP 
interface
4) Additional tools:
Eps, Lgf, Measurement tools, 
5) Links and related resources
Other graph libraries
Lemon site, Boost, Leda, Goblin, GTL

Best, Balazs



More information about the Lemon-devel mailing list