Doxyfile.in 87.3 KB
Newer Older
1
# Doxyfile 1.8.2-20120930
2
3
4

# This file describes the settings to be used by the documentation system
# doxygen (www.doxygen.org) for a project.
5
#
6
7
8
9
10
11
# All text after a hash (#) is considered a comment and will be ignored.
# The format is:
#       TAG = value [value, ...]
# For lists items can also be appended using:
#       TAG += value [value, ...]
# Values that contain spaces should be placed between quotes (" ").
12
13
14
15

#---------------------------------------------------------------------------
# Project related configuration options
#---------------------------------------------------------------------------
16
17
18
19
20
21
22
23
24
25
26
27
28

# This tag specifies the encoding used for all characters in the config file
# that follow. The default is UTF-8 which is also the encoding used for all
# text before the first occurrence of this tag. Doxygen uses libiconv (or the
# iconv built into libc) for the transcoding. See
# http://www.gnu.org/software/libiconv for the list of possible encodings.

DOXYFILE_ENCODING      = UTF-8

# The PROJECT_NAME tag is a single word (or sequence of words) that should
# identify the project. Note that if you do not use Doxywizard you need
# to put quotes around the project name if it contains spaces.

29
PROJECT_NAME           = "Milena"
30
31
32
33
34

# The PROJECT_NUMBER tag can be used to enter a project or revision number.
# This could be handy for archiving the generated documentation or
# if some version control system is used.

35
PROJECT_NUMBER         = "User documentation @PACKAGE_VERSION@ @ID@"
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54

# Using the PROJECT_BRIEF tag one can provide an optional one line description
# for a project that appears at the top of each page and should give viewer
# a quick idea about the purpose of the project. Keep the description short.

PROJECT_BRIEF          = "An Image Processing Platform"

# With the PROJECT_LOGO tag one can specify an logo or icon that is
# included in the documentation. The maximum height of the logo should not
# exceed 55 pixels and the maximum width should not exceed 200 pixels.
# Doxygen will copy the logo to the output directory.

PROJECT_LOGO           = @top_srcdir@/doc/images/logo.jpg

# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
# base path where the generated documentation will be put.
# If a relative path is entered, it will be relative to the location
# where doxygen was started. If left blank the current directory will be used.

55
OUTPUT_DIRECTORY       = @builddir@/user-refman.tmp
56
57
58
59
60
61
62
63

# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
# 4096 sub-directories (in 2 levels) under the output directory of each output
# format and will distribute the generated files over these directories.
# Enabling this option can be useful when feeding doxygen a huge amount of
# source files, where putting all generated files in the same directory would
# otherwise cause performance problems for the file system.

64
CREATE_SUBDIRS         = YES
65
66
67
68
69
70
71
72
73
74
75
76

# The OUTPUT_LANGUAGE tag is used to specify the language in which all
# documentation generated by doxygen is written. Doxygen will use this
# information to generate all constant output in the proper language.
# The default language is English, other supported languages are:
# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,
# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.

77
OUTPUT_LANGUAGE        = English
78
79
80
81
82
83

# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
# include brief member descriptions after the members that are listed in
# the file and class documentation (similar to JavaDoc).
# Set to NO to disable this.

84
BRIEF_MEMBER_DESC      = NO
85
86
87
88
89
90

# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
# the brief description of a member or function before the detailed description.
# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
# brief descriptions will be completely suppressed.

91
REPEAT_BRIEF           = YES
92
93
94
95
96
97
98
99
100
101
102

# This tag implements a quasi-intelligent brief description abbreviator
# that is used to form the text in various listings. Each string
# in this list, if found as the leading text of the brief description, will be
# stripped from the text and the result after processing the whole list, is
# used as the annotated text. Otherwise, the brief description is used as-is.
# If left blank, the following values are used ("$name" is automatically
# replaced with the name of the entity): "The $name class" "The $name widget"
# "The $name file" "is" "provides" "specifies" "contains"
# "represents" "a" "an" "the"

103
ABBREVIATE_BRIEF       =
104
105
106
107
108

# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
# Doxygen will generate a detailed section even if there is only a brief
# description.

109
ALWAYS_DETAILED_SEC    = YES
110
111
112
113
114
115

# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
# inherited members of a class in the documentation of that class as if those
# members were ordinary class members. Constructors, destructors and assignment
# operators of the base classes will not be shown.

116
INLINE_INHERITED_MEMB  = YES
117
118
119
120
121

# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
# path before files name in the file list and in the header files. If set
# to NO the shortest path that makes the file name unique will be used.

122
FULL_PATH_NAMES        = NO
123
124
125
126
127
128

# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
# can be used to strip a user-defined part of the path. Stripping is
# only done if one of the specified strings matches the left-hand part of
# the path. The tag can be used to show relative paths in the file list.
# If left blank the directory from which doxygen is run is used as the
129
130
131
# path to strip. Note that you specify absolute paths here, but also
# relative paths, which will be relative from the directory where doxygen is
# started.
132

133
STRIP_FROM_PATH        = @top_srcdir@/milena
134
135
136
137
138
139
140
141

# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
# the path mentioned in the documentation of a class, which tells
# the reader which header file to include in order to use a class.
# If left blank only the name of the header file containing the class
# definition is used. Otherwise one should specify the include paths that
# are normally passed to the compiler using the -I flag.

142
STRIP_FROM_INC_PATH    = @top_srcdir@/milena
143
144
145
146
147

# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
# (but less readable) file names. This can be useful if your file system
# doesn't support long names like on DOS, Mac, or CD-ROM.

148
SHORT_NAMES            = NO
149
150
151
152
153
154
155

# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
# will interpret the first line (until the first dot) of a JavaDoc-style
# comment as the brief description. If set to NO, the JavaDoc
# comments will behave just like regular Qt-style comments
# (thus requiring an explicit @brief command for a brief description.)

Guillaume Lazzara's avatar
Guillaume Lazzara committed
156
JAVADOC_AUTOBRIEF      = YES
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171

# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
# interpret the first line (until the first dot) of a Qt-style
# comment as the brief description. If set to NO, the comments
# will behave just like regular Qt-style comments (thus requiring
# an explicit \brief command for a brief description.)

QT_AUTOBRIEF           = NO

# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
# treat a multi-line C++ special comment block (i.e. a block of //! or ///
# comments) as a brief description. This used to be the default behaviour.
# The new default is to treat a multi-line C++ comment block as a detailed
# description. Set this tag to YES if you prefer the old behaviour instead.

172
MULTILINE_CPP_IS_BRIEF = NO
173
174
175
176
177

# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
# member inherits the documentation from any documented member that it
# re-implements.

178
INHERIT_DOCS           = YES
179
180
181
182
183

# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
# a new page for each member. If set to NO, the documentation of a member will
# be part of the file/class/namespace that contains it.

184
SEPARATE_MEMBER_PAGES  = NO
185
186
187
188

# The TAB_SIZE tag can be used to set the number of spaces in a tab.
# Doxygen uses this value to replace tabs by spaces in code fragments.

189
TAB_SIZE               = 8
190
191
192
193
194
195
196
197

# This tag can be used to specify a number of aliases that acts
# as commands in the documentation. An alias has the form "name=value".
# For example adding "sideeffect=\par Side Effects:\n" will allow you to
# put the command \sideeffect (or @sideeffect) in the documentation, which
# will result in a user-defined paragraph with heading "Side Effects:".
# You can put \n's in the value part of an alias to insert newlines.

198
ALIASES                =
199
200
201
202
203
204
205
206
207
208
209
210
211

# This tag can be used to specify a number of word-keyword mappings (TCL only).
# A mapping has the form "name=value". For example adding
# "class=itcl::class" will allow you to use the command class in the
# itcl::class meaning.

TCL_SUBST              =

# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
# sources only. Doxygen will then generate output that is more tailored for C.
# For instance, some of the names that are used will be different. The list
# of all members will be omitted, etc.

212
OPTIMIZE_OUTPUT_FOR_C  = NO
213
214
215
216
217
218

# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java
# sources only. Doxygen will then generate output that is more tailored for
# Java. For instance, namespaces will be presented as packages, qualified
# scopes will look different, etc.

219
OPTIMIZE_OUTPUT_JAVA   = NO
220
221
222
223
224
225
226
227
228
229
230
231
232
233

# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran
# sources only. Doxygen will then generate output that is more tailored for
# Fortran.

OPTIMIZE_FOR_FORTRAN   = NO

# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
# sources. Doxygen will then generate output that is tailored for
# VHDL.

OPTIMIZE_OUTPUT_VHDL   = NO

# Doxygen selects the parser to use depending on the extension of the files it
234
235
236
237
238
239
240
241
242
# parses. With this tag you can assign which parser to use for a given
# extension. Doxygen has a built-in mapping, but you can override or extend it
# using this tag. The format is ext=language, where ext is a file extension,
# and language is one of the parsers supported by doxygen: IDL, Java,
# Javascript, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C,
# C++. For instance to make doxygen treat .inc files as Fortran files (default
# is PHP), and .f files as C (default is Fortran), use: inc=Fortran f=C. Note
# that for custom extensions you also need to set FILE_PATTERNS otherwise the
# files are not read by doxygen.
243
244
245
246
247
248
249
250
251
252
253
254

EXTENSION_MAPPING      =

# If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all
# comments according to the Markdown format, which allows for more readable
# documentation. See http://daringfireball.net/projects/markdown/ for details.
# The output of markdown processing is further processed by doxygen, so you
# can mix doxygen, HTML, and XML commands with Markdown formatting.
# Disable only in case of backward compatibilities issues.

MARKDOWN_SUPPORT       = YES

255
256
257
258
259
260
261
# When enabled doxygen tries to link words that correspond to documented classes,
# or namespaces to their corresponding documentation. Such a link can be
# prevented in individual cases by by putting a % sign in front of the word or
# globally by setting AUTOLINK_SUPPORT to NO.

AUTOLINK_SUPPORT       = YES

262
263
264
265
266
267
268
# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
# to include (a tag file for) the STL sources as input, then you should
# set this tag to YES in order to let doxygen match functions declarations and
# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
# func(std::string) {}). This also makes the inheritance and collaboration
# diagrams that involve STL classes more complete and accurate.

269
BUILTIN_STL_SUPPORT    = YES
270
271
272
273
274
275
276
277
278
279
280
281

# If you use Microsoft's C++/CLI language, you should set this option to YES to
# enable parsing support.

CPP_CLI_SUPPORT        = NO

# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
# Doxygen will parse them like normal C++ but will assume all classes use public
# instead of private inheritance when no explicit protection keyword is present.

SIP_SUPPORT            = NO

282
283
284
285
# For Microsoft's IDL there are propget and propput attributes to indicate
# getter and setter methods for a property. Setting this option to YES (the
# default) will make doxygen replace the get and set methods by a property in
# the documentation. This will only work if the methods are indeed getting or
286
287
288
# setting a simple type. If this is not the case, or you want to show the
# methods anyway, you should set this option to NO.

289
IDL_PROPERTY_SUPPORT   = NO
290
291
292
293
294
295

# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
# tag is set to YES, then doxygen will reuse the documentation of the first
# member in the group (if any) for the other members of the group. By default
# all members of a group must be documented explicitly.

296
DISTRIBUTE_GROUP_DOC   = NO
297
298
299
300
301
302
303

# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
# the same type (for instance a group of public functions) to be put as a
# subgroup of that type (e.g. under the Public Functions section). Set it to
# NO to prevent subgrouping. Alternatively, this can be done per class using
# the \nosubgrouping command.

304
SUBGROUPING            = YES
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329

# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and
# unions are shown inside the group in which they are included (e.g. using
# @ingroup) instead of on a separate page (for HTML and Man pages) or
# section (for LaTeX and RTF).

INLINE_GROUPED_CLASSES = NO

# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and
# unions with only public data fields will be shown inline in the documentation
# of the scope in which they are defined (i.e. file, namespace, or group
# documentation), provided this scope is documented. If set to NO (the default),
# structs, classes, and unions are shown on a separate page (for HTML and Man
# pages) or section (for LaTeX and RTF).

INLINE_SIMPLE_STRUCTS  = NO

# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
# is documented as struct, union, or enum with the name of the typedef. So
# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
# with name TypeT. When disabled the typedef will appear as a member of a file,
# namespace, or class. And the struct will be named TypeS. This can typically
# be useful for C code in case the coding convention dictates that all compound
# types are typedef'ed and only the typedef is referenced, never the tag name.

330
TYPEDEF_HIDES_STRUCT   = YES
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358

# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
# determine which symbols to keep in memory and which to flush to disk.
# When the cache is full, less often used symbols will be written to disk.
# For small to medium size projects (<1000 input files) the default value is
# probably good enough. For larger projects a too small cache size can cause
# doxygen to be busy swapping symbols to and from disk most of the time
# causing a significant performance penalty.
# If the system has enough physical memory increasing the cache will improve the
# performance by keeping more symbols in memory. Note that the value works on
# a logarithmic scale so increasing the size by one will roughly double the
# memory usage. The cache size is given by this formula:
# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
# corresponding to a cache size of 2^16 = 65536 symbols.

SYMBOL_CACHE_SIZE      = 0

# Similar to the SYMBOL_CACHE_SIZE the size of the symbol lookup cache can be
# set using LOOKUP_CACHE_SIZE. This cache is used to resolve symbols given
# their name and scope. Since this can be an expensive process and often the
# same symbol appear multiple times in the code, doxygen keeps a cache of
# pre-resolved symbols. If the cache is too small doxygen will become slower.
# If the cache is too large, memory is wasted. The cache size is given by this
# formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range is 0..9, the default is 0,
# corresponding to a cache size of 2^16 = 65536 symbols.

LOOKUP_CACHE_SIZE      = 0

359
360
361
#---------------------------------------------------------------------------
# Build related configuration options
#---------------------------------------------------------------------------
362
363
364
365
366
367

# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
# documentation are documented, even if no documentation was available.
# Private class members and static file members will be hidden unless
# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES

368
EXTRACT_ALL            = YES
369
370
371
372

# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
# will be included in the documentation.

373
EXTRACT_PRIVATE        = NO
374

375
376
# If the EXTRACT_PACKAGE tag is set to YES all members with package or internal
# scope will be included in the documentation.
377
378
379
380
381
382

EXTRACT_PACKAGE        = NO

# If the EXTRACT_STATIC tag is set to YES all static members of a file
# will be included in the documentation.

383
EXTRACT_STATIC         = NO
384
385
386
387
388

# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
# defined locally in source files will be included in the documentation.
# If set to NO only classes defined in header files are included.

389
EXTRACT_LOCAL_CLASSES  = NO
390
391
392
393
394
395

# This flag is only useful for Objective-C code. When set to YES local
# methods, which are defined in the implementation section but not in
# the interface are included in the documentation.
# If set to NO (the default) only methods in the interface are included.

396
EXTRACT_LOCAL_METHODS  = NO
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411

# If this flag is set to YES, the members of anonymous namespaces will be
# extracted and appear in the documentation as a namespace called
# 'anonymous_namespace{file}', where file will be replaced with the base
# name of the file that contains the anonymous namespace. By default
# anonymous namespaces are hidden.

EXTRACT_ANON_NSPACES   = NO

# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
# undocumented members of documented classes, files or namespaces.
# If set to NO (the default) these members will be included in the
# various overviews, but no documentation section is generated.
# This option has no effect if EXTRACT_ALL is enabled.

412
HIDE_UNDOC_MEMBERS     = NO
413
414
415
416
417
418

# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
# undocumented classes that are normally visible in the class hierarchy.
# If set to NO (the default) these classes will be included in the various
# overviews. This option has no effect if EXTRACT_ALL is enabled.

419
HIDE_UNDOC_CLASSES     = NO
420
421
422
423
424
425

# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
# friend (class|struct|union) declarations.
# If set to NO (the default) these declarations will be included in the
# documentation.

426
HIDE_FRIEND_COMPOUNDS  = YES
427
428
429
430
431
432

# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
# documentation blocks found inside the body of a function.
# If set to NO (the default) these blocks will be appended to the
# function's detailed documentation block.

433
HIDE_IN_BODY_DOCS      = YES
434
435
436
437
438
439

# The INTERNAL_DOCS tag determines if documentation
# that is typed after a \internal command is included. If the tag is set
# to NO (the default) then the documentation will be excluded.
# Set it to YES to include the internal documentation.

440
INTERNAL_DOCS          = NO
441
442
443
444
445
446
447

# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
# file names in lower-case letters. If set to YES upper-case letters are also
# allowed. This is useful if you have classes or files whose names only differ
# in case and if your file system supports case sensitive file names. Windows
# and Mac users are advised to set this option to NO.

448
CASE_SENSE_NAMES       = YES
449
450
451
452
453

# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
# will show members with their full class and namespace scopes in the
# documentation. If set to YES the scope will be hidden.

454
HIDE_SCOPE_NAMES       = NO
455
456
457
458
459

# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
# will put a list of the files that are included by a file in the documentation
# of that file.

460
SHOW_INCLUDE_FILES     = YES
461
462
463
464
465
466
467
468
469
470

# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
# will list include files with double quotes in the documentation
# rather than with sharp brackets.

FORCE_LOCAL_INCLUDES   = NO

# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
# is inserted in the documentation for inline members.

471
INLINE_INFO            = YES
472
473
474
475
476
477

# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
# will sort the (detailed) documentation of file and class members
# alphabetically by member name. If set to NO the members will appear in
# declaration order.

478
SORT_MEMBER_DOCS       = YES
479
480
481
482
483
484

# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
# brief documentation of file, namespace and class members alphabetically
# by member name. If set to NO (the default) the members will appear in
# declaration order.

485
SORT_BRIEF_DOCS        = YES
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525

# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
# will sort the (brief and detailed) documentation of class members so that
# constructors and destructors are listed first. If set to NO (the default)
# the constructors will appear in the respective orders defined by
# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.

SORT_MEMBERS_CTORS_1ST = YES

# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
# hierarchy of group names into alphabetical order. If set to NO (the default)
# the group names will appear in their defined order.

SORT_GROUP_NAMES       = YES

# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
# sorted by fully-qualified names, including namespaces. If set to
# NO (the default), the class list will be sorted only by class name,
# not including the namespace part.
# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
# Note: This option applies only to the class list, not to the
# alphabetical list.

SORT_BY_SCOPE_NAME     = NO

# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to
# do proper type resolution of all parameters of a function it will reject a
# match between the prototype and the implementation of a member function even
# if there is only one candidate or it is obvious which candidate to choose
# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen
# will still accept a match between prototype and implementation in such cases.

STRICT_PROTO_MATCHING  = YES

# The GENERATE_TODOLIST tag can be used to enable (YES) or
# disable (NO) the todo list. This list is created by putting \todo
# commands in the documentation.

526
GENERATE_TODOLIST      = NO
527
528
529
530
531

# The GENERATE_TESTLIST tag can be used to enable (YES) or
# disable (NO) the test list. This list is created by putting \test
# commands in the documentation.

532
GENERATE_TESTLIST      = YES
533
534
535
536
537

# The GENERATE_BUGLIST tag can be used to enable (YES) or
# disable (NO) the bug list. This list is created by putting \bug
# commands in the documentation.

538
GENERATE_BUGLIST       = YES
539
540
541
542
543

# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
# disable (NO) the deprecated list. This list is created by putting
# \deprecated commands in the documentation.

544
GENERATE_DEPRECATEDLIST= YES
545
546
547
548

# The ENABLED_SECTIONS tag can be used to enable conditional
# documentation sections, marked by \if sectionname ... \endif.

549
ENABLED_SECTIONS       =
550
551
552
553
554
555
556
557
558

# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
# the initial value of a variable or macro consists of for it to appear in
# the documentation. If the initializer consists of more lines than specified
# here it will be hidden. Use a value of 0 to hide initializers completely.
# The appearance of the initializer of individual variables and macros in the
# documentation can be controlled using \showinitializer or \hideinitializer
# command in the documentation regardless of this setting.

559
MAX_INITIALIZER_LINES  = 30
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577

# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
# at the bottom of the documentation of classes and structs. If set to YES the
# list will mention the files that were used to generate the documentation.

SHOW_USED_FILES        = NO

# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
# This will remove the Files entry from the Quick Index and from the
# Folder Tree View (if specified). The default is YES.

SHOW_FILES             = NO

# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
# Namespaces page.
# This will remove the Namespaces entry from the Quick Index
# and from the Folder Tree View (if specified). The default is YES.

578
SHOW_NAMESPACES        = YES
579
580
581
582
583
584
585
586
587

# The FILE_VERSION_FILTER tag can be used to specify a program or script that
# doxygen should invoke to get the current version for each file (typically from
# the version control system). Doxygen will invoke the program by executing (via
# popen()) the command <command> <input-file>, where <command> is the value of
# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
# provided by doxygen. Whatever the program writes to standard output
# is used as the file version. See the manual for examples.

588
FILE_VERSION_FILTER    =
589
590
591

# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
# by doxygen. The layout file controls the global structure of the generated
592
# output files in an output format independent way. To create the layout file
593
594
595
596
597
598
599
600
601
602
603
604
# that represents doxygen's defaults, run doxygen with the -l option.
# You can optionally specify a file name after the option, if omitted
# DoxygenLayout.xml will be used as the name of the layout file.

LAYOUT_FILE            = @top_srcdir@/milena/doc/DoxygenLayout.xml

# The CITE_BIB_FILES tag can be used to specify one or more bib files
# containing the references data. This must be a list of .bib files. The
# .bib extension is automatically appended if omitted. Using this command
# requires the bibtex tool to be installed. See also
# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style
# of the bibliography can be controlled using LATEX_BIB_STYLE. To use this
605
606
# feature you need bibtex and perl available in the search path. Do not use
# file names with spaces, bibtex cannot handle them.
607

608
609
CITE_BIB_FILES         = @abs_top_srcdir@/doc/doc.bib \
		       	 @abs_top_srcdir@/doc/olena.bib
610

611
612
613
#---------------------------------------------------------------------------
# configuration options related to warning and progress messages
#---------------------------------------------------------------------------
614
615
616
617

# The QUIET tag can be used to turn on/off the messages that are generated
# by doxygen. Possible values are YES and NO. If left blank NO is used.

618
QUIET                  = YES
619
620
621
622
623

# The WARNINGS tag can be used to turn on/off the warning messages that are
# generated by doxygen. Possible values are YES and NO. If left blank
# NO is used.

624
WARNINGS               = YES
625
626
627
628
629

# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
# automatically be disabled.

630
WARN_IF_UNDOCUMENTED   = NO
631
632
633
634
635
636

# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
# potential errors in the documentation, such as not documenting some
# parameters in a documented function, or documenting parameters that
# don't exist or using markup commands wrongly.

637
WARN_IF_DOC_ERROR      = YES
638
639
640
641
642
643
644

# The WARN_NO_PARAMDOC option can be enabled to get warnings for
# functions that are documented, but have no documentation for their parameters
# or return value. If set to NO (the default) doxygen will only warn about
# wrong or incomplete parameter documentation, but not about the absence of
# documentation.

645
WARN_NO_PARAMDOC       = NO
646
647
648
649
650
651
652
653

# The WARN_FORMAT tag determines the format of the warning messages that
# doxygen can produce. The string should contain the $file, $line, and $text
# tags, which will be replaced by the file and line number from which the
# warning originated and the warning text. Optionally the format may contain
# $version, which will be replaced by the version of the file (if it could
# be obtained via FILE_VERSION_FILTER)

654
WARN_FORMAT            = "$file:$line: $text"
655
656
657
658
659

# The WARN_LOGFILE tag can be used to specify a file to which warning
# and error messages should be written. If left blank the output is written
# to stderr.

660
WARN_LOGFILE           =
661

662
663
664
#---------------------------------------------------------------------------
# configuration options related to the input files
#---------------------------------------------------------------------------
665
666
667
668
669
670

# The INPUT tag can be used to specify the files and/or directories that contain
# documented source files. You may enter file names like "myfile.cpp" or
# directories like "/usr/src/myproject". Separate the files or directories
# with spaces.

671
INPUT                  = @top_srcdir@/milena
672
673
674
675
676
677
678

# This tag can be used to specify the character encoding of the source files
# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
# also the default input encoding. Doxygen uses libiconv (or the iconv built
# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
# the list of possible encodings.

Roland Levillain's avatar
Roland Levillain committed
679
INPUT_ENCODING         = UTF-8
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698

# If the value of the INPUT tag contains directories, you can use the
# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
# and *.h) to filter out the source-files in the directories. If left
# blank the following patterns are tested:
# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
# *.f90 *.f *.for *.vhd *.vhdl

FILE_PATTERNS          = *.cc \
                         *.hh \
                         *.hxx \
                         *.hcc \
                         *.dox

# The RECURSIVE tag can be used to turn specify whether or not subdirectories
# should be searched for input files as well. Possible values are YES and NO.
# If left blank NO is used.

699
RECURSIVE              = YES
700
701
702
703
704
705
706
707

# The EXCLUDE tag can be used to specify files and/or directories that should be
# excluded from the INPUT source files. This way you can easily exclude a
# subdirectory from a directory tree whose root is specified with the INPUT tag.
# Note that relative paths are relative to the directory from which doxygen is
# run.

EXCLUDE                = @top_srcdir@/milena/sandbox \
708
                         @top_srcdir@/milena/mln/core/concept/proxy.hxx \
709
710
                         @top_srcdir@/milena/doc/user-refman \
                         @top_srcdir@/milena/doc/devel-refman \
711
                         @top_srcdir@/milena/tests/unit_test
712
713
714
715
716

# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or
# directories that are symbolic links (a Unix file system feature) are excluded
# from the input.

717
EXCLUDE_SYMLINKS       = YES
718
719
720
721
722
723
724

# If the value of the INPUT tag contains directories, you can use the
# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
# certain files from those directories. Note that the wildcards are matched
# against the file with absolute path, so to exclude all test directories
# for example use the pattern */test/*

725
EXCLUDE_PATTERNS       = *spe.hh
726
727
728
729
730
731
732

# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
# (namespaces, classes, functions, etc.) that should be excluded from the
# output. The symbol name can be a fully qualified name, a word, or if the
# wildcard * is used, a substring. Examples: ANamespace, AClass,
# AClass::ANamespace, ANamespace::*Test

733
734
735
736
737
738
739
EXCLUDE_SYMBOLS        = mln::*_check*				\
		         mln::internal::check::*		\
			 mln::internal::data<*			\
			 mln::internal::subject_impl<*		\
			 mln::internal::subject_impl		\
			 mln::internal::subject_point_impl<*	\
			 mln::internal::subject_point_impl	\
740
741
			 mln::trait::bkd_*			\
			 mln::trait::accumulator::*		\
742
			 mln::trait::accumulator_<*		\
743
		         mln::trait::image::*	    		\
744
		         mln::trait::image_<*	    		\
745
			 mln::trait::neighborhood::*		\
746
			 mln::trait::op_*<			\
747
			 mln::trait::op::*			\
748
			 mln::trait::impl::ch_value_<*		\
749
			 mln::trait::site_set::*		\
750
751
			 mln::trait::site_set_<*		\
			 mln::trait::set_*	    		\
752
			 mln::trait::value::*	    		\
753
			 mln::trait::value_*	    		\
754
			 mln::trait::window::*			\
755
			 mln::trait::window_<*			\
756
757
			 mln::trait::internal::* 		\
			 mln::trait::next::*			\
758
759
760
761
762
763
764
765
			 mln::metal::*					    	\
			 mln::doc::*						\
			 mln::io::*::internal::*				\
			 mln::internal::exact_*					\
			 mln::internal::fixme					\
			 mln::internal::helper*category*			\
			 mln::tag::*

766
767
768
769
770
771
772
773
774
775
776
777
778
779
780

# The EXAMPLE_PATH tag can be used to specify one or more files or
# directories that contain example code fragments that are included (see
# the \include command).

EXAMPLE_PATH           = @top_srcdir@/milena/doc/examples \
                         @top_srcdir@/milena/doc/outputs \
                         @top_srcdir@/milena/doc/examples/split \
                         @top_srcdir@/milena/doc/outputs/split

# If the value of the EXAMPLE_PATH tag contains directories, you can use the
# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
# and *.h) to filter out the source-files in the directories. If left
# blank all files are included.

781
EXAMPLE_PATTERNS       = *.cc \
782
783
784
785
786
787
788
789
                         *.cc.raw \
                         *.txt

# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
# searched for input files to be used with the \include or \dontinclude
# commands irrespective of the value of the RECURSIVE tag.
# Possible values are YES and NO. If left blank NO is used.

790
EXAMPLE_RECURSIVE      = NO
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807

# The IMAGE_PATH tag can be used to specify one or more files or
# directories that contain image that are included in the documentation (see
# the \image command).

IMAGE_PATH             = @top_srcdir@/milena/doc/img \
                         @top_srcdir@/milena/doc/figures

# The INPUT_FILTER tag can be used to specify a program that doxygen should
# invoke to filter for each input file. Doxygen will invoke the filter program
# by executing (via popen()) the command <filter> <input-file>, where <filter>
# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
# input file. Doxygen will then use the output that the filter program writes
# to standard output.
# If FILTER_PATTERNS is specified, this tag will be
# ignored.

808
INPUT_FILTER           =
809
810
811
812
813
814
815
816
817
818

# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
# basis.
# Doxygen will compare the file name with each pattern and apply the
# filter if there is a match.
# The filters are a list of the form:
# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
# info on how filters are used. If FILTER_PATTERNS is empty or if
# non of the patterns match the file name, INPUT_FILTER is applied.

819
FILTER_PATTERNS        =
820
821
822
823
824

# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
# INPUT_FILTER) will be used to filter the input files when producing source
# files to browse (i.e. when SOURCE_BROWSER is set to YES).

825
FILTER_SOURCE_FILES    = NO
826
827
828
829
830
831
832
833
834

# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
# pattern. A pattern will override the setting for FILTER_PATTERN (if any)
# and it is also possible to disable source filtering for a specific pattern
# using *.ext= (so without naming a filter). This option only has effect when
# FILTER_SOURCE_FILES is enabled.

FILTER_SOURCE_PATTERNS =

835
836
837
#---------------------------------------------------------------------------
# configuration options related to source browsing
#---------------------------------------------------------------------------
838
839
840
841
842
843

# If the SOURCE_BROWSER tag is set to YES then a list of source files will
# be generated. Documented entities will be cross-referenced with these sources.
# Note: To get rid of all source code in the generated output, make sure also
# VERBATIM_HEADERS is set to NO.

Guillaume Lazzara's avatar
Guillaume Lazzara committed
844
SOURCE_BROWSER         = YES
845
846
847
848

# Setting the INLINE_SOURCES tag to YES will include the body
# of functions and classes directly in the documentation.

849
INLINE_SOURCES         = NO
850
851
852

# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
# doxygen to hide any special comment blocks from generated source code
853
# fragments. Normal C, C++ and Fortran comments will always remain visible.
854

855
STRIP_CODE_COMMENTS    = YES
856
857
858
859
860

# If the REFERENCED_BY_RELATION tag is set to YES
# then for each documented function all documented
# functions referencing it will be listed.

861
REFERENCED_BY_RELATION = NO
862
863
864
865
866

# If the REFERENCES_RELATION tag is set to YES
# then for each documented function all documented entities
# called/used by that function will be listed.

867
REFERENCES_RELATION    = NO
868
869
870
871
872
873
874

# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
# link to the source code.
# Otherwise they will link to the documentation.

875
REFERENCES_LINK_SOURCE = NO
876
877
878
879
880
881
882

# If the USE_HTAGS tag is set to YES then the references to source code
# will point to the HTML generated by the htags(1) tool instead of doxygen
# built-in source browser. The htags tool is part of GNU's global source
# tagging system (see http://www.gnu.org/software/global/global.html). You
# will need version 4.8.6 or higher.

883
USE_HTAGS              = NO
884
885
886
887
888

# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
# will generate a verbatim copy of the header file for each class for
# which an include is specified. Set to NO to disable this.

889
VERBATIM_HEADERS       = YES
890

891
892
893
#---------------------------------------------------------------------------
# configuration options related to the alphabetical class index
#---------------------------------------------------------------------------
894
895
896
897
898

# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
# of all compounds will be generated. Enable this if the project
# contains a lot of classes, structs, unions or interfaces.

899
ALPHABETICAL_INDEX     = YES
900
901
902
903
904

# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
# in which this list will be split (can be a number in the range [1..20])

905
COLS_IN_ALPHA_INDEX    = 2
906
907
908
909
910
911

# In case all classes in a project start with a common prefix, all
# classes will be put under the same header in the alphabetical index.
# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
# should be ignored while generating the index headers.

Guillaume Lazzara's avatar
Guillaume Lazzara committed
912
IGNORE_PREFIX          = mln::
913

914
915
916
#---------------------------------------------------------------------------
# configuration options related to the HTML output
#---------------------------------------------------------------------------
917
918
919
920

# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
# generate HTML output.

921
GENERATE_HTML          = YES
922
923
924
925
926

# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `html' will be used as the default path.

927
HTML_OUTPUT            = html
928
929
930
931
932

# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
# doxygen will generate files with .html extension.

933
HTML_FILE_EXTENSION    = .html
934
935
936
937
938
939
940
941
942
943
944
945

# The HTML_HEADER tag can be used to specify a personal HTML header for
# each generated HTML page. If it is left blank doxygen will generate a
# standard header. Note that when using a custom header you are responsible
#  for the proper inclusion of any scripts and style sheets that doxygen
# needs, which is dependent on the configuration options used.
# It is advised to generate a default header using "doxygen -w html
# header.html footer.html stylesheet.css YourConfigFile" and then modify
# that header. Note that the header is subject to change so you typically
# have to redo this when upgrading to a newer version of doxygen or when
# changing the value of configuration settings such as GENERATE_TREEVIEW!

946
HTML_HEADER            = @top_srcdir@/doc/header.html
947
948
949
950
951

# The HTML_FOOTER tag can be used to specify a personal HTML footer for
# each generated HTML page. If it is left blank doxygen will generate a
# standard footer.

952
HTML_FOOTER            = @top_srcdir@/doc/subdoc_footer.html
953
954
955

# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
# style sheet that is used by each HTML page. It can be used to
956
957
958
959
960
961
962
963
964
965
966
967
968
969
# fine-tune the look of the HTML output. If left blank doxygen will
# generate a default style sheet. Note that it is recommended to use
# HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this
# tag will in the future become obsolete.

HTML_STYLESHEET        =

# The HTML_EXTRA_STYLESHEET tag can be used to specify an additional
# user-defined cascading style sheet that is included after the standard
# style sheets created by doxygen. Using this option one can overrule
# certain style aspects. This is preferred over using HTML_STYLESHEET
# since it does not replace the standard style sheet and is therefor more
# robust against future updates. Doxygen will copy the style sheet file to
# the output directory.
970

971
HTML_EXTRA_STYLESHEET  = @top_srcdir@/doc/doc.css
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014

# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
# other source files which should be copied to the HTML output directory. Note
# that these files will be copied to the base HTML output directory. Use the
# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
# files. In the HTML_STYLESHEET file, use the file name only. Also note that
# the files will be copied as-is; there are no commands or markers available.

HTML_EXTRA_FILES       =

# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
# Doxygen will adjust the colors in the style sheet and background images
# according to this color. Hue is specified as an angle on a colorwheel,
# see http://en.wikipedia.org/wiki/Hue for more information.
# For instance the value 0 represents red, 60 is yellow, 120 is green,
# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
# The allowed range is 0 to 359.

HTML_COLORSTYLE_HUE    = 220

# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
# the colors in the HTML output. For a value of 0 the output will use
# grayscales only. A value of 255 will produce the most vivid colors.

HTML_COLORSTYLE_SAT    = 100

# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
# the luminance component of the colors in the HTML output. Values below
# 100 gradually make the output lighter, whereas values above 100 make
# the output darker. The value divided by 100 is the actual gamma applied,
# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
# and 100 does not change the gamma.

HTML_COLORSTYLE_GAMMA  = 80

# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
# page will contain the date and time when the page was generated. Setting
# this to NO can help when comparing the output of multiple runs.

HTML_TIMESTAMP         = YES

# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
# documentation will contain sections that can be hidden and shown after the
1015
# page has loaded.
1016
1017
1018

HTML_DYNAMIC_SECTIONS  = NO

1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of
# entries shown in the various tree structured indices initially; the user
# can expand and collapse entries dynamically later on. Doxygen will expand
# the tree to such a level that at most the specified number of entries are
# visible (unless a fully collapsed tree already exceeds this amount).
# So setting the number of entries 1 will produce a full collapsed tree by
# default. 0 is a special value representing an infinite number of entries
# and will result in a full expanded tree by default.

HTML_INDEX_NUM_ENTRIES = 100

1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
# If the GENERATE_DOCSET tag is set to YES, additional index files
# will be generated that can be used as input for Apple's Xcode 3
# integrated development environment, introduced with OSX 10.5 (Leopard).
# To create a documentation set, doxygen will generate a Makefile in the
# HTML output directory. Running make will produce the docset in that
# directory and running "make install" will install the docset in
# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
# it at startup.
# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
# for more information.

GENERATE_DOCSET        = NO

# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
# feed. A documentation feed provides an umbrella under which multiple
# documentation sets from a single provider (such as a company or product suite)
# can be grouped.

1048
DOCSET_FEEDNAME        = "Olena Platform Documentation"
1049
1050
1051
1052
1053
1054

# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
# should uniquely identify the documentation set bundle. This should be a
# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
# will append .docset to the name.

1055
DOCSET_BUNDLE_ID       = org.lrde.olena
1056

1057
1058
1059
# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely
# identify the documentation publisher. This should be a reverse domain-name
# style string, e.g. com.mycompany.MyDocSet.documentation.
1060

1061
DOCSET_PUBLISHER_ID    = org.lrde
1062
1063
1064

# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.

1065
DOCSET_PUBLISHER_NAME  = EPITA - LRDE
1066
1067
1068
1069
1070
1071

# If the GENERATE_HTMLHELP tag is set to YES, additional index files
# will be generated that can be used as input for tools like the
# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
# of the generated HTML documentation.

1072
GENERATE_HTMLHELP      = NO
1073
1074
1075
1076
1077
1078

# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
# be used to specify the file name of the resulting .chm file. You
# can add a path in front of the file if the result should not be
# written to the html output directory.

1079
CHM_FILE               =
1080
1081
1082
1083
1084
1085

# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
# be used to specify the location (absolute path including file name) of
# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
# the HTML help compiler on the generated index.hhp.

1086
HHC_LOCATION           =
1087
1088
1089
1090
1091

# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
# controls if a separate .chi index file is generated (YES) or that
# it should be included in the master .chm file (NO).

1092
GENERATE_CHI           = NO
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103

# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
# is used to encode HtmlHelp index (hhk), content (hhc) and project file
# content.

CHM_INDEX_ENCODING     =

# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
# controls whether a binary table of contents is generated (YES) or a
# normal table of contents (NO) in the .chm file.

1104
BINARY_TOC             = NO
1105
1106
1107
1108

# The TOC_EXPAND flag can be set to YES to add extra items for group members
# to the contents of the HTML help documentation and to the tree view.

1109
TOC_EXPAND             = YES
1110
1111
1112
1113
1114
1115

# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
# that can be used as input for Qt's qhelpgenerator to generate a
# Qt Compressed Help (.qch) of the generated HTML documentation.

1116
GENERATE_QHP           = NO
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186

# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
# be used to specify the file name of the resulting .qch file.
# The path specified is relative to the HTML output folder.

QCH_FILE               = "@builddir@/milena.qch"

# The QHP_NAMESPACE tag specifies the namespace to use when generating
# Qt Help Project output. For more information please see
# http://doc.trolltech.com/qthelpproject.html#namespace

QHP_NAMESPACE          = "fr.epita.lrde.olena.milena"

# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
# Qt Help Project output. For more information please see
# http://doc.trolltech.com/qthelpproject.html#virtual-folders

QHP_VIRTUAL_FOLDER     = "milena-2.0"

# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
# add. For more information please see
# http://doc.trolltech.com/qthelpproject.html#custom-filters

QHP_CUST_FILTER_NAME   =

# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
# custom filter to add. For more information please see
# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
# Qt Help Project / Custom Filters</a>.

QHP_CUST_FILTER_ATTRS  =

# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
# project's
# filter section matches.
# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
# Qt Help Project / Filter Attributes</a>.

QHP_SECT_FILTER_ATTRS  =

# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
# be used to specify the location of Qt's qhelpgenerator.
# If non-empty doxygen will try to run qhelpgenerator on the generated
# .qhp file.

QHG_LOCATION           = "qhelpgenerator"

# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
#  will be generated, which together with the HTML files, form an Eclipse help
# plugin. To install this plugin and make it available under the help contents
# menu in Eclipse, the contents of the directory containing the HTML and XML
# files needs to be copied into the plugins directory of eclipse. The name of
# the directory within the plugins directory should be the same as
# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
# the help appears.

GENERATE_ECLIPSEHELP   = NO

# A unique identifier for the eclipse help plugin. When installing the plugin
# the directory name containing the HTML and XML files should also have
# this name.

ECLIPSE_DOC_ID         = org.doxygen.Project

# The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs)
# at top of each HTML page. The value NO (the default) enables the index and
# the value YES disables it. Since the tabs have the same information as the
# navigation tree you can set this option to NO if you already set
# GENERATE_TREEVIEW to YES.

