From: <cli...@li...> - 2010-08-12 12:05:22
|
Send clisp-cvs mailing list submissions to cli...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/clisp-cvs or, via email, send a message with subject or body 'help' to cli...@li... You can reach the person managing the list at cli...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of clisp-cvs digest..." CLISP CVS commits for today Today's Topics: 1. clisp/doc impbody.xml,1.604,1.605 (Sam Steingold) 2. clisp/doc impbody.xml,1.605,1.606 (Sam Steingold) ---------------------------------------------------------------------- Message: 1 Date: Wed, 11 Aug 2010 17:48:07 +0000 From: Sam Steingold <sd...@us...> Subject: clisp/doc impbody.xml,1.604,1.605 To: cli...@li... Message-ID: <E1O...@sf...> Update of /cvsroot/clisp/clisp/doc In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv15528 Modified Files: impbody.xml Log Message: add "compile-file-return" and document initial values of *compile-verbose* et al Index: impbody.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/impbody.xml,v retrieving revision 1.604 retrieving revision 1.605 diff -u -d -r1.604 -r1.605 --- impbody.xml 16 Jul 2010 16:27:45 -0000 1.604 +++ impbody.xml 11 Aug 2010 17:48:03 -0000 1.605 @@ -5106,7 +5106,7 @@ <ulink role="clhs" url="chap-24"/></title> <para>The compiler can be called not only by the functions &compile;, - &compile-file; and &disassemble;, but also by the declaration + &compile-file-my; and &disassemble;, but also by the declaration &compile-decl;.</para> <section id="compilefile"><title>Function &compile-file;</title> @@ -5148,12 +5148,14 @@ <para>The variables <firstterm>&compile-warn; <indexterm id="compile-warn" significance="preferred"> - <primary>*COMPILE-WARNINGS*</primary></indexterm></firstterm>, - &compile-verbose-var;, &compile-print-var; provide defaults for the - &warnings-k;, &verbose-k;, &print-k; keyword arguments, respectively, - and are bound by &compile-file; to the values of the arguments, i.e., - these arguments are recursive.</para> + <primary>*COMPILE-WARNINGS*</primary></indexterm></firstterm> + (initially set to &t;), &compile-verbose-var; (initially set to &t;, + affected by &opt-v;) &compile-print-var; (initially set to &nil;, + affected by &opt-v;) provide defaults for the &warnings-k;, &verbose-k;, + &print-k; keyword arguments, respectively, and are bound by &compile-file; + to the values of the arguments, i.e., these arguments are recursive.</para> +<section id="compile-file-output"><title>Output files</title> <para>For each input file (default file type: &lisp-file;) the following files are generated: <informaltable id="compile-file-new-files-table" frame="all"> @@ -5184,6 +5186,30 @@ compile the first file with &clisp;, the second file will be <emphasis>clobbered</emphasis> if you have any &ffi-pac; forms in the first one!</para></warning> +</section> + +<section id="compile-file-return"><title>Return values</title> +<para>As per &clhs;, &compile-file; returns 3 values: +<variablelist><varlistentry><term>output-truename</term> + <listitem><simpara>the truename of the output &fasl-file;, or &nil; + if the file could not be created, in which case the compilation is + considered to have failed</simpara></listitem></varlistentry> +<varlistentry><term>warnings-p</term> + <listitem><simpara>&nil; if no conditions of type &error-t; or &warning-t; + were detected during compilation, and the number of such conditions otherwise +</simpara></listitem></varlistentry> +<varlistentry><term>failure-p</term> + <listitem><simpara>&nil; if no conditions of type &error-t; or &warning-t; + (other than &style-warning-t;) were detected during compilation, + and the number of such conditions otherwise +</simpara></listitem></varlistentry></variablelist> +Since &clisp; tends to be relatively generous with warnings + (see, e.g., <xref linkend="flocont"/>), the non-&nil; tertiary return value + (called <replaceable>failure-p</replaceable>) does ¬-e; indicated a + failure of compilation. +The correct way to check whether &compile-file; has failed is the +primary return value.</para> +</section> </section> ------------------------------ Message: 2 Date: Wed, 11 Aug 2010 18:13:54 +0000 From: Sam Steingold <sd...@us...> Subject: clisp/doc impbody.xml,1.605,1.606 To: cli...@li... Message-ID: <E1O...@sf...> Update of /cvsroot/clisp/clisp/doc In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv20091 Modified Files: impbody.xml Log Message: fix last patch Index: impbody.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/impbody.xml,v retrieving revision 1.605 retrieving revision 1.606 diff -u -d -r1.605 -r1.606 --- impbody.xml 11 Aug 2010 17:48:03 -0000 1.605 +++ impbody.xml 11 Aug 2010 18:13:50 -0000 1.606 @@ -5189,7 +5189,7 @@ </section> <section id="compile-file-return"><title>Return values</title> -<para>As per &clhs;, &compile-file; returns 3 values: +<para>As per &ansi-cl;, &compile-file; returns 3 values: <variablelist><varlistentry><term>output-truename</term> <listitem><simpara>the truename of the output &fasl-file;, or &nil; if the file could not be created, in which case the compilation is @@ -5203,12 +5203,12 @@ (other than &style-warning-t;) were detected during compilation, and the number of such conditions otherwise </simpara></listitem></varlistentry></variablelist> -Since &clisp; tends to be relatively generous with warnings +Since &clisp; tends to be relatively garrulous with warnings (see, e.g., <xref linkend="flocont"/>), the non-&nil; tertiary return value - (called <replaceable>failure-p</replaceable>) does ¬-e; indicated a - failure of compilation. + (called <replaceable>failure-p</replaceable> by the &ansi-cl;) + does ¬-e; indicate a failure of compilation. The correct way to check whether &compile-file; has failed is the -primary return value.</para> + <emphasis>primary</emphasis> return value.</para> </section> </section> ------------------------------ ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev ------------------------------ _______________________________________________ clisp-cvs mailing list cli...@li... https://lists.sourceforge.net/lists/listinfo/clisp-cvs End of clisp-cvs Digest, Vol 52, Issue 9 **************************************** |