bugfixes for the high-level postgreSQL wrapper

1 files changed, 9 insertions, 24 deletions

diff --git a/web/question.txt b/web/question.txt
index 17a1abfcf..cccac2e1b 100755
--- a/web/question.txt
+++ b/web/question.txt
@@ -25,6 +25,12 @@ flexibility for speed. You get both.
     this programming modell as convenient as possible
 
 
+Why is it named Nimrod?
+-----------------------
+You have to find out for yourself. If you don't find a tongue-in-cheek 
+interpretation you have to look harder.
+
+
 How is Nimrod licensed?
 -----------------------
 
@@ -54,9 +60,9 @@ If you delete the line ``gcc.path = r"$nimrod\dist\mingw\bin"``, Nimrod uses
 the GCC from your ``PATH`` environment variable. 
 
 If you cannot modify ``$nimrod\config\nimrod.cfg``, copy 
-``$nimrod\config\nimrod.cfg`` to ``$APPDATA\nimrod.cfg`` and modify 
-``$APPDATA\nimrod.cfg`` instead. To determine what ``$APPDATA`` means for your
-Windows account, use the shell command::
+``$nimrod\config\nimrod.cfg`` to ``%APPDATA%\nimrod.cfg`` and modify 
+``%APPDATA%\nimrod.cfg`` instead. To determine what ``%APPDATA%`` means for 
+your Windows account, use the shell command::
 
   echo %APPDATA%
 
@@ -90,26 +96,5 @@ different command line arguments try the ``--passc`` and ``--passl`` switches.
 Unsupported compilers contain serious bugs that keep them from bootstrapping
 Nimrod.
 
-The linker outputs strange errors about missing symbols
--------------------------------------------------------
-
-I have seen this bug only with the GNU linker. The reason for this unknown.
-Try recompiling your code with the ``--force_build`` command line switch.
-
-
-Why is compilation so slow?
----------------------------
-
-There are two reasons for this:
 
-(1) Nimrod always recompiles **everything** (but only calls the C compiler for 
-    modules that changed). In a future version, only modules that have changed 
-    will be recompiled.
-(2) The C compiler that is called by Nimrod may be slow.
-    Especially GCC's compile times are not very heady. On Linux you may be able
-    to get `Tiny C <http://bellard.org/tcc/>`_ to work. TCC has excellent 
-    compile times. You should not use TCC for producing the release version 
-    though, as it has no optimizer.
 
-Note that from version 0.7.10 onwards the default build produces an optimized
-binary.