Index: doc/ChangeLog from Giovanni Palma giovanni@lrde.epita.fr * dev/build.texi: Update the file. * dev/srctree.texi: Likewise. * dev/upgrading.texi: Likewise.
+2004-04-15 Giovanni Palma giovanni@lrde.epita.fr + * dev/thanks.texi: Update thanks.
2004-04-15 Niels Van Vliet niels@lrde.epita.fr Index: doc/dev/build.texi --- doc/dev/build.texi Fri, 08 Aug 2003 13:24:29 +0200 burrus_n (oln/p/42_build.texi 1.11 600) +++ doc/dev/build.texi Thu, 15 Apr 2004 17:47:14 +0200 palma_g (oln/p/42_build.texi 1.11 600) @@ -260,10 +260,11 @@
@multitable @columnfractions .33 .66 @item @strong{System} @tab @strong{Compiler} -@item Linux @tab g++ 3.0 and 3.2 +@item Linux @tab g++ 3.0, 3.1, 3.2 and 3.3 @item Linux @tab icc (Intel's C++ Compiler) v7 @item MacOS X @tab g++ 3.1 -@item NetBSD 1.6 @tab g++ 3.2 +@item NetBSD 1.6 @tab g++ 3.2 and 3.3 +@item FreeBSD 5.0 @tab g++ 3.2 and 3.3 @item Cygwin @tab g++ 3.2 @end multitable
@@ -280,8 +281,7 @@ code, especially with intensive inlining. @end itemize
-Actually Olena yet compiles with g++ 2.95, but some wrong code might -be generated with data types. +Actually Olena does not compile with g++ 2.95 anymore.
Compilation time may have important differences between compilers, the following benchmark gives an idea of the time needed to complete a @@ -289,7 +289,6 @@
@multitable @columnfractions .5 .5 @item @strong{Compiler} @tab @strong{Time} -@item g++-2.95 @tab 16m42s @item g++-3.0 @tab 23m20s @item g++-3.2 @tab 20m03s @item icc-7 @tab 12m52s @@ -300,7 +299,6 @@
@multitable @columnfractions .25 .5 .25 @item @strong{Compiler} @tab @strong{Options} @tab @strong{Time} -@item g++-2.95 @tab @option{-O3 -finline-limit-1500} @tab 3m14s @item g++-3.0 @tab @option{-O3 -finline-limit-1500} @tab 2m08s @item g++-3.2 @tab @option{-O3 -finline-limit-1500} @tab 1m50s @item icc-7 @tab @option{-O3} @tab 5m41s Index: doc/dev/srctree.texi --- doc/dev/srctree.texi Thu, 07 Aug 2003 15:22:47 +0200 burrus_n (oln/p/45_srctree.te 1.6 600) +++ doc/dev/srctree.texi Thu, 15 Apr 2004 18:04:54 +0200 palma_g (oln/p/45_srctree.te 1.6 600) @@ -111,6 +111,9 @@ @item oln/morpho/ Morphological operators.
+@item oln/morpher +Generic morphers. + @item oln/level/ Level processing operators.
@@ -186,6 +189,10 @@ @item morpho/ Tests pertaining to morphological operators.
+@cindex @file{tests/morpher/} +@item morpho/ +Tests pertaining to morphers. + @cindex @file{tests/sanity/} @item sanity/ Tests that check that each Olena header can be separately included in @@ -338,43 +345,38 @@ A directory containing Texinfo sources for the Olena Developer's Handbook.
@cindex @file{doc/ref/} -@cindex @file{oln-ref.tex} @item doc/ref/ -A directory containing TeX sources and definitions to build the Reference -Manual. It noticeably contains: +A directory containing script to extract documentation and examples +from source code. It noticeably contains:
@table @file -@item oln-ref.tex -The master TeX file for the Reference Manual. - -@cindex @file{ref-types.tex} -@item ref-types.tex -Handwritten documentation about Olena value types, included in the -Reference Manual. - -@cindex @file{ref-morpho.tex} -@item ref-morpho.tex -@cindex @file{ref-level.tex} -@item ref-level.tex -@cindex @file{processing.tpl} -TeX sources describing Olena components. They are auto-generated by -AutoGen from Olena C++ header files@footnote{more precisely, from C++ -comments}, using definitions in @file{processing.tpl}. +@cindex @file{exdoc.pl} +@item exdoc.pl +Main script to extract code example. + +@cindex @file{img_conv.pl} +@item img_conv.pl +Script to convert image used by extracted code. + +@cindex @file{doxygen.config} +@item doxygen.config +Configuration file used by doxygen.
@cindex @file{Makefile.am} @item Makefile.am Automake definitions that control the build process, which (as of 0.7) depends on GNU Make.
-@item bin/ +@item out/ Auto-generated programs that create the pictures included in the Reference Manual.
@item html/ The HTML version of the Reference Manual.
-@item processing.tpl -AutoGen parameters for generating parts of the Reference Manual. +@item latex/ +The latex version of the Reference Manual. + @end table @end table
Index: doc/dev/upgrading.texi --- doc/dev/upgrading.texi Fri, 22 Aug 2003 12:36:42 +0200 astrid (oln/r/50_upgrading. 1.3 600) +++ doc/dev/upgrading.texi Thu, 15 Apr 2004 17:51:52 +0200 palma_g (oln/r/50_upgrading. 1.3 600) @@ -4,10 +4,16 @@ @chapter Upgrading from older versions
@menu +* Upgrading from 0.9 to 0.10:: * Upgrading from 0.8 to 0.9:: * Upgrading from 0.7 to 0.8:: @end menu
+@node Upgrading from 0.9 to 0.10 +@section Upgrading from 0.9 to 0.10 +Nothing should be done since the this release only provide a new +documentation system and many bug fixes. + @node Upgrading from 0.8 to 0.9 @section Upgrading from 0.8 to 0.9
"Giovanni" == Giovanni Palma giovanni@lrde.epita.fr writes:
Index: doc/ChangeLog from Giovanni Palma giovanni@lrde.epita.fr
- dev/build.texi: Update the file.
- dev/srctree.texi: Likewise.
- dev/upgrading.texi: Likewise.
+2004-04-15 Giovanni Palma giovanni@lrde.epita.fr
- dev/thanks.texi: Update thanks.
2004-04-15 Niels Van Vliet niels@lrde.epita.fr Index: doc/dev/build.texi --- doc/dev/build.texi Fri, 08 Aug 2003 13:24:29 +0200 burrus_n (oln/p/42_build.texi 1.11 600) +++ doc/dev/build.texi Thu, 15 Apr 2004 17:47:14 +0200 palma_g (oln/p/42_build.texi 1.11 600) @@ -260,10 +260,11 @@
@multitable @columnfractions .33 .66 @item @strong{System} @tab @strong{Compiler}
Utiliser @headitem plutôt.
@headitem System @tab Compiler
@multitable @columnfractions .33 .66 @item @strong{System} @tab @strong{Compiler}
Utiliser @headitem plutôt.
@headitem System @tab Compiler
Nouvelle commande (texinfo 4.7). Je n'effectue pas les changements. On demande déjà les dernières mises à jour de beaucoup d'outils.
"Niels" == Niels Van Vliet niels@lrde.epita.fr writes:
@multitable @columnfractions .33 .66 @item @strong{System} @tab @strong{Compiler}
Utiliser @headitem plutôt. @headitem System @tab Compiler
Nouvelle commande (texinfo 4.7). Je n'effectue pas les changements. On demande déjà les dernières mises à jour de beaucoup d'outils.
Euh... C'est pas grave du tout puisque vous fournissez la sortie info, et que la TeX, vous fournissez texinfo.tex. Donc je pense que c'est une hésitation légitime en général, mais pas pour ce cas.
À moins que je ne rate qqch ?