alpar@2391
|
1 |
/* -*- C++ -*-
|
alpar@2391
|
2 |
*
|
alpar@2391
|
3 |
* This file is a part of LEMON, a generic C++ optimization library
|
alpar@2391
|
4 |
*
|
alpar@2553
|
5 |
* Copyright (C) 2003-2008
|
alpar@2391
|
6 |
* Egervary Jeno Kombinatorikus Optimalizalasi Kutatocsoport
|
alpar@2391
|
7 |
* (Egervary Research Group on Combinatorial Optimization, EGRES).
|
alpar@2391
|
8 |
*
|
alpar@2391
|
9 |
* Permission to use, modify and distribute this software is granted
|
alpar@2391
|
10 |
* provided that this copyright notice appears in all copies. For
|
alpar@2391
|
11 |
* precise terms see the accompanying LICENSE file.
|
alpar@2391
|
12 |
*
|
alpar@2391
|
13 |
* This software is provided "AS IS" with no warranty of any kind,
|
alpar@2391
|
14 |
* express or implied, and with no claim as to its suitability for any
|
alpar@2391
|
15 |
* purpose.
|
alpar@2391
|
16 |
*
|
alpar@2391
|
17 |
*/
|
alpar@2391
|
18 |
|
alpar@1624
|
19 |
/*!
|
alpar@954
|
20 |
|
alpar@953
|
21 |
\page named-param Named Parameters
|
alpar@953
|
22 |
|
alpar@1624
|
23 |
\section named-func-param Named Function Parameters
|
alpar@955
|
24 |
|
alpar@1536
|
25 |
C++ makes it possible to use default parameter values when calling a
|
alpar@1536
|
26 |
function. In such a case we do not have to give value for parameters,
|
alpar@1536
|
27 |
the program will use the default ones. Unfortunately sometimes this
|
alpar@1536
|
28 |
is not enough. If we do not want to give values for all the
|
alpar@1536
|
29 |
parameters, only for some of them we come across problems, because an
|
alpar@1536
|
30 |
arbitrary set of parameters cannot be omitted. On the other hand
|
alpar@1536
|
31 |
parameters have a fixed order in the head of the function. C++ can
|
alpar@1536
|
32 |
apply the default values only in the back of the order, if we do not
|
alpar@1536
|
33 |
give other value for them. So we can not give the function for
|
alpar@1536
|
34 |
example the value of the first, and the third parameter, expecting
|
alpar@1536
|
35 |
that the program will aplly the default value for the second
|
alpar@1536
|
36 |
parameter. However sometimes we would like to use some functinos
|
alpar@1536
|
37 |
exactly in this way. With a crafty trick and with some little
|
alpar@1536
|
38 |
inconvenience this is possible. We have implemented this little trick
|
alpar@1536
|
39 |
as an example below.
|
hegyi@1141
|
40 |
|
hegyi@1141
|
41 |
\code
|
alpar@1713
|
42 |
class namedFn
|
hegyi@1141
|
43 |
{
|
hegyi@1141
|
44 |
int _id;
|
hegyi@1141
|
45 |
double _val;
|
hegyi@1141
|
46 |
int _dim;
|
hegyi@1141
|
47 |
|
hegyi@1141
|
48 |
public:
|
alpar@1713
|
49 |
namedFn() : _id(0), _val(1), _dim(2) {}
|
alpar@1713
|
50 |
namedFn& id(int p) { _id = p ; return *this; }
|
alpar@1713
|
51 |
namedFn& val(double p) { _val = p ; return *this; }
|
alpar@1713
|
52 |
namedFn& dim(int p) { _dim = p ; return *this; }
|
hegyi@1141
|
53 |
|
hegyi@1141
|
54 |
run() {
|
hegyi@1141
|
55 |
printf("Here is the function itself.");
|
hegyi@1141
|
56 |
}
|
hegyi@1141
|
57 |
};
|
hegyi@1141
|
58 |
\endcode
|
hegyi@1141
|
59 |
|
hegyi@1141
|
60 |
|
hegyi@1141
|
61 |
The usage is the following.
|
hegyi@1141
|
62 |
|
alpar@1713
|
63 |
We have to define a class, let's call it \c namedFn. Let us assume that
|
alpar@1713
|
64 |
we would like to use a parameter, called \c X. In the \c namedFn class we
|
alpar@1624
|
65 |
have to define an \c _X attribute, and a function \c X. The function
|
alpar@1624
|
66 |
expects a parameter with the type of \c _X, and sets the value of
|
alpar@1624
|
67 |
\c _X. After setting the value the function returns the class itself. The
|
alpar@1624
|
68 |
class also have to have a function, called for example <tt>run()</tt>, we have
|
alpar@1536
|
69 |
to implement here the original function itself. The constructor of the
|
alpar@1624
|
70 |
class have to give all the attributes like \c _X the default values of
|
alpar@1536
|
71 |
them.
|
hegyi@1141
|
72 |
|
alpar@1536
|
73 |
If we instantiate this class, the default values will be set for the
|
hegyi@1619
|
74 |
attributes (originally the parameters), initially. If we call function
|
alpar@1624
|
75 |
\c X, we get a class with the modified parameter value of
|
alpar@1713
|
76 |
\c X. Therefore we can modify any parameter-value, independently from the
|
alpar@1624
|
77 |
order. To run the algorithm we have to call the <tt>run()</tt> function at the
|
alpar@1536
|
78 |
end of the row.
|
hegyi@1141
|
79 |
|
alpar@1624
|
80 |
Example:
|
alpar@1624
|
81 |
\code
|
alpar@1713
|
82 |
namedFn().id(3).val(2).run();
|
alpar@1624
|
83 |
\endcode
|
alpar@955
|
84 |
|
alpar@1713
|
85 |
\note Although it is a class, namedFn is used pretty much like as it were
|
alpar@1713
|
86 |
a function. That it why it is called namedFn and not \c NamedFn.
|
alpar@1713
|
87 |
|
alpar@1713
|
88 |
\note In fact, the final <tt>.run()</tt> could be made unnecessary if the
|
alpar@1713
|
89 |
actual function code were put in the destructor instead. This however would make
|
alpar@1713
|
90 |
hard to implement functions with return values, and would also make the
|
alpar@1713
|
91 |
implementation of \ref named-templ-func-param "named template parameters"
|
alpar@1929
|
92 |
very problematic. <b>Therefore, by convention, <tt>.run()</tt> must be used
|
alpar@1929
|
93 |
to explicitly execute function having named parameters in Lemon.</b>
|
alpar@1713
|
94 |
|
alpar@1713
|
95 |
|
alpar@955
|
96 |
\section traits-classes Traits Classes
|
alpar@955
|
97 |
|
alpar@1536
|
98 |
The procedure above can also be applied when defining classes. In this
|
alpar@1536
|
99 |
case the type of the attributes can be changed. Initially we have to
|
alpar@1536
|
100 |
define a class with the default attribute types. This is the so called
|
alpar@1536
|
101 |
Traits Class. Later on the types of these attributes can be changed,
|
alpar@1536
|
102 |
as described below. In our software \ref lemon::DijkstraDefaultTraits is an
|
alpar@1536
|
103 |
example of how a traits class looks like.
|
hegyi@1141
|
104 |
|
alpar@955
|
105 |
\section named-templ-param Named Class Template Parameters
|
alpar@954
|
106 |
|
alpar@1536
|
107 |
If we would like to change the type of an attribute in a class that
|
alpar@1536
|
108 |
was instantiated by using a traits class as a template parameter, and
|
alpar@1536
|
109 |
the class contains named parameters, we do not have to reinstantiate
|
alpar@1536
|
110 |
the class with new traits class. Instead of that, adaptor classes can
|
alpar@1536
|
111 |
be used like in the following cases.
|
hegyi@1141
|
112 |
|
alpar@954
|
113 |
\code
|
deba@1709
|
114 |
Dijkstra<>::SetPredNodeMap<NullMap<Node,Node> >::Create
|
alpar@954
|
115 |
\endcode
|
hegyi@1141
|
116 |
|
alpar@954
|
117 |
It can also be used in conjunction with other named template
|
alpar@954
|
118 |
parameters in arbitrary order.
|
hegyi@1141
|
119 |
|
alpar@954
|
120 |
\code
|
deba@1709
|
121 |
Dijkstra<>::SetDistMap<MyMap>::SetPredMap<NullMap<Node,Edge> >::Create
|
alpar@954
|
122 |
\endcode
|
alpar@954
|
123 |
|
alpar@1536
|
124 |
The result will be an instantiated Dijkstra class, in which the
|
alpar@1536
|
125 |
DistMap and the PredMap is modified.
|
hegyi@1141
|
126 |
|
alpar@1624
|
127 |
\section named-templ-func-param Named Function Template Parameters
|
alpar@955
|
128 |
|
alpar@1536
|
129 |
If the class has so called wizard functions, the new class with the
|
alpar@1536
|
130 |
modified tpye of attributes can be returned by the appropriate wizard
|
alpar@1536
|
131 |
function. The usage of these wizard functions is the following:
|
alpar@953
|
132 |
|
alpar@953
|
133 |
*/
|