From mantoniotti@common-lisp.net Fri Nov 9 08:56:40 2007 From: mantoniotti To: cl-unification-cvs@common-lisp.net Subject: [cl-unification-cvs] CVS cl-unification/docs/html Date: Fri, 09 Nov 2007 08:56:40 -0500 Message-ID: <20071109135640.27EDC1130@common-lisp.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3877032226444809667==" --===============3877032226444809667== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Update of /project/cl-unification/cvsroot/cl-unification/docs/html In directory clnet:/tmp/cvs-serv1902 Modified Files: index.html=20 Log Message: Changed the position of the disclaimer. --- /project/cl-unification/cvsroot/cl-unification/docs/html/index.html 2007/= 05/21 17:10:26 1.5 +++ /project/cl-unification/cvsroot/cl-unification/docs/html/index.html 2007/= 11/09 13:56:40 1.6 @@ -34,23 +34,6 @@ =20

Common Lisp Extensions: UNIFICATION

=20 - -
- -

- DISCLAIMER: The code associated to these documents is not - completely tested and it is bound to contain errors and omissions. - This documentation may contain errors and omissions as well.

- -

The file COPYING contains a Berkeley-style license. You - are advised to use the code at your own risk. No warranty - whatsoever is provided, the author will not be held responsible for - any effect generated by your use of the library, and you can put - here the scarier extra disclaimer you can think of. -

-
-
-

The notion of unification originated in the field of formal logic (e.g. [R65],) and has been used extensively in Computer Science and Programming Languages. Most @@ -303,6 +286,25 @@ [R56] J. A. Robinson, A machine-oriented logic base= d on the resolution principle, Journal of the ACM, Vol. 12, No. 1, January 1965, Pages 23--49.

+ + +

+
+ +

+ DISCLAIMER: The code associated to these documents is not + completely tested and it is bound to contain errors and omissions. + This documentation may contain errors and omissions as well.

+ +

The file COPYING contains a Berkeley-style license. You + are advised to use the code at your own risk. No warranty + whatsoever is provided, the author will not be held responsible for + any effect generated by your use of the library, and you can put + here the scarier extra disclaimer you can think of. +

+
+
+ =20 =20