1.1 --- a/configure.ac Tue Oct 05 09:41:05 2004 +0000
1.2 +++ b/configure.ac Thu Oct 07 07:39:42 2004 +0000
1.3 @@ -1,5 +1,5 @@
1.4 dnl Process this file with autoconf to produce a configure script.
1.5 -AC_INIT([LEMON], [0.2], [etik-ol@cs.elte.hu], [lemon])
1.6 +AC_INIT([LEMON], [0.3], [etik-ol@cs.elte.hu], [lemon])
1.7 AC_CONFIG_AUX_DIR([config])
1.8 AM_INIT_AUTOMAKE(1.7)
1.9 AC_CONFIG_SRCDIR([src/lemon/invalid.h])
2.1 --- a/doc/Doxyfile Tue Oct 05 09:41:05 2004 +0000
2.2 +++ b/doc/Doxyfile Thu Oct 07 07:39:42 2004 +0000
2.3 @@ -1,4 +1,4 @@
2.4 -# Doxyfile 1.3.6
2.5 +# Doxyfile 1.3.9
2.6
2.7 # This file describes the settings to be used by the documentation system
2.8 # doxygen (www.doxygen.org) for a project
2.9 @@ -23,7 +23,7 @@
2.10 # This could be handy for archiving the generated documentation or
2.11 # if some version control system is used.
2.12
2.13 -PROJECT_NUMBER = 0.2
2.14 +PROJECT_NUMBER = 0.3
2.15
2.16 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
2.17 # base path where the generated documentation will be put.
2.18 @@ -32,14 +32,24 @@
2.19
2.20 OUTPUT_DIRECTORY =
2.21
2.22 +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
2.23 +# 4096 sub-directories (in 2 levels) under the output directory of each output
2.24 +# format and will distribute the generated files over these directories.
2.25 +# Enabling this option can be useful when feeding doxygen a huge amount of source
2.26 +# files, where putting all generated files in the same directory would otherwise
2.27 +# cause performance problems for the file system.
2.28 +
2.29 +CREATE_SUBDIRS = NO
2.30 +
2.31 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
2.32 # documentation generated by doxygen is written. Doxygen will use this
2.33 # information to generate all constant output in the proper language.
2.34 # The default language is English, other supported languages are:
2.35 -# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch,
2.36 -# Finnish, French, German, Greek, Hungarian, Italian, Japanese, Japanese-en
2.37 -# (Japanese with English messages), Korean, Korean-en, Norwegian, Polish, Portuguese,
2.38 -# Romanian, Russian, Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian.
2.39 +# Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish,
2.40 +# Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese,
2.41 +# Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian,
2.42 +# Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish,
2.43 +# Swedish, and Ukrainian.
2.44
2.45 OUTPUT_LANGUAGE = English
2.46
2.47 @@ -95,16 +105,25 @@
2.48 # path before files name in the file list and in the header files. If set
2.49 # to NO the shortest path that makes the file name unique will be used.
2.50
2.51 -FULL_PATH_NAMES = NO
2.52 +FULL_PATH_NAMES = YES
2.53
2.54 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
2.55 # can be used to strip a user-defined part of the path. Stripping is
2.56 # only done if one of the specified strings matches the left-hand part of
2.57 -# the path. It is allowed to use relative paths in the argument list.
2.58 +# the path. The tag can be used to show relative paths in the file list.
2.59 # If left blank the directory from which doxygen is run is used as the
2.60 # path to strip.
2.61
2.62 -STRIP_FROM_PATH =
2.63 +STRIP_FROM_PATH = ../src
2.64 +
2.65 +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
2.66 +# the path mentioned in the documentation of a class, which tells
2.67 +# the reader which header file to include in order to use a class.
2.68 +# If left blank only the name of the header file containing the class
2.69 +# definition is used. Otherwise one should specify the include paths that
2.70 +# are normally passed to the compiler using the -I flag.
2.71 +
2.72 +STRIP_FROM_INC_PATH = ../src
2.73
2.74 # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
2.75 # (but less readable) file names. This can be useful is your file systems
2.76 @@ -211,6 +230,13 @@
2.77
2.78 EXTRACT_LOCAL_CLASSES = YES
2.79
2.80 +# This flag is only useful for Objective-C code. When set to YES local
2.81 +# methods, which are defined in the implementation section but not in
2.82 +# the interface are included in the documentation.
2.83 +# If set to NO (the default) only methods in the interface are included.
2.84 +
2.85 +EXTRACT_LOCAL_METHODS = NO
2.86 +
2.87 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
2.88 # undocumented members of documented classes, files or namespaces.
2.89 # If set to NO (the default) these members will be included in the
2.90 @@ -251,7 +277,7 @@
2.91 # file names in lower-case letters. If set to YES upper-case letters are also
2.92 # allowed. This is useful if you have classes or files whose names only differ
2.93 # in case and if your file system supports case sensitive file names. Windows
2.94 -# users are advised to set this option to NO.
2.95 +# and Mac users are advised to set this option to NO.
2.96
2.97 CASE_SENSE_NAMES = YES
2.98
2.99 @@ -341,6 +367,12 @@
2.100
2.101 SHOW_USED_FILES = YES
2.102
2.103 +# If the sources in your project are distributed over multiple directories
2.104 +# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
2.105 +# in the documentation.
2.106 +
2.107 +SHOW_DIRECTORIES = YES
2.108 +
2.109 #---------------------------------------------------------------------------
2.110 # configuration options related to warning and progress messages
2.111 #---------------------------------------------------------------------------
2.112 @@ -392,7 +424,7 @@
2.113 # with spaces.
2.114
2.115 INPUT = mainpage.dox \
2.116 - graphs.dox \
2.117 + graphs.dox \
2.118 maps.dox \
2.119 coding_style.dox \
2.120 groups.dox \
2.121 @@ -406,7 +438,7 @@
2.122 # and *.h) to filter out the source-files in the directories. If left
2.123 # blank the following patterns are tested:
2.124 # *.c *.cc *.cxx *.cpp *.c++ *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh *.hxx *.hpp
2.125 -# *.h++ *.idl *.odl *.cs *.php *.php3 *.inc
2.126 +# *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm
2.127
2.128 FILE_PATTERNS =
2.129
2.130 @@ -464,10 +496,20 @@
2.131 # by executing (via popen()) the command <filter> <input-file>, where <filter>
2.132 # is the value of the INPUT_FILTER tag, and <input-file> is the name of an
2.133 # input file. Doxygen will then use the output that the filter program writes
2.134 -# to standard output.
2.135 +# to standard output. If FILTER_PATTERNS is specified, this tag will be
2.136 +# ignored.
2.137
2.138 INPUT_FILTER =
2.139
2.140 +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
2.141 +# basis. Doxygen will compare the file name with each pattern and apply the
2.142 +# filter if there is a match. The filters are a list of the form:
2.143 +# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
2.144 +# info on how filters are used. If FILTER_PATTERNS is empty, INPUT_FILTER
2.145 +# is applied to all files.
2.146 +
2.147 +FILTER_PATTERNS =
2.148 +
2.149 # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
2.150 # INPUT_FILTER) will be used to filter the input files when producing source
2.151 # files to browse (i.e. when SOURCE_BROWSER is set to YES).
2.152 @@ -920,7 +962,9 @@
2.153 # are defined before the preprocessor is started (similar to the -D option of
2.154 # gcc). The argument of the tag is a list of macros of the form: name
2.155 # or name=definition (no spaces). If the definition and the = are
2.156 -# omitted =1 is assumed.
2.157 +# omitted =1 is assumed. To prevent a macro definition from being
2.158 +# undefined via #undef or recursively expanded use the := operator
2.159 +# instead of the = operator.
2.160
2.161 PREDEFINED = DOXYGEN
2.162
3.1 --- a/src/work/Doxyfile Tue Oct 05 09:41:05 2004 +0000
3.2 +++ b/src/work/Doxyfile Thu Oct 07 07:39:42 2004 +0000
3.3 @@ -23,7 +23,7 @@
3.4 # This could be handy for archiving the generated documentation or
3.5 # if some version control system is used.
3.6
3.7 -PROJECT_NUMBER = 0.2
3.8 +PROJECT_NUMBER = 0.3
3.9
3.10 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
3.11 # base path where the generated documentation will be put.