--- parser3/INSTALL	2009/06/13 07:28:00	1.52
+++ parser3/INSTALL	2009/09/22 01:57:19	1.55
@@ -1,5 +1,5 @@
 Alexander Petrosian <paf@design.ru> (http://paf.design.ru)
-$Id: INSTALL,v 1.52 2009/06/13 07:28:00 misha Exp $
+$Id: INSTALL,v 1.55 2009/09/22 01:57:19 misha Exp $
 
 1.What is the process to compile Parser3?
 
@@ -127,6 +127,8 @@ $Id: INSTALL,v 1.52 2009/06/13 07:28:00
   WARNING: if you want to use apache configure option --enable-shared=max, do this:
   ./p3runConfigure --enable-shared=max --disable-shared=mod_parser3.c
 
+  Make build-std" command to compile just httpd binary, support stuff won't build with parser libs.
+
 6.
   Since Parser 3.4.0 the several optimisations were implemented.
   If you experience problems you can try to disable them by commenting corresponding defines and recompiling parser3.
@@ -140,7 +142,6 @@ $Id: INSTALL,v 1.52 2009/06/13 07:28:00
     #define OPTIMIZE_BYTECODE_CONSTRUCT               -- $a(expr),  $a[value]
                                                          $.a(expr), $.a[value]
                                                          $self.a(expr), $self.a[value]
-    #define OPTIMIZE_BYTECODE_CONSTRUCT_OBJECT        -- ^class::constructor
     #define OPTIMIZE_BYTECODE_CUT_REM_OPERATOR        -- cut rem operator with any number of params during compilation
     #define OPTIMIZE_BYTECODE_STRING_POOL             -- simplifying string's bytecode into expression
 
@@ -165,4 +166,9 @@ $Id: INSTALL,v 1.52 2009/06/13 07:28:00
                                      write operations it is safe to modify them and save some memory.
     #define CORD_CHARS_CACHE      -- language cords with same language and length are cached and reused.
 
+  src/include/pa_string.h
+    #define STRING_LENGTH_CACHING -- cache String::Body.length() for char* strings
+
+  src/include/pa_hash.h
+    #define HASH_ORDER            -- hash keys are iterated in the order of insertion