# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 

 # 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 

 # 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.

 # to NO the shortest path that makes the file name unique will be used.

 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 

 # 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 

 # 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 

 # 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. 

 # 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 

 # If left blank the directory from which doxygen is run is used as the 

 # path to strip.

 # path to strip.

 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 

 # 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 path mentioned in the documentation of a class, which tells 

 # the reader which header file to include in order to use a class. 

 # 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 

 # If left blank only the name of the header file containing the class 

 # definition is used. Otherwise one should specify the include paths that 

 # definition is used. Otherwise one should specify the include paths that 

 # are normally passed to the compiler using the -I flag.

 # are normally passed to the compiler using the -I flag.

 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 

 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 

 # (but less readable) file names. This can be useful is your file systems 

 # (but less readable) file names. This can be useful is your file systems 

 # doesn't support long names like on DOS, Mac, or CD-ROM.

 # doesn't support long names like on DOS, Mac, or CD-ROM.

 # The INTERNAL_DOCS tag determines if documentation 

 # The INTERNAL_DOCS tag determines if documentation 

 # that is typed after a \internal command is included. If the tag is set 

 # that is typed after a \internal command is included. If the tag is set 

 # to NO (the default) then the documentation will be excluded. 

 # to NO (the default) then the documentation will be excluded. 

 # Set it to YES to include the internal documentation.

 # Set it to YES to include the internal documentation.

 # If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 

 # 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 

 # 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 

 # 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 

 # in case and if your file system supports case sensitive file names. Windows 

 # here it will be hidden. Use a value of 0 to hide initializers completely. 

 # here it will be hidden. Use a value of 0 to hide initializers completely. 

 # The appearance of the initializer of individual variables and defines in the 

 # The appearance of the initializer of individual variables and defines in the 

 # documentation can be controlled using \showinitializer or \hideinitializer 

 # documentation can be controlled using \showinitializer or \hideinitializer 

 # command in the documentation regardless of this setting.

 # command in the documentation regardless of this setting.

 # Set the SHOW_USED_FILES tag to NO to disable the list of files generated 

 # 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 

 # 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.

 # list will mention the files that were used to generate the documentation.

                          ../../doc/coding_style.dox \

                          ../../doc/coding_style.dox \

                          ../../doc/groups.dox \

                          ../../doc/groups.dox \

                          ../lemon \

                          ../lemon \

                          ../lemon/concept \

                          ../lemon/concept \

                          ../test/test_tools.h \

                          ../test/test_tools.h \

 # If the value of the INPUT tag contains directories, you can use the 

 # 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 

 # 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 

 # and *.h) to filter out the source-files in the directories. If left 

 # blank the following patterns are tested: 

 # blank the following patterns are tested: 

 # The EXAMPLE_PATH tag can be used to specify one or more files or 

 # The EXAMPLE_PATH tag can be used to specify one or more files or 

 # directories that contain example code fragments that are included (see 

 # directories that contain example code fragments that are included (see 

 # the \include command).

 # the \include command).

 # If the value of the EXAMPLE_PATH tag contains directories, you can use the 

 # 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 

 # 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 

 # and *.h) to filter out the source-files in the directories. If left 

 # blank all files are included.

 # blank all files are included.

 #---------------------------------------------------------------------------

 #---------------------------------------------------------------------------

 # The SEARCHENGINE tag specifies whether or not a search engine should be 

 # The SEARCHENGINE tag specifies whether or not a search engine should be 

 # used. If set to NO the values of all tags below this one will be ignored.

 # used. If set to NO the values of all tags below this one will be ignored.