1187
DISABLE_INDEX          = NO
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198

# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
# structure should be generated to display hierarchical information.
# If the tag value is set to YES, a side panel will be generated
# containing a tree-like index structure (just like the one that
# is generated for HTML Help). For this to work a browser that supports
# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
# Windows users are probably better off using the HTML help feature.
# Since the tree basically has the same information as the tab index you
# could consider to set DISABLE_INDEX to NO when enabling this option.

1199
GENERATE_TREEVIEW      = YES
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211

# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values
# (range [0,1..20]) that doxygen will group on one line in the generated HTML
# documentation. Note that a value of 0 will completely suppress the enum
# values from appearing in the overview section.

ENUM_VALUES_PER_LINE   = 4

# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
# used to set the initial width (in pixels) of the frame in which the tree
# is shown.

1212
TREEVIEW_WIDTH         = 250
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280

# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
# links to external symbols imported via tag files in a separate window.

EXT_LINKS_IN_WINDOW    = NO

# Use this tag to change the font size of Latex formulas included
# as images in the HTML documentation. The default is 10. Note that
# when you change the font size after a successful doxygen run you need
# to manually remove any form_*.png images from the HTML output directory
# to force them to be regenerated.

FORMULA_FONTSIZE       = 10

# Use the FORMULA_TRANPARENT tag to determine whether or not the images
# generated for formulas are transparent PNGs. Transparent PNGs are
# not supported properly for IE 6.0, but are supported on all modern browsers.
# Note that when changing this option you need to delete any form_*.png files
# in the HTML output before the changes have effect.

FORMULA_TRANSPARENT    = YES

# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
# (see http://www.mathjax.org) which uses client side Javascript for the
# rendering instead of using prerendered bitmaps. Use this if you do not
# have LaTeX installed or if you want to formulas look prettier in the HTML
# output. When enabled you may also need to install MathJax separately and
# configure the path to it using the MATHJAX_RELPATH option.

USE_MATHJAX            = NO

# When MathJax is enabled you need to specify the location relative to the
# HTML output directory using the MATHJAX_RELPATH option. The destination
# directory should contain the MathJax.js script. For instance, if the mathjax
# directory is located at the same level as the HTML output directory, then
# MATHJAX_RELPATH should be ../mathjax. The default value points to
# the MathJax Content Delivery Network so you can quickly see the result without
# installing MathJax.
# However, it is strongly recommended to install a local
# copy of MathJax from http://www.mathjax.org before deployment.

MATHJAX_RELPATH        = http://cdn.mathjax.org/mathjax/latest

# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension
# names that should be enabled during MathJax rendering.

MATHJAX_EXTENSIONS     =

# When the SEARCHENGINE tag is enabled doxygen will generate a search box
# for the HTML output. The underlying search engine uses javascript
# and DHTML and should work on any modern browser. Note that when using
# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
# (GENERATE_DOCSET) there is already a search function so this one should
# typically be disabled. For large projects the javascript based search engine
# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.

SEARCHENGINE           = YES

# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
# implemented using a PHP enabled web server instead of at the web client
# using Javascript. Doxygen will generate the search PHP script and index
# file to put on the web server. The advantage of the server
# based approach is that it scales better to large projects and allows
# full text search. The disadvantages are that it is more difficult to setup
# and does not have live searching capabilities.

SERVER_BASED_SEARCH    = NO

1281
1282
1283
#---------------------------------------------------------------------------
# configuration options related to the LaTeX output
#---------------------------------------------------------------------------
1284
1285
1286
1287

# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
# generate Latex output.

1288
GENERATE_LATEX         = YES
1289
1290
1291
1292
1293

# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `latex' will be used as the default path.

1294
LATEX_OUTPUT           = latex
1295
1296
1297
1298
1299
1300
1301

# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
# invoked. If left blank `latex' will be used as the default command name.
# Note that when enabling USE_PDFLATEX this option is only used for
# generating bitmaps for formulas in the HTML output, but not in the
# Makefile that is written to the output directory.

1302
LATEX_CMD_NAME         = latex
1303
1304
1305
1306
1307

# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
# generate index for LaTeX. If left blank `makeindex' will be used as the
# default command name.

1308
MAKEINDEX_CMD_NAME     = makeindex
1309
1310
1311
1312
1313

# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
# LaTeX documents. This may be useful for small projects and may help to
# save some trees in general.

1314
COMPACT_LATEX          = NO
1315
1316
1317
1318
1319

# The PAPER_TYPE tag can be used to set the paper type that is used
# by the printer. Possible values are: a4, letter, legal and
# executive. If left blank a4wide will be used.

1320
PAPER_TYPE             = a4wide
1321
1322
1323
1324

# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
# packages that should be included in the LaTeX output.

1325
EXTRA_PACKAGES         =
1326
1327
1328
1329
1330
1331

# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
# the generated latex document. The header should contain everything until
# the first chapter. If it is left blank doxygen will generate a
# standard header. Notice: only use this tag if you know what you are doing!

1332
LATEX_HEADER           =
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345

# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for
# the generated latex document. The footer should contain everything after
# the last chapter. If it is left blank doxygen will generate a
# standard footer. Notice: only use this tag if you know what you are doing!

LATEX_FOOTER           =

# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated
# is prepared for conversion to pdf (using ps2pdf). The pdf file will
# contain links (just like the HTML output) instead of page references
# This makes the output suitable for online browsing using a pdf viewer.

1346
PDF_HYPERLINKS         = YES
1347
1348
1349
1350
1351

# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of
# plain latex in the generated Makefile. Set this option to YES to get a
# higher quality PDF documentation.

1352
USE_PDFLATEX           = YES
1353
1354
1355
1356
1357
1358

# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode.
# command to the generated LaTeX files. This will instruct LaTeX to keep
# running if errors occur, instead of asking the user for help.
# This option is also used when generating formulas in HTML.

1359
LATEX_BATCHMODE        = YES
1360
1361
1362
1363
1364

# If LATEX_HIDE_INDICES is set to YES then doxygen will not
# include the index chapters (such as File Index, Compound Index, etc.)
# in the output.

1365
LATEX_HIDE_INDICES     = NO
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379

# If LATEX_SOURCE_CODE is set to YES then doxygen will include
# source code with syntax highlighting in the LaTeX output.
# Note that which sources are shown also depends on other settings
# such as SOURCE_BROWSER.

LATEX_SOURCE_CODE      = NO

# The LATEX_BIB_STYLE tag can be used to specify the style to use for the
# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See
# http://en.wikipedia.org/wiki/BibTeX for more info.

LATEX_BIB_STYLE        = plain

1380
1381
1382
#---------------------------------------------------------------------------
# configuration options related to the RTF output
#---------------------------------------------------------------------------
1383
1384
1385
1386
1387

# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output
# The RTF output is optimized for Word 97 and may not look very pretty with
# other RTF readers or editors.

1388
GENERATE_RTF           = NO
1389
1390
1391
1392
1393

# The RTF_OUTPUT tag is used to specify where the RTF docs will be put.
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `rtf' will be used as the default path.

1394
RTF_OUTPUT             = rtf
1395
1396
1397
1398
1399

# If the COMPACT_RTF tag is set to YES Doxygen generates more compact
# RTF documents. This may be useful for small projects and may help to
# save some trees in general.

1400
COMPACT_RTF            = NO
1401
1402
1403
1404
1405
1406
1407
1408

# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated
# will contain hyperlink fields. The RTF file will
# contain links (just like the HTML output) instead of page references.
# This makes the output suitable for online browsing using WORD or other
# programs which support those fields.
# Note: wordpad (write) and others do not support links.

1409
RTF_HYPERLINKS         = NO
1410
1411
1412
1413
1414

# Load style sheet definitions from file. Syntax is similar to doxygen's
# config file, i.e. a series of assignments. You only have to provide
# replacements, missing definitions are set to their default value.

1415
RTF_STYLESHEET_FILE    =
1416
1417
1418
1419

# Set optional variables used in the generation of an rtf document.
# Syntax is similar to doxygen's config file.

1420
RTF_EXTENSIONS_FILE    =
1421

1422
1423
1424
#---------------------------------------------------------------------------
# configuration options related to the man page output
#---------------------------------------------------------------------------
1425
1426
1427
1428

# If the GENERATE_MAN tag is set to YES (the default) Doxygen will
# generate man pages

1429
GENERATE_MAN           = NO
1430
1431
1432
1433
1434

# The MAN_OUTPUT tag is used to specify where the man pages will be put.
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `man' will be used as the default path.

