Menu
▾
▴
clisp-cvs Digest, Vol 29, Issue 9
|
From: <cli...@li...> - 2008-09-11 19:04:21
|
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 mop-ent.xml,2.19,2.20 mop.xml,2.86,2.87 (Sam Steingold) 2. clisp/doc mop-ent.xml,2.20,2.21 mop.xml,2.87,2.88 (Sam Steingold) 3. clisp/doc mop.xml,2.88,2.89 (Sam Steingold) 4. clisp/doc impext.xml,1.541,1.542 (Sam Steingold) 5. clisp/doc mop-ent.xml,2.21,2.22 (Sam Steingold) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Sep 2008 15:31:49 +0000 From: Sam Steingold <sd...@us...> Subject: clisp/doc mop-ent.xml,2.19,2.20 mop.xml,2.86,2.87 To: cli...@li... Message-ID: <E1K...@ma...> Update of /cvsroot/clisp/clisp/doc In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv3520/doc Modified Files: mop-ent.xml mop.xml Log Message: (cam-cdf): new entity Index: mop.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/mop.xml,v retrieving revision 2.86 retrieving revision 2.87 diff -u -d -r2.86 -r2.87 --- mop.xml 11 Sep 2008 15:24:53 -0000 2.86 +++ mop.xml 11 Sep 2008 15:31:47 -0000 2.87 @@ -2775,15 +2775,15 @@ <para>Discriminating functions call &compute-applicable-methods-mop; and &compute-applicable-methods-UC; to compute the methods -applicable to the generic functions arguments. Applicable methods are -combined by &compute-effective-method; to produce -an <firstterm>effective method</firstterm>. +applicable to the generic functions arguments. +Applicable methods are combined by &compute-effective-method; to +produce an <firstterm>effective method</firstterm>. Provisions are made to allow memoization of the method applicability and effective methods computations. (See the description of &compute-discriminating-function; for details.)</para> -<para>The body of method definitions are processed by -&make-method-lambda;. The result of this generic function is a &lambda-expr; +<para>The body of method definitions are processed by &make-method-lambda;. +The result of this generic function is a &lambda-expr; which is processed by either &compile; or &compile-file; to produce a <firstterm>method function</firstterm>. The arguments received by the method function are controlled by the &call-method; forms appearing in @@ -3218,14 +3218,7 @@ precedence order with the most specific method appearing first. If no methods are applicable to the supplied arguments the empty list is returned.</simpara> - <simpara>When a generic function is invoked, the discriminating - function must determine the ordered list of methods applicable to the - arguments. Depending on the generic function and the arguments, this - is done in one of three ways: using a memoized value; calling - &compute-applicable-methods-UC;; or calling - &compute-applicable-methods-mop;. - (Refer to the description of &compute-discriminating-function; for - the details of this process.)</simpara> + &cam-cdf; <simpara>The &args-r; argument is permitted to contain more elements than the generic function accepts required arguments; in these cases the extra arguments will be ignored. An &err-sig; if &args-r; @@ -3285,14 +3278,8 @@ list of applicable methods based only on the supplied classes, this generic function returns an unspecified &pri-val; and false as its second value.</simpara> - <simpara>When a generic function is invoked, the discriminating - function must determine the ordered list of methods applicable to the - arguments. Depending on the generic function and the arguments, this - is done in one of three ways: using a memoized value; calling - &compute-applicable-methods-UC;; or calling - &compute-applicable-methods-mop;. (Refer to the description of - &compute-discriminating-function; for the details of this process.) - </simpara><simpara>The following consistency relationship between + &cam-cdf; + <simpara>The following consistency relationship between &compute-applicable-methods-UC; and &compute-applicable-methods-mop; must be maintained: for any given generic function and set of arguments, if &compute-applicable-methods-UC; returns a second value of true, Index: mop-ent.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/mop-ent.xml,v retrieving revision 2.19 retrieving revision 2.20 diff -u -d -r2.19 -r2.20 --- mop-ent.xml 10 Sep 2008 16:21:58 -0000 2.19 +++ mop-ent.xml 11 Sep 2008 15:31:47 -0000 2.20 @@ -185,3 +185,11 @@ <varlistentry><term>&slot-r;</term> <listitem><simpara>an &esdmo;.</simpara></listitem></varlistentry>'> <!ENTITY mo-prim '<primary>metaobject</primary>'> +<!ENTITY cam-cdf '<simpara>When a generic function is invoked, the + discriminating function must determine the ordered list of methods + applicable to the arguments. Depending on the generic function and + the arguments, this is done in one of three ways: using a memoized + value; calling &compute-applicable-methods-UC;; or calling + &compute-applicable-methods-mop;. + (Refer to the description of &compute-discriminating-function; for + the details of this process.)</simpara>'> ------------------------------ Message: 2 Date: Thu, 11 Sep 2008 15:36:59 +0000 From: Sam Steingold <sd...@us...> Subject: clisp/doc mop-ent.xml,2.20,2.21 mop.xml,2.87,2.88 To: cli...@li... Message-ID: <E1K...@ma...> Update of /cvsroot/clisp/clisp/doc In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv5527/doc Modified Files: mop-ent.xml mop.xml Log Message: (reinit-keep-value): new entity Index: mop.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/mop.xml,v retrieving revision 2.87 retrieving revision 2.88 diff -u -d -r2.87 -r2.88 --- mop.xml 11 Sep 2008 15:31:47 -0000 2.87 +++ mop.xml 11 Sep 2008 15:36:56 -0000 2.88 @@ -1280,8 +1280,8 @@ <para>Initialization of a &c-mo; must be done by calling &make-instance; and allowing it to call &initialize-instance;. Reinitialization of a -&c-mo; must be done by calling &reinitialize-instance;. Portable -programs must ¬-e; <itemizedlist> +&c-mo; must be done by calling &reinitialize-instance;. + Portable programs must ¬-e;<itemizedlist> <listitem><simpara>... call &initialize-instance; directly to initialize a &c-mo;;</simpara></listitem> <listitem><simpara>... call &shared-initialize; directly to @@ -1320,9 +1320,7 @@ Portable programs are free to define default initialization arguments for portable subclasses of the class &class;.</para> -<para>Unless there is a specific note to the contrary, then during -reinitialization, if an initialization argument is not supplied, the -previously stored value is left unchanged.</para> +&reinit-keep-value; <itemizedlist> <listitem><simpara>The &direct-default-initargs-k; argument is a list @@ -2810,8 +2808,8 @@ <para>Initialization of a &gfmo; must be done by calling &make-instance; and allowing it to call &initialize-instance;. Reinitialization of a -generic-function metaobject must be done by calling -&reinitialize-instance;. Portable programs must ¬-e;<itemizedlist> +&gfmo; must be done by calling &reinitialize-instance;. + Portable programs must ¬-e;<itemizedlist> <listitem><simpara>... call &initialize-instance; directly to initialize a &gfmo;;</simpara></listitem> <listitem><simpara>... call &shared-initialize; directly to @@ -2848,18 +2846,16 @@ Portable programs are free to define default initialization arguments for portable subclasses of the class &generic-function-t;.</para> -<para>Unless there is a specific note to the contrary, then during -reinitialization, if an initialization argument is not supplied, the -previously stored value is left unchanged.</para> +&reinit-keep-value; <itemizedlist> <listitem><simpara>The &argument-precedence-order-k; argument is a list of symbols.</simpara> <simpara>An &err-sig; if this argument appears but the &lambda-list-k; - argument does not appear. An &err-sig; if this value is not a &proper-list-glo; - or if this value is not a permutation of the symbols from the - required arguments part of the &lambda-list-k; initialization - argument.</simpara> + argument does not appear. An &err-sig; if this value is not a + &proper-list-glo; or if this value is not a permutation of the + symbols from the required arguments part of the &lambda-list-k; + initialization argument.</simpara> <simpara>When the generic function is being initialized or reinitialized, and this argument is not supplied, but the &lambda-list-k; argument is supplied, this value defaults to the Index: mop-ent.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/mop-ent.xml,v retrieving revision 2.20 retrieving revision 2.21 diff -u -d -r2.20 -r2.21 --- mop-ent.xml 11 Sep 2008 15:31:47 -0000 2.20 +++ mop-ent.xml 11 Sep 2008 15:36:56 -0000 2.21 @@ -193,3 +193,6 @@ &compute-applicable-methods-mop;. (Refer to the description of &compute-discriminating-function; for the details of this process.)</simpara>'> +<!ENTITY reinit-keep-value '<para>Unless there is a specific note to the + contrary, then during reinitialization, if an initialization argument + is not supplied, the previously stored value is left unchanged.</para>'> ------------------------------ Message: 3 Date: Thu, 11 Sep 2008 18:39:14 +0000 From: Sam Steingold <sd...@us...> Subject: clisp/doc mop.xml,2.88,2.89 To: cli...@li... Message-ID: <E1K...@ma...> Update of /cvsroot/clisp/clisp/doc In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv8593/doc Modified Files: mop.xml Log Message: fmt Index: mop.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/mop.xml,v retrieving revision 2.88 retrieving revision 2.89 diff -u -d -r2.88 -r2.89 --- mop.xml 11 Sep 2008 15:36:56 -0000 2.88 +++ mop.xml 11 Sep 2008 18:39:12 -0000 2.89 @@ -1332,8 +1332,8 @@ <listitem><simpara> The &direct-slots-k; argument is a list of &canonicalized-slot-spec;s.</simpara> <simpara>An &err-sig; if this value is not a &proper-list-glo; or if any - element of the list is not a &canonicalized-slot-spec;. - </simpara><para>After error checking, this value is converted to a + element of the list is not a &canonicalized-slot-spec;.</simpara> + <para>After error checking, this value is converted to a list of &dsdmo;s before it is associated with the &c-mo;. Conversion of each &canonicalized-slot-spec; to a &dsdmo; is a two-step process. First, the generic function &dsd-class; is called with the &c-mo; and ------------------------------ Message: 4 Date: Thu, 11 Sep 2008 18:42:32 +0000 From: Sam Steingold <sd...@us...> Subject: clisp/doc impext.xml,1.541,1.542 To: cli...@li... Message-ID: <E1K...@ma...> Update of /cvsroot/clisp/clisp/doc In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv9741 Modified Files: impext.xml Log Message: add index entries for foreign function and variable Index: impext.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/impext.xml,v retrieving revision 1.541 retrieving revision 1.542 diff -u -d -r1.541 -r1.542 --- impext.xml 15 Aug 2008 15:55:13 -0000 1.541 +++ impext.xml 11 Sep 2008 18:42:30 -0000 1.542 @@ -2657,7 +2657,9 @@ and to do many related things, like inspect and modify foreign memory, define a <quote>callback</quote> (i.e., make a lisp function available to the &c-lang; world), etc. -To use this facility, one writes a foreign function description into an +To use this facility, one writes a <firstterm>foreign function + <indexterm id="dffi-ff"><primary>foreign function</primary> + </indexterm></firstterm> description into an ordinary Lisp file, which is then compiled and loaded as usual; or just evaluates the appropriate form in the &repl;.</para> @@ -3542,8 +3544,9 @@ <section id="dffi-variables"><title>Foreign variables</title> -<para>Foreign variables are variables whose storage is allocated in the - foreign language module. +<para><firstterm>Foreign variables<indexterm id="dffi-fv"><primary>foreign + variable</primary></indexterm></firstterm> are variables whose + storage is allocated in the foreign language module. They can nevertheless be evaluated and modified through &setq;, just as normal variables can, except that the range of allowed values is limited according to the variable's foreign type.</para> @@ -3579,11 +3582,11 @@ <section id="dffi-functions"><title>Foreign functions</title> <para>Foreign functions are functions which are defined in the foreign language. - There are <firstterm>named foreign functions<indexterm id="dffi-ff-a"> + There are <firstterm>named foreign functions<indexterm id="dffi-ff-n"> <primary>foreign function</primary><secondary>named</secondary> </indexterm></firstterm> (imported via &def-call-out; or created via &def-call-in;) and - <firstterm>anonymous foreign functions<indexterm id="dffi-ff-n"> + <firstterm>anonymous foreign functions<indexterm id="dffi-ff-a"> <primary>foreign function</primary><secondary>anonymous</secondary> </indexterm></firstterm>; they arise through conversion of function pointers using &foreign-function;.</para> ------------------------------ Message: 5 Date: Thu, 11 Sep 2008 18:53:15 +0000 From: Sam Steingold <sd...@us...> Subject: clisp/doc mop-ent.xml,2.21,2.22 To: cli...@li... Message-ID: <E1K...@ma...> Update of /cvsroot/clisp/clisp/doc In directory sc8-pr-cvs4.sourceforge.net:/tmp/cvs-serv13743 Modified Files: mop-ent.xml Log Message: avoid indexterm IDs in links Index: mop-ent.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/mop-ent.xml,v retrieving revision 2.21 retrieving revision 2.22 diff -u -d -r2.21 -r2.22 --- mop-ent.xml 11 Sep 2008 15:36:56 -0000 2.21 +++ mop-ent.xml 11 Sep 2008 18:53:13 -0000 2.22 @@ -169,13 +169,13 @@ described in the &ansi-cl; section <ulink url="&clhs;/Body/sec_7-5-3.html" >7.5.3 <quote>Inheritance of Slots and Options</quote></ulink>.</simpara>'> <!ENTITY dsds-r '<replaceable>direct-slot-definitions</replaceable>'> -<!ENTITY c-mo '<link linkend="mop-class-mo">class metaobject</link>'> -<!ENTITY dsdmo '<link linkend="mop-dsd-mo">direct</link> &sdmo;'> -<!ENTITY esdmo '<link linkend="mop-esd-mo">effective</link> &sdmo;'> -<!ENTITY gfmo '<link linkend="mop-gen-fun-mo">generic function metaobject</link>'> -<!ENTITY m-mo '<link linkend="mop-method-mo">method metaobject</link>'> -<!ENTITY mcmo '<link linkend="mop-meth-comp-mo">method combination metaobject</link>'> -<!ENTITY sdmo '<link linkend="mop-slot-def-mo">slot definition metaobject</link>'> +<!ENTITY c-mo '<link linkend="mop-mo-classes">class metaobject</link>'> +<!ENTITY dsdmo '<link linkend="mop-mo-slot-defs">direct</link> &sdmo;'> +<!ENTITY esdmo '<link linkend="mop-mo-slot-defs">effective</link> &sdmo;'> +<!ENTITY gfmo '<link linkend="mop-mo-gen-funs">generic function metaobject</link>'> +<!ENTITY m-mo '<link linkend="mop-mo-methods">method metaobject</link>'> +<!ENTITY mcmo '<link linkend="mop-mo-meth-combs">method combination metaobject</link>'> +<!ENTITY sdmo '<link linkend="mop-mo-slot-defs">slot definition metaobject</link>'> <!ENTITY an-object '<listitem><simpara>an object</simpara></listitem>'> <!ENTITY a-cmo '<listitem><simpara>a &c-mo;.</simpara></listitem>'> <!ENTITY class-obj-slot-arg '<varlistentry><term>&class-r;</term> ------------------------------ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ------------------------------ _______________________________________________ clisp-cvs mailing list cli...@li... https://lists.sourceforge.net/lists/listinfo/clisp-cvs End of clisp-cvs Digest, Vol 29, Issue 9 **************************************** |