svn commit: r651210 - /harmony/enhanced/drlvm/trunk/vm/port/doc/PortReadme.htm

[va...@apache.org]

Author: varlax
Date: Thu Apr 24 02:45:25 2008
New Revision: 651210

URL: http://svn.apache.org/viewvc?rev=651210&view=rev
Log:
Dropped outdated data, added preliminary notes.

Modified:
    harmony/enhanced/drlvm/trunk/vm/port/doc/PortReadme.htm

Modified: harmony/enhanced/drlvm/trunk/vm/port/doc/PortReadme.htm
URL: http://svn.apache.org/viewvc/harmony/enhanced/drlvm/trunk/vm/port/doc/PortReadme.htm?rev=651210&r1=651209&r2=651210&view=diff
==============================================================================
--- harmony/enhanced/drlvm/trunk/vm/port/doc/PortReadme.htm (original)
+++ harmony/enhanced/drlvm/trunk/vm/port/doc/PortReadme.htm Thu Apr 24 02:45:25 2008
@@ -15,10 +15,6 @@
     limitations under the License.
 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<!--
-Author: Alexey V. Varlamov
-Version: $Revision: 1.1.2.1.4.3 $
--->
 <html>
 
 <head>
@@ -27,6 +23,13 @@
 
 <body>
 
+<h3>0. Preliminary Notes</h3>
+
+The porting layer is a work-in-progress and is not yet shaped nicely.
+Currently it consists of quite heterogeneous pieces (APR extensions, logger, 
+encoder, utility templates etc) which do not form unified interface.
+
+
 <h3>1. Design  Notes</h3>
 
 The porting layer design adheres to concepts of APR (<a href="http://apr.apache.org/docs/apr/">Apache
@@ -39,6 +42,7 @@
 Detailed APIs mainly follow the APR standard, but there may not be strict correspondence
 in signatures. Pure C should be used for implementation.
 
+<!-- The below info is outdated
 <h4>Using APR binaries directly</h4>
 Harmony defines its own headers aligned with APR, but does not wrap APR functions
 in code (no delegating calls). Instead, signatures are mapped directly to APR functions
@@ -79,6 +83,8 @@
 <li>Potential confusion in the open community, especially for those experienced in
   APR applications.
 </ul>
+
+-->
 
 <h3>2. Directory structure</h3>