1435
MAN_OUTPUT             = man
1436
1437
1438
1439

# The MAN_EXTENSION tag determines the extension that is added to
# the generated man pages (default is the subroutine's section .3)

1440
MAN_EXTENSION          = .3
1441
1442
1443
1444
1445
1446
1447

# If the MAN_LINKS tag is set to YES and Doxygen generates man output,
# then it will generate one additional man file for each entity
# documented in the real man page(s). These additional files
# only source the real man page, but without them the man command
# would be unable to find the correct page. The default is NO.

1448
MAN_LINKS              = NO
1449

1450
1451
1452
#---------------------------------------------------------------------------
# configuration options related to the XML output
#---------------------------------------------------------------------------
1453
1454
1455
1456
1457

# If the GENERATE_XML tag is set to YES Doxygen will
# generate an XML file that captures the structure of
# the code including all documentation.

1458
GENERATE_XML           = NO
1459
1460
1461
1462
1463

# The XML_OUTPUT tag is used to specify where the XML pages will be put.
# If a relative path is entered the value of OUTPUT_DIRECTORY will be
# put in front of it. If left blank `xml' will be used as the default path.

1464
XML_OUTPUT             = xml
1465
1466
1467
1468
1469

# The XML_SCHEMA tag can be used to specify an XML schema,
# which can be used by a validating XML parser to check the
# syntax of the XML files.

1470
XML_SCHEMA             =
1471
1472
1473
1474
1475

# The XML_DTD tag can be used to specify an XML DTD,
# which can be used by a validating XML parser to check the
# syntax of the XML files.

1476
XML_DTD                =
1477
1478
1479
1480
1481
1482

# If the XML_PROGRAMLISTING tag is set to YES Doxygen will
# dump the program listings (including syntax highlighting
# and cross-referencing information) to the XML output. Note that
# enabling this will significantly increase the size of the XML output.

1483
XML_PROGRAMLISTING     = YES
1484

1485
1486
1487
#---------------------------------------------------------------------------
# configuration options for the AutoGen Definitions output
#---------------------------------------------------------------------------
1488
1489
1490
1491
1492
1493
1494

# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will
# generate an AutoGen Definitions (see autogen.sf.net) file
# that captures the structure of the code including all
# documentation. Note that this feature is still experimental
# and incomplete at the moment.

1495
GENERATE_AUTOGEN_DEF   = NO
1496

1497
1498
1499
#---------------------------------------------------------------------------
# configuration options related to the Perl module output
#---------------------------------------------------------------------------
1500
1501
1502
1503
1504
1505
1506

# If the GENERATE_PERLMOD tag is set to YES Doxygen will
# generate a Perl module file that captures the structure of
# the code including all documentation. Note that this
# feature is still experimental and incomplete at the
# moment.

1507
GENERATE_PERLMOD       = NO
1508
1509
1510
1511
1512

# If the PERLMOD_LATEX tag is set to YES Doxygen will generate
# the necessary Makefile rules, Perl scripts and LaTeX code to be able
# to generate PDF and DVI output from the Perl module output.

1513
PERLMOD_LATEX          = NO
1514
1515
1516
1517
1518
1519
1520
1521
1522

# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be
# nicely formatted so it can be parsed by a human reader.
# This is useful
# if you want to understand what is going on.
# On the other hand, if this
# tag is set to NO the size of the Perl module output will be much smaller
# and Perl will parse it just the same.

1523
PERLMOD_PRETTY         = YES
1524
1525
1526
1527
1528
1529

# The names of the make variables in the generated doxyrules.make file
# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX.
# This is useful so different doxyrules.make files included by the same
# Makefile don't overwrite each other's variables.

1530
PERLMOD_MAKEVAR_PREFIX =
1531

1532
#---------------------------------------------------------------------------
1533
# Configuration options related to the preprocessor
1534
#---------------------------------------------------------------------------
1535
1536
1537
1538
1539

# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will
# evaluate all C-preprocessor directives found in the sources and include
# files.

1540
ENABLE_PREPROCESSING   = YES
1541
1542
1543
1544
1545
1546

# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro
# names in the source code. If set to NO (the default) only conditional
# compilation will be performed. Macro expansion can be done in a controlled
# way by setting EXPAND_ONLY_PREDEF to YES.

Thierry Geraud's avatar
Thierry Geraud committed
1547
MACRO_EXPANSION        = YES
1548
1549
1550
1551
1552

# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES
# then the macro expansion is limited to the macros specified with the
# PREDEFINED and EXPAND_AS_DEFINED tags.

1553
EXPAND_ONLY_PREDEF     = NO
1554
1555
1556
1557

# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files
# pointed to by INCLUDE_PATH will be searched when a #include is found.

1558
SEARCH_INCLUDES        = YES
1559
1560
1561
1562
1563

# The INCLUDE_PATH tag can be used to specify one or more directories that
# contain include files that are not input files but should be processed by
# the preprocessor.

1564
INCLUDE_PATH           = "@boostcppflags@"
1565
1566
1567
1568
1569
1570

# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard
# patterns (like *.h and *.hpp) to filter out the header-files in the
# directories. If left blank, the patterns specified with FILE_PATTERNS will
# be used.

1571
INCLUDE_FILE_PATTERNS  =
1572
1573
1574
1575
1576
1577
1578
1579
1580

# The PREDEFINED tag can be used to specify one or more macro names that
# are defined before the preprocessor is started (similar to the -D option of
# gcc). The argument of the tag is a list of macros of the form: name
# or name=definition (no spaces). If the definition and the = are
# omitted =1 is assumed. To prevent a macro definition from being
# undefined via #undef or recursively expanded use the := operator
# instead of the = operator.

1581
1582
PREDEFINED             = MLN_INCLUDE_ONLY \
		         "for_all(x)=for(x.start(); x.is_valid(); x.next())" \
1583
1584
1585
1586
1587
                         "for_all_2(x1, x2)=for(x1.start(), x2.start();	x1.is_valid(); x1.next(), x2.next())" \
                         "for_all_3(x1, x2, x3)=for(x1.start(), x2.start(), x3.start();	x1.is_valid(); x1.next(), x2.next(), x3.next())" \
                         "for_all_remaining(x)=if (! x.is_valid()) {} else while (x.next(), x.is_valid())" \
                         "mlc_unqualif(T)=typename mln::metal::unqualif<T>::ret" \
                         "mlc_equal(T1,T2)=mln::metal::equal<T1,T2>" \
1588
			 "mlc_bool(B)=mln::metal::bool_<( B )>" \
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
                         "mln_piter(T)=typename T::piter" \
                         "mln_fwd_piter(T)=typename T::fwd_piter" \
                         "mln_bkd_piter(T)=typename T::bkd_piter" \
                         "mln_qiter(T)=typename T::qiter" \
                         "mln_fwd_qiter(T)=typename T::fwd_qiter" \
                         "mln_bkd_qiter(T)=typename T::bkd_qiter" \
                         "mln_niter(T)=typename T::niter" \
                         "mln_fwd_niter(T)=typename T::fwd_niter" \
                         "mln_bkd_niter(T)=typename T::bkd_niter" \
                         "mln_viter(T)=typename T::viter" \
                         "mln_fwd_viter(T)=typename T::fwd_viter" \
                         "mln_bkd_viter(T)=typename T::bkd_viter" \
                         "mln_result(T)=typename T::result" \
                         "mln_enc(T)=typename T::enc" \
                         "mln_value(T)=typename T::value" \
                         "mln_qlf_value(T)=typename T::qlf_value" \
Guillaume Lazzara's avatar
Guillaume Lazzara committed
1605
                         "mln_domain(T)=typename T::domain_t" \
1606
1607
1608
1609
1610
1611
                         "mln_sum(T)=typename mln::value::props<T>::sum" \
                         "mln_vset(T)=typename T::vset" \
                         "mln_rvalue(T)=typename T::rvalue" \
                         "mln_lvalue(T)=typename T::lvalue" \
                         "mln_mesh(T)=typename T::mesh" \
                         "mln_coord(T)=typename T::coord" \
1612
1613
1614
                         "mln_site(T)=typename T::site" \
                         "mln_psite(T)=typename T::psite" \
                         "mln_dpsite(T)=typename T::dpsite" \
1615
1616
                         "mln_accu_with(A, T)=typename A::template with< T >::ret" \
                         "mln_trait_op_div(L, R)=typename mln::trait::op::div< L , R >::ret" \
