From e04555ddb232bb8322de8dd3a00ceeaad48e58a3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Daniel=20Kochma=C5=84ski?= Date: Sat, 8 Aug 2015 18:49:31 +0200 Subject: [PATCH] doc: remove information about clos being optional MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Daniel Kochmański --- doc/preface.xmlf | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/preface.xmlf b/doc/preface.xmlf index 5758f2f74..d17799eda 100644 --- a/doc/preface.xmlf +++ b/doc/preface.xmlf @@ -63,11 +63,10 @@ facilities for memory management, dynamic loading and dumping of binary images, support for multiple threads of execution. The CRS is built into a library that can be linked with the code of the application. &ECL; is - modular: main modules are the program development tools (top level, - debugger, trace, stepper), the compiler, and CLOS. A native implementation - of CLOS is available in &ECL;: one can configure &ECL; with or without CLOS. - A runtime version of &ECL; can be built with just the modules which are - required by the application. + modular: main modules are the program development tools (top level, debugger, + trace, stepper), the compiler, and CLOS. A native implementation of CLOS is + available in &ECL;. A runtime version of &ECL; can be built with just the + modules which are required by the application. The &ECL; compiler compiles from Lisp to C, and then invokes the GNU C compiler to produce binaries. While former releases of ECL @@ -158,6 +157,7 @@ ---- BEGINNING OF COPYRIGHT FOR THE ECL CORE ENVIRONMENT ------------ + Copyright (c) 2015, Daniel Kochmański Copyright (c) 2000, Juan Jose Garcia Ripoll Copyright (c) 1990, 1991, 1993 Giuseppe Attardi Copyright (c) 1984 Taiichi Yuasa and Masami Hagiya