clisp-devel — closed list for developers and testers

Processing of Defining Macros

[Sam S. <sd...@gn...>]

http://clhs.lisp.se/Body/03_bcaa.htm:
>> It is not specified whether definitions made available in the
>> compilation environment are available in the evaluation environment, nor
>> is it specified whether they are available in subsequent compilation
>> units or subsequent invocations of the compiler.

Some macros form Figure 3-8 leak into the evaluation environment and
some do not.

Specifically, declaim, defvar, defconstant, defparameter do NOT.
defmacro, defclass, defstruct, defpackage DO.

This kinda makes sense - except for declaim which I think should be in
the second list.

On the second thought, I think this is not quite right.
Compiling a file should have an effect of loading its lib file.
E.g., in a single session, using an example from
http://clisp.org/impnotes/require.html,

(compile-file "foo")

will _not_ define variables defined in "foo", but

(compile-file "bar")

will load "foo.lib" (because of `(require "foo")` in "bar.lisp") and
thus will define the variables.

Bruno, can you elaborate on these design decisions?
(possibly by committing a patch to doc/impbody.xml)
Do you think declaim should be in the second list?

Thanks.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://iris.org.il
https://ffii.org http://thereligionofpeace.com http://islamexposedonline.com
Lisp: its not just for geniuses anymore.

clisp-cvs Digest, Vol 80, Issue 2

[<cli...@li...>]

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: document uncallable-generic-function
      (cli...@li...)


----------------------------------------------------------------------

Message: 1
Date: Tue, 01 Aug 2017 13:19:49 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: document uncallable-generic-function
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/99f95a6481c0
changeset: 15952:99f95a6481c0a73c5e5ba75ba6c815fde438fba2
user:      Sam Steingold <sd...@gn...>
date:      2017-08-01 09:19:16 -0400
description:
document uncallable-generic-function

diffstat:

 doc/mop.xml |  6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)



------------------------------

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

------------------------------

Subject: Digest Footer

_______________________________________________
clisp-cvs mailing list
cli...@li...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs


------------------------------

End of clisp-cvs Digest, Vol 80, Issue 2
****************************************

Re: CLISP CLOS style warnings

[Sam S. <sd...@gn...>]

> * Pascal Bourguignon <cwo@vasbezngvzntb.pbz> [2017-08-01 17:21:12 +0200]:
>
> It works perfectly, but on clisp, since DYNAMICALLY-MODIFIABLE doesn’t
> come from EXT.
> Where does it come from???

CLOS.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://jij.org
http://islamexposedonline.com https://ffii.org http://iris.org.il
A computer scientist is someone who fixes things that aren't broken.

Re: CLISP CLOS style warnings

[Pascal B. <pj...@in...>]

> On 1 Aug 2017, at 17:21, Pascal Bourguignon <pj...@in...> wrote:
> 
> It works perfectly, but on clisp, since DYNAMICALLY-MODIFIABLE doesn’t come from EXT.  
> Where does it come from???

Oh, and but on abcl, which also has a EXT package.  

I would advise remaining those short-named packages, unless they implement a CDR-specified API.
“ORG.CLISP.EXT” sounds a good unique name, or at least “CLISP-EXT”… 


> [pjb@despina :0.0 ~]$ clall '(compile-file "/tmp/d.lisp")'
> 
> 
> 
> Armed Bear Common Lisp:
> ========================================================================
> Implementation: Armed Bear Common Lisp 1.4.0
>     on Mac OS X 10.12.6
>     on X86_64 NIL (despina.home)
> 
> Reading of: "(compile-file \"/tmp/d.lisp\")"
> signaled no error
> 
> Evaluation of: (COMPILE-FILE "/tmp/d.lisp")
> signaled the following error:
>   #<READER-ERROR {2D87B142}>
>   The symbol "DYNAMICALLY-MODIFIABLE" was not found in package EXT.
> wrote nothing on *ERROR-OUTPUT*
> wrote nothing on *TRACE-OUTPUT*
> wrote the following *STANDARD-OUTPUT* (lines excluded):
> ------------------------------------------------------------------------
> ; Compiling /private/tmp/d.lisp ...
> ; (DEFPACKAGE "EXT" ...)
> ------------------------------------------------------------------------
> returned no value
> 

-- 
__Pascal J. Bourguignon__

Re: CLISP CLOS style warnings

[Pascal B. <pj...@in...>]

> On 1 Aug 2017, at 17:08, Sam Steingold <sd...@gn...> wrote:
> 
>> * Faré <snuerr@tznvy.pbz> [2017-08-01 10:07:33 -0400]:
>> 
>>> To mark a generic function as user-extendable, one can now use a
>>> declaration:
>>> 
>>> --8<---------------cut here---------------start------------->8---
>>> (defgeneric perform (...)
>>>  (declare #+clisp (dynamically-modifiable))
>>>  ...)
>>> (defgeneric operation-done-p (...)
>>>  (declare #+clisp (dynamically-modifiable))
>>>  ...)
>>> --8<---------------cut here---------------end--------------->8---
>>> 
>>> The declaration is now in `hg tip` (but has not been released yet).
>>> 
>> Will that declaration cause a warning or error on older versions of
>> clisp? If yes, what read-time conditional more precise than #+clisp
>> can I use to only enable on recent enough versions of clisp?
> 
> My first reaction was
> 
> --8<---------------cut here---------------start------------->8---
> (declaim (declaration dynamically-modifiable))
> --8<---------------cut here---------------end--------------->8---
> 
> but for some reason it does not work with defgeneric.
> Sorry.



1- when naming an implementation-specific declaration, we need to know what package it comes from!
   (Now, an implementation could use only the symbol-name of the declaration so it would accept with the same semantics any package, but this would be a problem if the program uses the same symbol name in a different package to mean something else, so I would advise implementations to avoid using symbol-names for declarations, and instead to specify a specific package).

2- indeed the correct way to use implementation specific declarations is to declaim them.

    #-clisp (defpackage “EXT” #| be careful with those 💣🔪🔫 smart quotes! |#
               (:use)
               (:export “DYNAMICALLY-MODIFIABLE”))

    (declaim (declaration ext:dynamically-modifiable))

    (defgeneric foo (bar)
       (declare ext:dynamically-modifiable)))


It works perfectly, but on clisp, since DYNAMICALLY-MODIFIABLE doesn’t come from EXT.  
Where does it come from???



[pjb@despina :0.0 ~]$ clall '(compile-file "/tmp/d.lisp")'



Armed Bear Common Lisp:
========================================================================
Implementation: Armed Bear Common Lisp 1.4.0
    on Mac OS X 10.12.6
    on X86_64 NIL (despina.home)

Reading of: "(compile-file \"/tmp/d.lisp\")"
signaled no error

Evaluation of: (COMPILE-FILE "/tmp/d.lisp")
signaled the following error:
  #<READER-ERROR {2D87B142}>
  The symbol "DYNAMICALLY-MODIFIABLE" was not found in package EXT.
wrote nothing on *ERROR-OUTPUT*
wrote nothing on *TRACE-OUTPUT*
wrote the following *STANDARD-OUTPUT* (lines excluded):
------------------------------------------------------------------------
; Compiling /private/tmp/d.lisp ...
; (DEFPACKAGE "EXT" ...)
------------------------------------------------------------------------
returned no value


Clozure Common Lisp:
--> #P"/private/tmp/d.dx64fsl", NIL, NIL


CLISP:
========================================================================
Implementation: CLISP 2.49 (2010-07-07) (built 3704439585) (memory 3704439775)
    on 
/usr/bin/clang -arch x86_64 -pipe -Wl,-no_pie -arch x86_64 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -O -DUNIX_BINARY_DISTRIB -DENABLE_UNICODE -DDYNAMIC_MODULES -I. -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64  -lintl -Wl,-framework -Wl,CoreFoundation -lreadline -lncurses  -liconv -L/opt/local/lib -lsigsegv  libgnu_cl.a -L/opt/local/lib
SAFETY=0 HEAPCODES STANDARD_HEAPCODES WIDE_HARD GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libsigsegv 2.11
libiconv 1.15
libreadline 7.0 GNU C 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)
    on X86_64 X86_64 (despina.home [192.168.7.10])

Reading of: "(compile-file \"/tmp/d.lisp\")"
signaled no error

Evaluation of: (COMPILE-FILE "/tmp/d.lisp")
signaled the following error:
  #<SYSTEM::SIMPLE-PACKAGE-ERROR #x000000020023FE91>
  
READ from #<CLOSED INPUT BUFFERED FILE-STREAM CHARACTER #P"/tmp/d.lisp" @5>: #<PACKAGE
  EXT> has no external symbol with name "DYNAMICALLY-MODIFIABLE"

wrote the following *ERROR-OUTPUT* (lines excluded):
------------------------------------------------------------------------
0 errors, 0 warnings
------------------------------------------------------------------------
wrote nothing on *TRACE-OUTPUT*
wrote the following *STANDARD-OUTPUT* (lines excluded):
------------------------------------------------------------------------
;; Compiling file /tmp/d.lisp ...
------------------------------------------------------------------------
returned no value


ECL:
========================================================================
Implementation: ECL 16.1.2
    on Darwin 16.7.0
    on x86_64 NIL (despina.home)

Reading of: "(compile-file \"/tmp/d.lisp\")"
signaled no error

Evaluation of: (COMPILE-FILE "/tmp/d.lisp")
signaled the following error:
  #<a C:COMPILER-NOTE>
  Note:
  Invoking external command:
  gcc -I. -I/usr/local/include/ -g -O2 -fPIC -fno-common -D_THREAD_SAFE -Ddarwin -O2 -c /private/tmp/d.c -o /private/tmp/d.o 
wrote nothing on *ERROR-OUTPUT*
wrote nothing on *TRACE-OUTPUT*
wrote the following *STANDARD-OUTPUT* (lines excluded):
------------------------------------------------------------------------
;;; Loading #P"/usr/local/lib/ecl-16.1.2/cmp.fas"
;;;
;;; Compiling /tmp/d.lisp.
;;; OPTIMIZE levels: Safety=2, Space=0, Speed=3, Debug=0
;;;
;;; Compiling (DEFGENERIC FOO ...).
;;; End of Pass 1.
------------------------------------------------------------------------
returned no value


SBCL:; compiling file "/private/tmp/d.lisp" (written 01 AUG 2017 05:19:58 PM):
; compiling (DEFPACKAGE "EXT" ...)
; compiling (DECLAIM (DECLARATION EXT:DYNAMICALLY-MODIFIABLE))
; compiling (DEFGENERIC FOO ...)

; /tmp/d.fasl written
; compilation finished in 0:00:00.003
--> #P"/private/tmp/d.fasl", T, T

========================================================================

[pjb@despina :0.0 ~]$ 


-- 
__Pascal J. Bourguignon__

Re: CLISP CLOS style warnings

[Sam S. <sd...@gn...>]

> * Faré <snuerr@tznvy.pbz> [2017-08-01 10:07:33 -0400]:
>
>> To mark a generic function as user-extendable, one can now use a
>> declaration:
>>
>> --8<---------------cut here---------------start------------->8---
>> (defgeneric perform (...)
>>   (declare #+clisp (dynamically-modifiable))
>>   ...)
>> (defgeneric operation-done-p (...)
>>   (declare #+clisp (dynamically-modifiable))
>>   ...)
>> --8<---------------cut here---------------end--------------->8---
>>
>> The declaration is now in `hg tip` (but has not been released yet).
>>
> Will that declaration cause a warning or error on older versions of
> clisp? If yes, what read-time conditional more precise than #+clisp
> can I use to only enable on recent enough versions of clisp?

My first reaction was

--8<---------------cut here---------------start------------->8---
(declaim (declaration dynamically-modifiable))
--8<---------------cut here---------------end--------------->8---

but for some reason it does not work with defgeneric.
Sorry.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://www.memritv.org
https://jihadwatch.org http://camera.org http://jij.org
Only a fool has no doubts.

CLISP CLOS style warnings

[Sam S. <sd...@gn...>]

Hi,
I am writing in regards to the CLISP CLOS style warnings reported in
https://sourceforge.net/p/clisp/mailman/message/35946823/
Specifically:

--8<---------------cut here---------------start------------->8---
WARNING: Adding method
         #<STANDARD-METHOD (#<STANDARD-CLASS TEST-OP> (EQL #<SYSTEM 
         "alexandria">))> to an already called generic function
         #<STANDARD-GENERIC-FUNCTION OPERATION-DONE-P>
WARNING: Adding method
         #<STANDARD-METHOD (#<STANDARD-CLASS TEST-OP> (EQL #<SYSTEM 
         "alexandria">))> to an already called generic function
         #<STANDARD-GENERIC-FUNCTION PERFORM>
WARNING: Adding method
         #<STANDARD-METHOD (#<STANDARD-CLASS TEST-OP> (EQL #<SYSTEM 
         "babel">))> to an already called generic function
         #<STANDARD-GENERIC-FUNCTION OPERATION-DONE-P>
--8<---------------cut here---------------end--------------->8---

The rationale for these warnings is explained in
http://clisp.org/impnotes/mop-clisp.html#mop-clisp-gf-already-called-warning

However, when the normal use case for a generic function is being
extended by its users (e.g., `print-object`), this warning is
inappropriate.
ASDF user macros, apparently, expand to method definitions, thus they
are similar to `print-object`.
To mark a generic function as user-extendable, one can now use a
declaration:

--8<---------------cut here---------------start------------->8---
(defgeneric perform (...)
  (declare #+clisp (dynamically-modifiable))
  ...)
(defgeneric operation-done-p (...)
  (declare #+clisp (dynamically-modifiable))
  ...)
--8<---------------cut here---------------end--------------->8---

The declaration is now in `hg tip` (but has not been released yet).

Thank you!

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://honestreporting.com
http://jij.org https://jihadwatch.org http://mideasttruth.com
Me, sarcastic?! Yeah, right...

clisp-cvs Digest, Vol 80, Issue 1

[<cli...@li...>]

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: GNU_DTD: use DTDVER
      (cli...@li...)
   2. clisp: add clisp-set-compile-command
      (cli...@li...)
   3. clisp: add symbols-cleanup
      (cli...@li...)
   4. clisp: (with-counting-mop-warnings): extract from a test and
      spl... (cli...@li...)
   5. clisp: Implement RFE#52: add (declare
      (dynamically-modifiable)). (cli...@li...)
   6. clisp: update (C) year (cli...@li...)


----------------------------------------------------------------------

Message: 1
Date: Mon, 31 Jul 2017 21:44:38 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: GNU_DTD: use DTDVER
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/066239c4afed
changeset: 15946:066239c4afed71d9e887030356ad83a6690916db
user:      Sam Steingold <sd...@gn...>
date:      2017-07-31 14:15:15 -0400
description:
GNU_DTD: use DTDVER

diffstat:

 doc/Makefile |  2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)



------------------------------

Message: 2
Date: Mon, 31 Jul 2017 21:44:39 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: add clisp-set-compile-command
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/b7ed89871d6e
changeset: 15947:b7ed89871d6e55680cdd439153535e16e3a3376f
user:      Sam Steingold <sd...@gn...>
date:      2017-07-31 15:58:46 -0400
description:
add clisp-set-compile-command

diffstat:

 emacs/misc.el |  18 ++++++++++++++++++
 1 files changed, 18 insertions(+), 0 deletions(-)



------------------------------

Message: 3
Date: Mon, 31 Jul 2017 21:44:40 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: add symbols-cleanup
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/d45b9083a8a5
changeset: 15948:d45b9083a8a5622916b190ae46a7091c7c26e8e4
user:      Sam Steingold <sd...@gn...>
date:      2017-07-31 16:07:35 -0400
description:
add symbols-cleanup

* tests/tests.lisp (symbols-cleanup): add
* tests/conditions.tst, tests/eval20.tst, tests/ext-clisp.tst, tests/format.tst:
* tests/hashlong.tst, tests/iofkts.tst, tests/macro8.tst, tests/map.tst, tests/mop.tst, tests/mt.tst:
* tests/number2.tst, tests/path.tst, tests/restarts.tst, tests/setf.tst, tests/steele7.tst:
* tests/streams.tst, tests/streamslong.tst, tests/symbol10.tst, tests.lisp, tests/type.tst:
* tests/unportable.tst, tests/weakhash.tst, tests/weakptr.tst: use it

diffstat:

 tests/ChangeLog       |    9 +
 tests/conditions.tst  |   14 +-
 tests/eval20.tst      |   13 +-
 tests/ext-clisp.tst   |    6 +-
 tests/format.tst      |   15 +-
 tests/hashlong.tst    |   11 +-
 tests/iofkts.tst      |   23 +-
 tests/macro8.tst      |   82 +-----
 tests/map.tst         |   11 +-
 tests/mop.tst         |  603 ++++++++++++++++++++++---------------------------
 tests/mt.tst          |    8 +-
 tests/number2.tst     |   10 +-
 tests/path.tst        |   21 +-
 tests/restarts.tst    |   11 +-
 tests/setf.tst        |    7 +-
 tests/steele7.tst     |    8 +-
 tests/streams.tst     |   36 +--
 tests/streamslong.tst |    6 +-
 tests/symbol10.tst    |   14 +-
 tests/tests.lisp      |    4 +-
 tests/type.tst        |   25 +-
 tests/unportable.tst  |    6 +-
 tests/weakhash.tst    |   12 +-
 tests/weakptr.tst     |    8 +-
 24 files changed, 350 insertions(+), 613 deletions(-)



------------------------------

Message: 4
Date: Mon, 31 Jul 2017 21:44:41 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: (with-counting-mop-warnings): extract from a test and
	spl...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/dd886582bd26
changeset: 15949:dd886582bd26a34bfb6fb668c2b19fc33ee8f41d
user:      Sam Steingold <sd...@gn...>
date:      2017-07-31 16:13:23 -0400
description:
(with-counting-mop-warnings): extract from a test and split the test in two

diffstat:

 tests/ChangeLog |   5 ++++
 tests/mop.tst   |  62 ++++++++++++++++++++++++++++++++++----------------------
 2 files changed, 43 insertions(+), 24 deletions(-)



------------------------------

Message: 5
Date: Mon, 31 Jul 2017 21:44:43 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: Implement RFE#52: add (declare
	(dynamically-modifiable)).
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/6fca28881cb1
changeset: 15950:6fca28881cb16997442b573da0fcbde4517c9a78
user:      Sam Steingold <sd...@gn...>
date:      2017-07-31 17:44:23 -0400
description:
Implement RFE#52: add (declare (dynamically-modifiable)).

* src/clos-genfun1.lisp (generic-function): Add slot
$DYNAMICALLY-MODIFIABLE.
* src/clos-genfun2b.lisp (+gf-declarations+): New constant.
(check-gf-declspecs): Use it.
(std-add-method): Use GF-DYNAMICALLY-MODIFIABLE instead of
*DYNAMICALLY-MODIFIABLE-GENERIC-FUNCTION-NAMES* to disable warnings.
(gf-set-dynamically-modifiable): New function.
(initialize-instance-<generic-function>)
(reinitialize-instance-<generic-function>): Use it.
(*dynamically-modifiable-generic-function-names*): Remove.
(need-gf-already-called-warning-p): Use GF-DYNAMICALLY-MODIFIABLE
instead of *DYNAMICALLY-MODIFIABLE-GENERIC-FUNCTION-NAMES*.
* src/clos-package.lisp, src/init.lisp: Export DYNAMICALLY-MODIFIABLE.
* src/compiler.lisp (*declaration-types*): Add DYNAMICALLY-MODIFIABLE.
(process-declarations): Handle DYNAMICALLY-MODIFIABLE.
* src/clos-genfun4.lisp (no-applicable-method, no-primary-method)
(no-next-method, find-method, add-method, remove-method)
(compute-discriminating-function, compute-applicable-methods)
(compute-applicable-methods-using-classes)
(compute-effective-method): Declare dynamically-modifiable.
* src/clos-genfun5.lisp (ensure-generic-function-using-class): Ditto.
* src/clos-method3.lisp (method-qualifiers, method-generic-function)
((setf method-generic-function), function-keywords): Ditto.
* src/clos-class5.lisp (shared-initialize, reinitialize-instance)
(initialize-instance, allocate-instance, make-instance)
(dynamically-modifiable, update-instance-for-different-class)
(make-instances-obsolete, update-instance-for-redefined-class): Ditto.
* src/clos-class6.lisp (class-name, (setf class-name))
(class-direct-subclasses, class-direct-superclasses)
(compute-direct-slot-definition-initargs)
(compute-class-precedence-list)
(compute-effective-slot-definition-initargs)
(compute-effective-slot-definition, compute-slots)
(compute-default-initargs, ensure-class-using-class)
(validate-superclass, add-direct-subclass, remove-direct-subclass)
(reader-method-class, writer-method-class): Ditto.
* src/clos-dependent.lisp (add-dependent, remove-dependent)
(map-dependents): Ditto.
* src/clos-print.lisp (print-object): Ditto.
* src/clos-slotdef3.lisp (direct-slot-definition-class)
(effective-slot-definition-class): Ditto.
* src/clos-slots2.lisp (slot-missing, slot-unbound)
(slot-value-using-class, (setf slot-value-using-class))
(slot-boundp-using-class, slot-makunbound-using-class): Ditto.
* src/clos-specializer3.lisp (specializer-direct-generic-functions)
(add-direct-method, remove-direct-method)
(specializer-direct-methods): Ditto.
* src/describe.lisp (describe-object): Ditto.
* src/documentation.lisp (documentation, (setf documentation)): Ditto.
* src/gray.lisp (close, open-stream-p, stream-element-type)
((setf stream-element-type), stream-position)
(stream-read-sequence, stream-write-sequence, stream-read-char)
(stream-unread-char, stream-read-char-no-hang, stream-peek-char)
(stream-listen, stream-read-char-will-hang-p)
(stream-read-char-sequence, stream-read-line, stream-clear-input)
(stream-write-char, stream-line-column, stream-start-line-p)
(stream-write-char-sequence, stream-write-string, stream-terpri)
(stream-fresh-line, stream-finish-output, stream-force-output)
(stream-clear-output, stream-advance-to-column, stream-read-byte)
(stream-read-byte-lookahead, stream-read-byte-will-hang-p)
(stream-read-byte-no-hang, stream-read-byte-sequence)
(stream-write-byte, stream-write-byte-sequence): Ditto.
* src/loadform.lisp (make-load-form): Ditto.

diffstat:

 doc/Symbol-Table.text      |    2 +
 doc/mop.xml                |   10 +
 src/ChangeLog              |   67 ++++++++++
 src/NEWS                   |    4 +
 src/clos-class5.lisp       |   19 ++-
 src/clos-class6.lisp       |   16 ++
 src/clos-dependent.lisp    |    3 +
 src/clos-genfun1.lisp      |    5 +-
 src/clos-genfun2b.lisp     |   65 ++-------
 src/clos-genfun4.lisp      |   10 +
 src/clos-genfun5.lisp      |    3 +-
 src/clos-method3.lisp      |    4 +
 src/clos-package.lisp      |    2 +-
 src/clos-print.lisp        |    1 +
 src/clos-slotdef3.lisp     |    2 +
 src/clos-slots2.lisp       |   14 +-
 src/clos-specializer3.lisp |    4 +
 src/compiler.lisp          |    4 +
 src/describe.lisp          |    1 +
 src/documentation.lisp     |    2 +
 src/gray.lisp              |  287 ++++++++++++++++++++------------------------
 src/init.lisp              |    2 +-
 src/loadform.lisp          |    1 +
 tests/ChangeLog            |    5 +
 tests/mop.tst              |   70 ++++++++--
 25 files changed, 368 insertions(+), 235 deletions(-)



------------------------------

Message: 6
Date: Mon, 31 Jul 2017 22:26:39 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: update (C) year
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/c1922a23f9b7
changeset: 15951:c1922a23f9b7fbc08bd1cabb658cb8847713351a
user:      Sam Steingold <sd...@gn...>
date:      2017-07-31 18:26:09 -0400
description:
update (C) year

diffstat:

 src/ari80386.d             |  3 +--
 src/built.d                |  2 +-
 src/charstrg.d             |  2 +-
 src/clos-class6.lisp       |  2 +-
 src/clos-dependent.lisp    |  1 +
 src/clos-genfun1.lisp      |  2 +-
 src/clos-genfun2b.lisp     |  2 +-
 src/clos-genfun4.lisp      |  2 +-
 src/clos-genfun5.lisp      |  1 +
 src/clos-method3.lisp      |  2 +-
 src/clos-package.lisp      |  2 +-
 src/clos-print.lisp        |  2 +-
 src/clos-slotdef3.lisp     |  1 +
 src/clos-slots2.lisp       |  2 +-
 src/clos-specializer3.lisp |  1 +
 src/compiler.lisp          |  2 +-
 src/constsym.d             |  2 +-
 src/debug.d                |  5 ++---
 src/documentation.lisp     |  2 +-
 src/encoding.d             |  2 +-
 src/eval.d                 |  4 ++--
 src/foreign.d              |  4 ++--
 src/foreign1.lisp          |  2 +-
 src/io.d                   |  3 +--
 src/lisparit.d             |  4 ++--
 src/lispbibl.d             |  2 +-
 src/list.d                 |  3 +--
 src/loadform.lisp          |  2 +-
 src/misc.d                 |  4 ++--
 src/pathname.d             |  2 +-
 src/predtype.d             |  4 ++--
 src/socket.d               |  4 ++--
 src/spvw.d                 |  4 ++--
 src/stream.d               |  2 +-
 src/subr.d                 |  2 +-
 src/unix.d                 |  4 ++--
 src/unixaux.d              |  2 +-
 src/win32.d                |  4 ++--
 src/zthread.d              |  2 +-
 39 files changed, 49 insertions(+), 49 deletions(-)



------------------------------

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

------------------------------

Subject: Digest Footer

_______________________________________________
clisp-cvs mailing list
cli...@li...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs


------------------------------

End of clisp-cvs Digest, Vol 80, Issue 1
****************************************

Re: uncallable-generic-function

[Bruno H. <br...@cl...>]

Hi Sam,

> DIUC that the `uncallable-generic-function' behavior in mop.tst is a bug?

I would view it as a limitation. It would be good to mention it in the impnotes
http://clisp.org/impnotes/mop-clisp.html

Proposed wording: "It is not possible to create a class with metaclass
STANDARD-CLASS when specifying a superclass with metaclass
FUNCALLABLE-STANDARD-CLASS, even though VALIDATE-SUPERCLASS returns T for this
situation."

The rationale for this limitation is that in clisp, STANDARD-CLASS objects have
a certain memory layout, and FUNCALLABLE-STANDARD-CLASS objects have another
memory layout, and the contortions of making them compatible are not worth it
- given that the use-case is obscure and Allegro CL does/did not support it
either.

Bruno

uncallable-generic-function

[Sam S. <sd...@gn...>]

Bruno,
DIUC that the `uncallable-generic-function' behavior in mop.tst is a bug?
Thanks.
-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://www.dhimmitude.org
http://islamexposedonline.com http://honestreporting.com https://jihadwatch.org
XFM: Exit file manager? [Continue] [Cancel] [Abort]

Re: How to handle these warnings?

[Bruno H. <br...@cl...>]

Hi Sam,

> Why is class-direct-subclasses in
> *dynamically-modifiable-generic-function-names* but
> class-direct-superclasses not?

When you look in the MOP (clisp/doc/mop-spec.pdf), pages 75..78,
you see on page 78 an indication that the default method on
class-direct-subclasses can be overridden. (Although I cannot
imagine what such a method could do differently, assuming
that the user has added overriding methods to
add-direct-subclass and remove-direct-subclass. But it's in
the spec...)

No such indication is present for class-direct-superclasses.

Bruno

Re: How to handle these warnings?

[Sam S. <sd...@gn...>]

Bruno
Why is class-direct-subclasses in
*dynamically-modifiable-generic-function-names* but
class-direct-superclasses not?
Thanks.
-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://www.dhimmitude.org
http://memri.org http://thereligionofpeace.com https://jihadwatch.org
"A pint of sweat will save a gallon of blood."          --George S. Patton

Re: How to handle these warnings?

[Bruno H. <br...@cl...>]

Daniel wrote:
> Note that this may lead to situations where loading the exact same code
> will lead to different results, depending on previous definitions: a GF
> without any declare expression would be dynamically modifiable depending on
> whether there was a previous definition.

Well explained. 100% agree.

Sam wrote:
> This is already the case.
> If you have a file with
> 
> (defun f (x) (lambda () (print x)))
> (funcall (f 10))
> 
> then loading it will print 10.
> If, however, you evaluate (defparameter x 100) before loading it, it
> will print 100.

This is precisely why DEFPARAMETER and DEFVAR are considered a problem
in the CL language. The usual workaround is to separate the sets of
symbols into two classes: those to which DEFPARAMETER and DEFVAR may
be applied (those whose print name starts and ends with a * or + character)
and those which, by convention (!), will not be subject to DEFPARAMETER
or DEFVAR. Remember that this is merely a workaround to an ill design.

It is not necessary to copy this ill design pattern to new areas, like
generic functions. So, please, forget about DECLAIM here.

> Then it will not be possible to change the dynamically-modifiable status
> of a GF without redefining it.

This is not a problem. The usual way of developing in any programming
language, nowadays, is
  - to store the definitions in text files,
  - when making a change: change the file then LOAD it.
The approach of InterLisp (change programs on-the-fly, in memory) became
obsolete when the edit-file--reload--retry cycle became efficient enough.

When you use closures e.g.
  (let ((balance 0))
    (defun add (x) (incf balance x)))
you cannot change the value of BALANCE, nor redefine ADD, without reloading
the file. Yet this is considered completely normal programming style.

Bruno

Re: How to handle these warnings?

[Sam S. <sd...@gn...>]

Hi Daniel,

> * Daniel Jour <qnavry.bregjvt@tznvy.pbz> [2017-07-19 22:57:40 +0000]:
>
> Note that this may lead to situations where loading the exact same code
> will lead to different results, depending on previous definitions:

This is already the case.
If you have a file with

(defun f (x) (lambda () (print x)))
(funcall (f 10))

then loading it will print 10.
If, however, you evaluate (defparameter x 100) before loading it, it
will print 100.

Note that the standard does NOT provide a way to revert the effects of
defvar or defparameter.

Note also the this whole conversation is related to warnings only, not
the actual effect of the code.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net
http://www.memritv.org http://honestreporting.com http://camera.org
Two wrongs don't make a right, but three rights make a left.

Re: How to handle these warnings?

[Daniel J. <dan...@gm...>]

Hi Sam,

Sam wrote:
> Not necessarily.
> When _redefining_ GF we can look
> at the old definition and carry the
> slot over to the new one, unless
> we also see
>
> (declare ((not dynamically-modifiable)))
>
> in the new definition.

Note that this may lead to situations where loading the exact same code
will lead to different results, depending on previous definitions: a GF
without any declare expression would be dynamically modifiable depending on
whether there was a previous definition. As such the specification whether
a GF is dynamically modifiable wouldn't be declarative ("declare" ??).

Best, Daniel

Re: How to handle these warnings?

[Sam S. <sd...@gn...>]

Bruno,

> * Bruno Haible <oe...@py...t> [2017-07-19 23:00:22 +0200]:
>
>> (declaim (dynamically-modifiable gf1 gf2 gf3))
>
> I don't think this will work right: If you store this information only in
> the GF, then after redefining the GF without (dynamically-modifiable), the
> effect will be lost - which is counter-intuitive. Whereas if you store

Not necessarily.
When _redefining_ GF we can look at the old definition and carry the
slot over to the new one, unless we also see

(declare ((not dynamically-modifiable)))

in the new definition.

> this information on the property list of the symbol or in the undocumented
> variable clos::*dynamically-modifiable-generic-function-names*, the
> semantics will be too complex, i.e. too hard to understand.

Then it will not be possible to change the dynamically-modifiable status
of a GF without redefining it.
I am not sure this is a good idea.
BTW, we might want to also add

(declaim ((not dynamically-modifiable) gf1 gf2 gf3))

>   - the only use of clos::*dynamically-modifiable-generic-function-names*
>     will be for clos-genfun2b.lisp line 856.

or no! please! we can do better:

(letf (((gf-dynamically-modifiable gf) t))
  (remove-method gf old-method))

Thanks.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://no2bds.org
http://thereligionofpeace.com http://think-israel.org http://memri.org
When C++ is your hammer, everything looks like a thumb.

Re: How to handle these warnings?

[Bruno H. <br...@cl...>]

[from clisp-list to clisp-devel]
Sam,

I mostly agree.

> >   1) What should the syntax for this declaration look like?
> >      (Extension of DEFGENERIC? Separate declaration macro? ...)
> 
> (defgeneric gf (...)
>   (declare (dynamically-modifiable))
>   ...)

Agree. The user will have to write

  (defgeneric gf (...)
    (declare #+clisp (dynamically-modifiable))
    ...)

because other implementations would choke on this declaration specifier ([1]
says "other declaration specifiers are not permitted").

> >   2) Where should the information be stored?
> >      (In the generic-function object? On the symbol's property list? ...)
> 
> generic-function object slot $dynamically-modifiable.

Yep. Looks good. If someone redefines the GF, with a DEFGENERIC form
without (dynamically-modifiable), it will warn about dynamic modifications.

> (declaim (dynamically-modifiable gf1 gf2 gf3))

I don't think this will work right: If you store this information only in
the GF, then after redefining the GF without (dynamically-modifiable), the
effect will be lost - which is counter-intuitive. Whereas if you store
this information on the property list of the symbol or in the undocumented
variable clos::*dynamically-modifiable-generic-function-names*, the
semantics will be too complex, i.e. too hard to understand.

In summary, I would vote for
  - the DEFGENERIC syntax,
  - store the info in a slot in the GF,
  - don't offer DECLAIM support for it,
  - the only use of clos::*dynamically-modifiable-generic-function-names*
    will be for clos-genfun2b.lisp line 856.

Bruno

[1] http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/mac_defgeneric.html

clisp-cvs Digest, Vol 79, Issue 2

[<cli...@li...>]

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: amend last patch: add non-GRAY stream symbols too
      (cli...@li...)


----------------------------------------------------------------------

Message: 1
Date: Tue, 18 Jul 2017 20:44:41 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: amend last patch: add non-GRAY stream symbols too
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/9c43d428b7ff
changeset: 15945:9c43d428b7ff9897cc2c4e97d926a5039f79aba7
user:      Sam Steingold <sd...@gn...>
date:      2017-07-18 16:44:09 -0400
description:
amend last patch: add non-GRAY stream symbols too

diffstat:

 src/gray.lisp |  7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)



------------------------------

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

------------------------------

Subject: Digest Footer

_______________________________________________
clisp-cvs mailing list
cli...@li...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs


------------------------------

End of clisp-cvs Digest, Vol 79, Issue 2
****************************************

clisp-cvs Digest, Vol 79, Issue 1

[<cli...@li...>]

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: Do not raise the CLOS:GF-ALREADY-CALLED-WARNING on
      Gray s... (cli...@li...)


----------------------------------------------------------------------

Message: 1
Date: Mon, 17 Jul 2017 16:05:21 +0000
From: cli...@li...
To: cli...@li...
Subject: clisp: Do not raise the CLOS:GF-ALREADY-CALLED-WARNING on
	Gray s...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/6e24ba20ba4d
changeset: 15944:6e24ba20ba4d10f08e3e3b97f19cd2a474453685
user:      Sam Steingold <sd...@gn...>
date:      2017-07-17 12:05:09 -0400
description:
Do not raise the CLOS:GF-ALREADY-CALLED-WARNING on Gray streams.

* src/gray.lisp (clos::*dynamically-modifiable-generic-function-names*):
Add Gray generic functions to avoid the
CLOS:GF-ALREADY-CALLED-WARNING as per the spec.
Reported by Jean Louis <bu...@gn...pport>.

diffstat:

 src/ChangeLog   |   7 ++++
 src/NEWS        |   1 +
 src/gray.lisp   |  81 ++++++++++++++++++++++++++++++--------------------------
 tests/ChangeLog |   4 ++
 tests/mop.tst   |   5 +++
 5 files changed, 61 insertions(+), 37 deletions(-)



------------------------------

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

------------------------------

Subject: Digest Footer

_______________________________________________
clisp-cvs mailing list
cli...@li...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs


------------------------------

End of clisp-cvs Digest, Vol 79, Issue 1
****************************************

Re: anyone familiar with quicklisp and ASDF?

[Anton V. <avo...@ya...>]

12.07.2017, 22:21, "Pascal Bourguignon" <pj...@in...>:
>> On 12 Jul 2017, at 19:10, Bruno Haible <br...@cl...> wrote:
>>
>> There's a question here: "Updating to ASDF 3.x in CLISP"
>> https://stackoverflow.com/questions/45043190/updating-to-asdf-3-x-in-clisp
>
> 0down vote
>
> asdf itself is self-updatable. You only have to load the latest version.
>
> http://paste.lisp.org/display/350703
>
> So basically, you download an asdf 3 somewhere, say ~/rc/asdf.lisp and in your ~/.clisprc.lisp you put:
>
> (load #P"~/quicklisp/setup.lisp") ; will load asdf 2.26
> (load (compile-file #P"~/rc/asdf.lisp")) ; will load asdf 3 over asdf 2.26.

Better other way around - first load new ASDF then quicklisp/setup.lisp - no ASDF
update happens in this case, because quicklsp first checks whether satisfying ASFD version is present
and if so it does not (requre 'asdf).

Also compiling every time seems like an overhead.

Re: anyone familiar with quicklisp and ASDF?

[Pascal B. <pj...@in...>]

> On 12 Jul 2017, at 19:10, Bruno Haible <br...@cl...> wrote:
> 
> There's a question here: "Updating to ASDF 3.x in CLISP"
> https://stackoverflow.com/questions/45043190/updating-to-asdf-3-x-in-clisp




0
down vote
 <>	
asdf itself is self-updatable. You only have to load the latest version.

http://paste.lisp.org/display/350703 <http://paste.lisp.org/display/350703>
So basically, you download an asdf 3 somewhere, say ~/rc/asdf.lisp and in your ~/.clisprc.lisp you put:

(load #P"~/quicklisp/setup.lisp")        ; will load asdf 2.26
(load (compile-file #P"~/rc/asdf.lisp")) ; will load asdf 3 over asdf 2.26.



-- 
__Pascal J. Bourguignon__

anyone familiar with quicklisp and ASDF?

[Bruno H. <br...@cl...>]

There's a question here: "Updating to ASDF 3.x in CLISP"
https://stackoverflow.com/questions/45043190/updating-to-asdf-3-x-in-clisp

Re: GSoC 2017 eval

[Sam S. <sd...@gn...>]

> * Compro Prasad <pbzcebcenfnq@tznvy.pbz> [2017-07-01 11:55:03 +0500]:
>
> I am sorry that I failed your requirements.

You failed GSoC requirements, not "ours": most of the work should be
done __BEFORE__ the midterm eval; the mentors should be reasonable
confident that the student will succeed.  We have seen no code.

> At least you should have given me a chance to see the results.

What results?

> You have demotivated me more than I thought of.

I am sorry to hear that.

> I was a bit inactive because of two reasons: improper internet
> connection, first time communicating through email.

Incidentally, please _always_ use the "Subject:" line appropriately.

> I had planned to have a good second month as I was returning to my
> college on 7th July or so which has continuous internet connectivity.

Google set the GSoC schedule.
The schedule requirement are not up to us.

You are still welcome to contribute to GNU CLISP.
You can also apply to GSoC 2018.

Thank you.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://honestreporting.com
http://camera.org http://islamexposedonline.com http://jij.org
The best herbal therapy is growing herbs on enemies' graves.

Re: new beta release

[Bruno H. <br...@cl...>]

[CCing clisp-devel]

Sebastian Rasmussen wrote:
> >>     https://sourceforge.net/p/clisp/clisp/ci/tip/tree/src/dutch.lisp
> 
> If I look at the Dutch space-format that you wrote I'm puzzled by
> the following formatting (I skipped the part up until VT to make it
> more readable):
> 
> "      permanent             tijdelijk~%"
> "instanties    bytes  instanties    bytes~%"
> "~9D ~9D  ~9D ~9D~%"
> 
> Wouldn't an example of this be (_ represents spaces):
> "      permanent             tijdelijk~%"
> "instanties    bytes  instanties    bytes~%"
> "_________1 _________1  _________1 _________1~%"
> 
> And so the table wouldn't be aligned..?
> Seems toi me like the format below would be more suitable?
> "~10D ~8D  ~10D ~8D~%" as the output format ought to be:
> 
> "      permanent             tijdelijk~%"
> "instanties    bytes  instanties    bytes~%"
> "---------- --------  ---------- --------~%"
> "_________1 _______1  _________1 _______1~%"
> 
> But maybe I misunderstand the format functions argument?

I think you understand FORMAT quite well. But the "permanent" label is meant
to apply to 2 columns at once. Like here:

> (times (defclass foo () ()))
                                            Permanent            Temporary
Class                                  instances   bytes    instances   bytes
-----                                  --------- ---------  --------- ---------
CONS                                           6        48        136      1088
SIMPLE-VECTOR                                  5       368         11       296
SIMPLE-STRING                                  0         0          6       144
HASH-TABLE                                     1        64          1        64
STANDARD-CLASS                                 1       120          0         0
SYSTEM::INTERNAL-WEAK-LIST                     0        16          2        80
FUNCTION                                       0         0          3        88
SYMBOL                                         0         0          2        64
SIMPLE-BIT-VECTOR                              0         0          4        56
-----                                  --------- ---------  --------- ---------
Gesamt                                        13       616        165      1880

Feel free to either repeat the words "permanent" or "temporary", or to insert
separator characters like "|" if you find that it produces better output.

> Also for the room-format there is a space after the VT while
> there is not in the space-format. Depending on the argument
> consumed by VT relative to the class name length a space
> might be better than none, but I'm not sure.

You are right: the purpose of the space is to avoid that two numbers
accidentally clump together if the class name was long.

Actually, this shows too many spaces; it could be improved:

> (room t)
Class                                   # Instances  Size (bytes)  Average size
-----                                   -----------  ------------  ------------
CONS                                       71066        568528          8.000
SIMPLE-STRING                              12376        429512         34.705
SIMPLE-8BIT-VECTOR                          3649        299200         81.995
SYMBOL                                      8653        276896         32.000
SIMPLE-VECTOR                               2644        212584         80.402
FUNCTION                                    4070        184608         45.358
HASH-TABLE                                   614         39296         64.000
SYSTEM-FUNCTION                             1107         35424         32.000
STANDARD-EFFECTIVE-SLOT-DEFINITION           532         29792         56.000
STANDARD-METHOD                              380         21280         56.000
CLOS::STRUCTURE-EFFECTIVE-SLOT-DEFINITION      237         15168         64.000
STANDARD-CLASS                               123         14760        120.000
STANDARD-GENERIC-FUNCTION                    171         12312         72.000
CLOS::STRUCTURE-DIRECT-SLOT-DEFINITION       237         11376         48.000
SYSTEM::INTERNAL-WEAK-HASHED-ALIST            27         10320        382.222
SYSTEM::INTERNAL-WEAK-LIST                   247          6648         26.915
ENCODING                                     104          5824         56.000
STANDARD-DIRECT-SLOT-DEFINITION              121          5808         48.000
STREAM                                        55          4072         74.036
WEAK-LIST                                    247          3952         16.000
SYSTEM::MACRO                                217          3472         16.000
STRING-STREAM                                 44          3176         72.182
STRUCTURE-CLASS                               26          3120        120.000
BUILT-IN-CLASS                                33          2640         80.000
STRING                                       102          2456         24.078
PATHNAME                                      95          2280         24.000
STANDARD-READER-METHOD                        20          1280         64.000
EQL-SPECIALIZER                               46          1104         24.000
SPECIAL-OPERATOR                              40           960         24.000
PACKAGE                                       19           912         48.000
METHOD-COMBINATION                            10           640         64.000
LONG-FLOAT                                    10           488         48.800
BIGNUM                                        24           416         17.333
FUNCALLABLE-STANDARD-CLASS                     3           360        120.000
SYMBOL-MACRO                                  20           320         16.000
GLOBAL-SYMBOL-MACRO                           20           320         16.000
CONCATENATED-STREAM                            4           288         72.000
SYNONYM-STREAM                                 3           216         72.000
BROADCAST-STREAM                               3           216         72.000
SINGLE-FLOAT                                  12           192         16.000
FILE-STREAM                                    1           168        168.000
LOGICAL-PATHNAME                               5           160         32.000
DOUBLE-FLOAT                                  10           160         16.000
BYTE                                           6            96         16.000
FOREIGN-POINTER                                6            96         16.000
RESTART                                        2            80         40.000
TWO-WAY-STREAM                                 1            72         72.000
ECHO-STREAM                                    1            72         72.000
READTABLE                                      3            72         24.000
RATIO                                          3            48         16.000
FFI:FOREIGN-FUNCTION                           1            40         40.000
NULL                                           1            32         32.000
VECTOR                                         1            32         32.000
FFI:FOREIGN-ADDRESS                            2            32         16.000
FFI:FOREIGN-VARIABLE                           1            32         32.000
SIMPLE-BIT-VECTOR                              2            24         12.000
8BIT-VECTOR                                    1            24         24.000
SIMPLE-ARRAY                                   1            24         24.000
RANDOM-STATE                                   1            16         16.000
COMPLEX                                        1            16         16.000
-----                                   -----------  ------------  ------------
Gesamt                                    107461       2213512         20.598


Bruno

New Swedish PO file for 'clisp' (version 2.49.60)

[Translation P. R. <ro...@tr...>]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'clisp' has been submitted
by the Swedish team of translators.  The file is available at:

    http://translationproject.org/latest/clisp/sv.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

    http://translationproject.org/latest/clisp/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

    http://translationproject.org/domain/clisp.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                <coo...@tr...>