1617
1618
                         "mln_trait_op_less(L, R)=typename mln::trait::op::less< L , R >::ret" \
                         "mln_trait_op_minus(L, R)=typename mln::trait::op::minus< L , R >::ret" \
1619
                         "mln_trait_op_mod(L, R)=typename mln::trait::op::mod< L , R >::ret" \
1620
1621
                         "mln_trait_op_plus(L, R)=typename mln::trait::op::plus< L , R >::ret" \
                         "mln_trait_op_times(L, R)=typename mln::trait::op::times< L , R >::ret" \
1622
                         "mln_trait_op_uminus(T)=typename mln::trait::op::uminus< T >::ret" \
1623
1624
                         "mln_ch_value(I, V)=typename mln::trait::ch_value< I, V >::ret" \
                         "mlc_unqualif_(T)=mln::metal::unqualif<T>::ret" \
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
                         "mln_piter_(T)=T::piter" \
                         "mln_fwd_piter_(T)=T::fwd_piter" \
                         "mln_bkd_piter_(T)=T::bkd_piter" \
                         "mln_qiter_(T)=T::qiter" \
                         "mln_fwd_qiter_(T)=T::fwd_qiter" \
                         "mln_bkd_qiter_(T)=T::bkd_qiter" \
                         "mln_niter_(T)=T::niter" \
                         "mln_fwd_niter_(T)=T::fwd_niter" \
                         "mln_bkd_niter_(T)=T::bkd_niter" \
                         "mln_viter_(T)=T::viter" \
                         "mln_fwd_viter_(T)=T::fwd_viter" \
                         "mln_bkd_viter_(T)=T::bkd_viter" \
                         "mln_result_(T)=T::result" \
                         "mln_enc_(T)=T::enc" \
                         "mln_value_(T)=T::value" \
                         "mln_qlf_value_(T)=T::qlf_value" \
Guillaume Lazzara's avatar
Guillaume Lazzara committed
1641
                         "mln_domain_(T)=T::domain_t" \
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
                         "mln_sum_(T)=mln::value::props<T>::sum" \
                         "mln_vset_(T)=T::vset" \
                         "mln_rvalue_(T)=T::rvalue" \
                         "mln_lvalue_(T)=T::lvalue" \
                         "mln_mesh_(T)=T::mesh" \
                         "mln_coord_(T)=T::coord" \
                         "mln_site_(T)=T::site" \
                         "mln_psite_(T)=T::psite" \
                         "mln_dpsite_(T)=T::dpsite" \
                         "mln_accu_with_(A, T)=A::template with< T >::ret" \
                         "mln_trait_op_plus_(L, R)=mln::trait::op::plus< L , R >::ret" \
                         "mln_trait_op_minus_(L, R)=mln::trait::op::minus< L , R >::ret" \
                         "mln_trait_op_times_(L, R)=mln::trait::op::times< L , R >::ret" \
                         "mln_trait_op_div_(L, R)=mln::trait::op::div< L , R >::ret" \
                         "mln_trait_op_mod_(L, R)=mln::trait::op::mod< L , R >::ret" \
                         "mln_trait_op_uminus_(T)=mln::trait::op::uminus< T >::ret" \
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
                         "mln_ch_value_(I, V)=typename mln::trait::ch_value< I, V >::ret" \
                         "mln_ch_value(I, V)_=mln::trait::ch_value< I, V >::ret" \
                         "mln_morpher_lvalue(I)=typename internal::morpher_lvalue_<I>::ret" \
                         "mln_concrete(I)=typename mln::trait::concrete< I >::ret" \
                         "mln_concrete_ch_value(I, V)=typename mln::trait::ch_value< typename mln::trait::concrete< I >::ret, V >::ret" \
                         "mlc_const(T)=typename mln::metal::const_< T >::ret" \
                         "mlc_const_return(T)=typename mln::metal::const_return_< T >::ret" \
                         "mln_element(T)=typename T::element" \
                         "mln_element_(T)=T::element" \
                         "mln_delta(T)=typename T::delta" \
                         "mln_delta_(T)=T::delta" \
                         "mln_dpoint(T)=typename T::dpoint" \
                         "mln_dpoint_(T)=T::dpoint" \
                         "mln_point(T)=typename T::point" \
                         "mln_point_(T)=T::point" \
                         "mln_gradient_component(I)=typename mln::trait::ch_value< I, mln::value::props< typename I::value >::sum >::ret" \
                         "mln_gradient(I)=mln::value::stack_image< I::point::dim, mln::trait::ch_value< I, mln::value::props< typename I::value >::sum >::ret >" \
                         "mln_trait_value_sum_product(T, U)=typename mln::trait::value_< mln_trait_op_times(T,U) >::sum" \
                         "mln_sum_product(T, U)=typename mln::trait::value_< mln_trait_op_times(T,U) >::sum" \
                         "mln_deduce(T, A1, A2)=typename T::A1::A2" \
                         "mln_graph_element(T)=typename T::graph_element" \
                         "mln_graph_element_(T)=T::graph_element" \
                         "mln_fun_vv2v(F, L, R)=mln::fun::vv2v::F< mln_value(L), mln_value(R) >" \
                         "mln_fun_vv2v_result(F, L, R)=typename mln_fun_vv2v(F, L, R)::result" \
                         "mln_ch_fun_vv2v(F, L, R)=typename mln::trait::ch_value< L, typename mln_fun_vv2v(F, L, R)::result >::ret" \
                         "mln_meta_accu_result(A, T)=typename mln::internal::meta_accu_ret_result_helper<A,T>::result" \
                         "mln_meta_accu_result_(A, T)=mln::internal::meta_accu_ret_result_helper<A,T>::result" \
                         "mln_q_subject(T)=typename T::q_subject" \
                         "mln_q_subject(T)_=T::q_subject" \
                         "mlc_is_a(T, M)=mln::metal::is_a<T, M>" \
                         "mlc_is_a__1comma(Tleft, Tright, M)=mln::metal::is_a<Tleft, Tright, M>" \
                         "mlc_is_not_a(T, M)=mln::metal::is_not_a< T, M >" \
1690
			 "mlc_is_not(T, U)=mln::metal::is_not< T, U >" \
1691
1692
                         "mlc_converts_to(T, U)=mln::metal::converts_to< T, U >" \
                         "mlc_not_equal(T1, T2)=mln::metal::not_equal< T1, T2 >" \
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
			 "mlc_is(T, U)=mln::metal::is< T, U >" \
			 "mlc_and(B1, B2)=mln::metal::and_< B1, B2 >" \
			 "mln_trait_window_size(W)=typename mln::trait::window_< W >::size" \
			 "mln_trait_window_support(W)=typename mln::trait::window_< W >::support" \
			 "mln_trait_window_definition(W)=typename mln::trait::window_< W >::definition" \
			 "mln_is_simple_window(W)=mln::metal::and_< mlc_is(mln_trait_window_size(W), \
			  			  mln::trait::window::size::fixed), \
						  mln::metal::and_< mlc_is(mln_trait_window_support(W), \
						  mln::trait::window::support::regular), \
						  mlc_is(mln_trait_window_definition(W), \
						  mln::trait::window::definition::unique) > >" 		\
			 "mln_is_fastest_IW(I, W)=mlc_and(mlc_is(mln_trait_image_speed(I),  		\
			  	       		         trait::image::speed::fastest),			\
							 mln_is_simple_window(W))"		\
1707
1708
1709
1710
1711
1712
                         "BOOST_PP_LOCAL_ITERATE()=<boost/preprocessor/iteration/detail/local.hpp>" \
			 "mln_ch_convolve(I, W)=typename mln::linear::ch_convolve<I, W>::ret" \
			 "mln_ch_convolve_(I, W)=mln::linear::ch_convolve<I, W>::ret" \
			 "mln_ch_convolve_grad(I, W)=typename mln::trait::ch_value< I, algebra::vec< I::site::dim, typename mln::linear::ch_convolve<I,W>::ret::value > >::ret" \
			 "mln_ch_convolve_grad_(I, W)=mln::trait::ch_value< I, algebra::vec< I::site::dim, mln::linear::ch_convolve<I,W>::ret::value > >::ret"

1713
1714
1715
1716
1717
1718

# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then
# this tag can be used to specify a list of macro names that should be expanded.
# The macro definition that is found in the sources will be used.
# Use the PREDEFINED tag if you want to use a different macro definition that
# overrules the definition found in the source code.
1719

Guillaume Lazzara's avatar