first release

web/download.txt

@@ -4,7 +4,8 @@
 Here you can download the latest version of the Nimrod Compiler.
 Please choose your platform:
 
-* binary and source for Windows (95, 98, XP): `<download/nimrod_win_0.7.0.exe>`_
-* source for Unix (including MacOS X): `<download/nimrod_unix_0.7.0.zip>`_
+* source for Unix (including MacOS X): `<download/nimrod_unix_0.5.1.zip>`_
+* binary and source for Windows (95, 98, XP): `<download/nimrod_windows_0.5.1.zip>`_
+  (includes LLVM and everything else you need)
 
 .. include:: ../install.txt

web/index.txt

@@ -17,18 +17,18 @@ Welcome to the Nimrod programming language
 programming language, that supports procedural, functional, object oriented and 
 generic programming styles while remaining simple and efficient. A special 
 feature that Nimrod inherited from Lisp is that Nimrod's abstract syntax tree
-(*AST*) is part ofthe specification - this allows a powerful macro system which 
+(*AST*) is part of the specification - this allows a powerful macro system which 
 can be used to create domain specific languages.
 
 *Nimrod* is a compiled, garbage-collected systems programming language 
 which has an excellent productivity/performance ratio. Nimrod's design 
-focusses on the 3E: efficiency, expressiveness, elegance (in the order of 
+focuses on the 3E: efficiency, expressiveness, elegance (in the order of 
 priority). 
 
 
 Some more of Nimrod's highlights:
 
-* Native code (currently via compilation to C).
+* Native code generation (currently via compilation to C).
 * Garbage collection, but not dependant on a Virtual Machine.
 * Portable: The Nimrod Compiler runs on Windows, Linux and Mac OS X.
   Porting to other platforms is easy.
@@ -38,12 +38,12 @@ Some more of Nimrod's highlights:
 * Exceptions.
 * Modern type system with local type inference, tuples, variants, etc.
 * User-defineable operators; new operators often easier to read than overloaded
-  ones
+  ones.
 * High level datatypes: strings, sets, sequences, etc.
 * Compile time evaluation without resorting to meta-programming facilities.
-* *Forward* compatibility: If later versions of the language introduce new
+* *Forward* compability: If later versions of the language introduce new
   keywords old code won't break!
-* Bindings to GTK2, X11, the Windows API, the POSIX API. New bindings are 
+* Bindings to GTK2, the Windows API, the POSIX API. New bindings are 
   easily generated in a semi-atomatic way. 
 * A plugable parser system: If you don't like Nimrod's syntax, you can plug in
   a parser and a source renderer for your own syntax!

web/links.txt

@@ -1 +1 @@
-Currently there are no links to other Nimrod-related sites.
+Visit our project page at Launchpad: https://launchpad.net/nimrod.

web/news.txt

@@ -1,7 +1,8 @@
-| `2008-01-12`:newsdate:
-| Nimrod version 0.8.0 has been released!
+| `2008-06-23`:newsdate:
+| Nimrod version |nimrodversion| has been released!
   Get it `here <./download.html>`_.
 
 
-| `2008-01-06`:newsdate:
+| `2008-06-22`:newsdate:
 | This page is finally online!
+

web/question.txt

@@ -22,11 +22,10 @@ Especially GCC's compile times are a bad joke. On Linux you may be able to get
 compile times. You should not use TCC for producing the release version
 though, as it has no optimizer.
 
-Experimental features are the *AST cache* and the *C file cache*. Both
-are not activated. To activate, add to your ``nimrod.cfg`` file the following
-lines::
+An experimental feature is the *C file cache*. It is not
+activated. To activate, add to your ``nimrod.cfg`` file the following
+line::
 
-  --ast_cache:on
   --c_file_cache:on
 
 
@@ -68,6 +67,11 @@ If your C compiler is not in the above list, try using the
 different command line arguments you have to edit the ``extccomp``
 module to add support for it and recompile the compiler. Please
 contribute a patch in this case.
+
+`The linker outputs strange errors about missing symbols`:Q:
+
+I have seen this bug only with the GNU linker. The reason for this unknown. 
+Try recompiling your code with the ``--c_file_cache:off`` command line switch.
 
 
 `Calling the C compiler fails - what's wrong?`:Q: