clisp-devel — closed list for developers and testers

Re: Test failure on ARM

[Jerry J. <log...@gm...>]

Thanks for the reply, Sam.

On Mon, Apr 23, 2012 at 10:51 AM, Sam Steingold <sd...@gn...> wrote:
> Jerry, I am afraid your best bet is to try to fix libffcall yourself.
> An alternative is, of course, to build CLISP without FFI.
> Sam.

I was afraid that would be the answer. :-)  I'll see if I can get
access to some ARM hardware so I can get more details on the problem.
In the meantime, I'll turn FFI off for the ARM platform to get the
builds going again.  Wish me luck.
-- 
Jerry James
http://www.jamezone.org/

Re: Test failure on ARM

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

Jerry, I am afraid your best bet is to try to fix libffcall yourself.
An alternative is, of course, to build CLISP without FFI.
Sam.

> * Jerry James <ybtnawreel@tznvy.pbz> [2012-04-19 16:53:53 -0600]:
>
> The Fedora ARM team experience a failure attempting to build clisp
> 2.49 on an armv7hl platform:
>
> http://arm.koji.fedoraproject.org/taskinfo?taskID=729921
>
> The failure is an illegal instruction, which is encountered while
> running foreign function tests.  I suspect that means the problem is
> really in ffcall.  We are currently using a 20100903 CVS snapshot of
> ffcall.  Does anybody have a working build of clisp 2.49 on this
> platform?  If so, what ffcall version are you using?
>
> Thanks,

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X 11.0.11004000
http://www.childpsy.net/ http://americancensorship.org
http://openvotingconsortium.org http://memri.org http://truepeace.org
20% of people do 80% of work; also 80% of people think they are in those 20%.

[ clisp-Bugs-3520570 ] CL:LOGICAL-PATHNAME-TRANSLATIONS signals invalid error condi

[SourceForge.net <no...@so...>]

Bugs item #3520570, was opened at 2012-04-23 01:44
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3520570&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: ANSI compliance issue
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Hans Hübner (lisphans)
>Assigned to: Sam Steingold (sds)
Summary: CL:LOGICAL-PATHNAME-TRANSLATIONS signals invalid error condi

Initial Comment:
as per my reading of the Hyperspec (http://clhs.lisp.se/Body/f_logica.htm), CL:LOGICAL-PATHNAME-TRANSLATIONS should signal a TYPE-ERROR if an unknown logical host name is specified as argument.  CLISP signals a SIMPLE-ERROR instead.

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

Comment By: Sam Steingold (sds)
Date: 2012-04-23 08:46

Message:
thank you for your bug report.
the bug has been fixed in the source tree (mercurial/hg).
you can either wait for the next release (recommended)
or check out the current mercurial tree (see http://clisp.org)
and build CLISP from the sources (be advised that between
releases the source tree is very unstable and may not even build
on your platform).

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3520570&group_id=1355

[ clisp-Bugs-3520570 ] CL:LOGICAL-PATHNAME-TRANSLATIONS signals invalid error condi

[SourceForge.net <no...@so...>]

Bugs item #3520570, was opened at 2012-04-23 01:44
Message generated for change (Tracker Item Submitted) made by lisphans
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3520570&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: ANSI compliance issue
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hans Hübner (lisphans)
Assigned to: Bruno Haible (haible)
Summary: CL:LOGICAL-PATHNAME-TRANSLATIONS signals invalid error condi

Initial Comment:
as per my reading of the Hyperspec (http://clhs.lisp.se/Body/f_logica.htm), CL:LOGICAL-PATHNAME-TRANSLATIONS should signal a TYPE-ERROR if an unknown logical host name is specified as argument.  CLISP signals a SIMPLE-ERROR instead.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3520570&group_id=1355

Re: MT crash

[Vladimir T. <vtz...@gm...>]

On Mon, Apr 23, 2012 at 4:57 AM, Sam Steingold <sd...@gn...> wrote:
> However, I wonder if TRT is to replace
>  end_system_call(); /* just in case */
> with
>  end_blocking_system_call(); /* just in case */
> in OS_error().
> Vladimir, WDYT?

No.
1. There are many system calls which cannot block and are not
surrounded by begin/end_blocking_system_call().
2. Contrary to end_system_call() which can be called many times with
no harm, end_blocking_system_call() that does not have matching
begin_blocking_system_call() may cause deadlock in certain situations
(will check again - I do not not remember the details but in the past
I have tried to do exactly this change and found out it is no go).

Re: MT crash

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

> * Don Cohen <qba...@vf...3-vap.pbz> [2012-04-22 13:19:39 -0700]:
>
> This is done as a user without permission of some sort - works ok as
> root.
>
> [1]> (POSIX:SET-FILE-STAT "/tmp/test-dir0" :MODE 511 :UID 1 :GID 1)
> *** thread is going into lisp land without calling
> end_blocking_call();Aborted (core dumped)
>
> whereas in non-MT version
> [1]> (POSIX:SET-FILE-STAT "/tmp/test-dir0" :MODE 511 :UID 1 :GID 1)
>
> *** - OS-FILE-ERROR(EPERM): Operation not permitted

Okay, this is very easy to fix "locally", i.e., by adding
"end_blocking_system_call()" before OS_file_error in calls.c:my_chmod et al.
However, I wonder if TRT is to replace

  end_system_call(); /* just in case */

with

  end_blocking_system_call(); /* just in case */

in OS_error().

Vladimir, WDYT?

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X 11.0.11004000
http://www.childpsy.net/ http://truepeace.org http://iris.org.il
http://www.memritv.org http://camera.org http://memri.org
The only time you have too much fuel is when you're on fire.

MT crash

[<don...@is...>]

This is in hg build from last night.
This is done as a user without permission of some sort - works ok as
root.

[1]> (POSIX:SET-FILE-STAT "/tmp/test-dir0" :MODE 511 :UID 1 :GID 1)
*** thread is going into lisp land without calling
end_blocking_call();Aborted (core dumped)

whereas in non-MT version
[1]> (POSIX:SET-FILE-STAT "/tmp/test-dir0" :MODE 511 :UID 1 :GID 1)

*** - OS-FILE-ERROR(EPERM): Operation not permitted
The following restarts are available:
ABORT          :R1      Abort main loop
Break 1 [2]>

[ clisp-Bugs-3520018 ] fatal error message blows up with large *print-right-margin*

[SourceForge.net <no...@so...>]

Bugs item #3520018, was opened at 2012-04-20 22:44
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3520018&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Bill Evans (mariposabill)
Assigned to: Bruno Haible (haible)
Summary: fatal error message blows up with large *print-right-margin*

Initial Comment:
My abject apologies if this is a feature, not a bug.

This probably also happens with other errors, but I used division by zero as a handy surrogate.

If I divide by zero and *print-right-margin* is #x3FFFFF, the error message appears as one would expect.  But if I divide by zero and *print-right-margin* is #x400000, then I get several thousand lines of aborted error message, followed by notification of Lisp stack overflow.
=== platform:
Linux tiger 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux
=== glibc version:
GNU C Library (Debian EGLIBC 2.11.2-10) stable release version 2.11.2, by Roland
 McGrath et al.
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.4.5.
Compiled on a Linux 2.6.32 system on 2011-01-23.
Available extensions:
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        BIND-8.2.3-T5B
For bug reporting instructions, please see:
<http://www.debian.org/Bugs/>.
=== clisp version:
GNU CLISP 2.49 (2010-07-07) (built 3543975151) (memory 3543975454)
Software: GNU C 4.4.5 
gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_MODULES -I.  -lreadline -lncurses -ldl    libgnu_cl.a 
SAFETY=0 HEAPCODES LINUX_NOEXEC_HEAPCODES SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libreadline 6.1
Features: 
(REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL
 INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN GETTEXT UNICODE
 BASE-CHAR=CHARACTER PC386 UNIX)
C Modules: (clisp i18n syscalls regexp)
Installation directory: /u/home/clisp/bug5/home/lib/clisp-2.49/
User language: ENGLISH
Machine: I686 (I686) tiger.x441afea5.org [10.0.0.1]
=== build details:
I downloaded the currently released version of clisp today (12 Apr 2012) from http://ftp.gnu.org/pub/gnu/clisp/latest.

I built it the normal way, as shown in the attached script.  Placed into its own empty directory, that script downloads the source, builds and installs clisp, and runs the program twice, first using the higher value of *print-right-margin* (the one that misbehaves), then using the lower value.

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

>Comment By: Sam Steingold (sds)
Date: 2012-04-22 12:19

Message:
I cannot reproduce this with the current hg tip.
could you please check out the hg tip and try it there?
thanks.

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

Comment By: Bill Evans (mariposabill)
Date: 2012-04-20 22:47

Message:
Oops.  I got the date of download wrong.  It's 20 April 2012, not 12 Apr
2012.  Sorry about that.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3520018&group_id=1355

[ clisp-Bugs-3520018 ] fatal error message blows up with large *print-right-margin*

[SourceForge.net <no...@so...>]

Bugs item #3520018, was opened at 2012-04-20 22:44
Message generated for change (Comment added) made by mariposabill
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3520018&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Bill Evans (mariposabill)
Assigned to: Bruno Haible (haible)
Summary: fatal error message blows up with large *print-right-margin*

Initial Comment:
My abject apologies if this is a feature, not a bug.

This probably also happens with other errors, but I used division by zero as a handy surrogate.

If I divide by zero and *print-right-margin* is #x3FFFFF, the error message appears as one would expect.  But if I divide by zero and *print-right-margin* is #x400000, then I get several thousand lines of aborted error message, followed by notification of Lisp stack overflow.
=== platform:
Linux tiger 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux
=== glibc version:
GNU C Library (Debian EGLIBC 2.11.2-10) stable release version 2.11.2, by Roland
 McGrath et al.
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.4.5.
Compiled on a Linux 2.6.32 system on 2011-01-23.
Available extensions:
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        BIND-8.2.3-T5B
For bug reporting instructions, please see:
<http://www.debian.org/Bugs/>.
=== clisp version:
GNU CLISP 2.49 (2010-07-07) (built 3543975151) (memory 3543975454)
Software: GNU C 4.4.5 
gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_MODULES -I.  -lreadline -lncurses -ldl    libgnu_cl.a 
SAFETY=0 HEAPCODES LINUX_NOEXEC_HEAPCODES SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libreadline 6.1
Features: 
(REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL
 INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN GETTEXT UNICODE
 BASE-CHAR=CHARACTER PC386 UNIX)
C Modules: (clisp i18n syscalls regexp)
Installation directory: /u/home/clisp/bug5/home/lib/clisp-2.49/
User language: ENGLISH
Machine: I686 (I686) tiger.x441afea5.org [10.0.0.1]
=== build details:
I downloaded the currently released version of clisp today (12 Apr 2012) from http://ftp.gnu.org/pub/gnu/clisp/latest.

I built it the normal way, as shown in the attached script.  Placed into its own empty directory, that script downloads the source, builds and installs clisp, and runs the program twice, first using the higher value of *print-right-margin* (the one that misbehaves), then using the lower value.

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

>Comment By: Bill Evans (mariposabill)
Date: 2012-04-20 22:47

Message:
Oops.  I got the date of download wrong.  It's 20 April 2012, not 12 Apr
2012.  Sorry about that.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3520018&group_id=1355

[ clisp-Bugs-3520018 ] fatal error message blows up with large *print-right-margin*

[SourceForge.net <no...@so...>]

Bugs item #3520018, was opened at 2012-04-20 22:44
Message generated for change (Tracker Item Submitted) made by mariposabill
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3520018&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Bill Evans (mariposabill)
Assigned to: Bruno Haible (haible)
Summary: fatal error message blows up with large *print-right-margin*

Initial Comment:
My abject apologies if this is a feature, not a bug.

This probably also happens with other errors, but I used division by zero as a handy surrogate.

If I divide by zero and *print-right-margin* is #x3FFFFF, the error message appears as one would expect.  But if I divide by zero and *print-right-margin* is #x400000, then I get several thousand lines of aborted error message, followed by notification of Lisp stack overflow.
=== platform:
Linux tiger 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux
=== glibc version:
GNU C Library (Debian EGLIBC 2.11.2-10) stable release version 2.11.2, by Roland
 McGrath et al.
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.4.5.
Compiled on a Linux 2.6.32 system on 2011-01-23.
Available extensions:
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        BIND-8.2.3-T5B
For bug reporting instructions, please see:
<http://www.debian.org/Bugs/>.
=== clisp version:
GNU CLISP 2.49 (2010-07-07) (built 3543975151) (memory 3543975454)
Software: GNU C 4.4.5 
gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_MODULES -I.  -lreadline -lncurses -ldl    libgnu_cl.a 
SAFETY=0 HEAPCODES LINUX_NOEXEC_HEAPCODES SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libreadline 6.1
Features: 
(REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL
 INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN GETTEXT UNICODE
 BASE-CHAR=CHARACTER PC386 UNIX)
C Modules: (clisp i18n syscalls regexp)
Installation directory: /u/home/clisp/bug5/home/lib/clisp-2.49/
User language: ENGLISH
Machine: I686 (I686) tiger.x441afea5.org [10.0.0.1]
=== build details:
I downloaded the currently released version of clisp today (12 Apr 2012) from http://ftp.gnu.org/pub/gnu/clisp/latest.

I built it the normal way, as shown in the attached script.  Placed into its own empty directory, that script downloads the source, builds and installs clisp, and runs the program twice, first using the higher value of *print-right-margin* (the one that misbehaves), then using the lower value.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3520018&group_id=1355

clisp-cvs Digest, Vol 69, Issue 3

[<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: local address is sometimes 127.0.0.1 and sometimes
      127.0.... (cli...@li...)
   2. clisp: The official binary IP address representation is now a
      byte (cli...@li...)
   3. clisp: style & typos (cli...@li...)
   4. clisp: * src/array.d (data_to_sbvector): add a modexp
      function (cli...@li...)


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

Message: 1
Date: Fri, 20 Apr 2012 00:07:22 +0000
From: cli...@li...
Subject: clisp: local address is sometimes 127.0.0.1 and sometimes
	127.0....
To: cli...@li...
Message-ID:
	<hg....@vz...g>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/169e74dd5a32
changeset: 15572:169e74dd5a32086b799455968fe02312bc5dc162
user:      Sam Steingold <sd...@po...>
date:      2012-04-18 18:05:54 -0400
description:
local address is sometimes 127.0.0.1 and sometimes 127.0.1.1; adjust the local-sa-check call

diffstat:

 modules/rawsock/test.tst |  20 ++++++++------------
 1 files changed, 8 insertions(+), 12 deletions(-)



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

Message: 2
Date: Fri, 20 Apr 2012 00:07:25 +0000
From: cli...@li...
Subject: clisp: The official binary IP address representation is now a
	byte
To: cli...@li...
Message-ID:
	<hg....@vz...g>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/13acccc8b965
changeset: 15574:13acccc8b9657892c8a629333ccd06ea4e792990
user:      Sam Steingold <sd...@po...>
date:      2012-04-19 20:06:50 -0400
description:
The official binary IP address representation is now a byte
vector, not an integer.
* src/socket.d (string_to_addr1): use data_to_sb8vector instead of
LEbytes_to_UI
* modules/rawsock/rawsock.c (CONVERT-ADDRESS): ipv6 is 128 bits,
not 64; accept byte vectors too
* modules/rawsock/test.tst: use CONVERT-ADDRESS instead of ip->ve

diffstat:

 modules/rawsock/rawsock.c   |  16 +++++++++++-----
 modules/rawsock/rawsock.xml |   5 +++--
 modules/rawsock/test.tst    |   8 ++++----
 src/ChangeLog               |  12 +++++++++++-
 src/NEWS                    |   4 ++++
 src/lispbibl.d              |   2 +-
 src/socket.d                |   4 ++--
 7 files changed, 36 insertions(+), 15 deletions(-)



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

Message: 3
Date: Fri, 20 Apr 2012 00:07:21 +0000
From: cli...@li...
Subject: clisp: style & typos
To: cli...@li...
Message-ID:
	<hg....@vz...g>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/45dbabd59234
changeset: 15571:45dbabd59234cd2382a4b8d7f987ad4d0e3b1b4f
user:      Sam Steingold <sd...@po...>
date:      2012-04-18 17:13:39 -0400
description:
style & typos

diffstat:

 src/eval.d |  17 +++++++----------
 1 files changed, 7 insertions(+), 10 deletions(-)



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

Message: 4
Date: Fri, 20 Apr 2012 00:07:24 +0000
From: cli...@li...
Subject: clisp: * src/array.d (data_to_sbvector): add a modexp
	function
To: cli...@li...
Message-ID:
	<hg....@vz...g>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/0f64e54b0f15
changeset: 15573:0f64e54b0f1538c8f122b33c8c8d78f879fce043
user:      Sam Steingold <sd...@po...>
date:      2012-04-19 19:04:20 -0400
description:
* src/array.d (data_to_sbvector): add a modexp function
(copy_sbvector): use it
* src/lispbibl.d (data_to_sbvector): add the prototype
(data_to_sb8vector): add a #define and export both to clisp.h
* modules/berkeley-db/bdb.c, modules/clx/new-clx/clx.f:
* modules/dirkey/dirkey.c, modules/gdbm/gdbm.c:
* modules/pcre/cpcre.c, modules/rawsock/rawsock.c:
* modules/syscalls/calls.c: use them

diffstat:

 modules/berkeley-db/bdb.c    |  16 +++-------------
 modules/clx/new-clx/clx.f    |  12 +++---------
 modules/clx/new-clx/test.tst |  15 ++++++++++++---
 modules/dirkey/dirkey.c      |  13 ++-----------
 modules/gdbm/gdbm.c          |   8 +++-----
 modules/pcre/cpcre.c         |   7 +------
 modules/rawsock/rawsock.c    |   7 ++-----
 modules/syscalls/calls.c     |   3 +--
 src/ChangeLog                |  11 +++++++++++
 src/array.d                  |  28 ++++++++++++++++++----------
 src/lispbibl.d               |  14 ++++++++++++++
 11 files changed, 70 insertions(+), 64 deletions(-)



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

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2

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

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


End of clisp-cvs Digest, Vol 69, Issue 3
****************************************

Test failure on ARM

[Jerry J. <log...@gm...>]

The Fedora ARM team experience a failure attempting to build clisp
2.49 on an armv7hl platform:

http://arm.koji.fedoraproject.org/taskinfo?taskID=729921

The failure is an illegal instruction, which is encountered while
running foreign function tests.  I suspect that means the problem is
really in ffcall.  We are currently using a 20100903 CVS snapshot of
ffcall.  Does anybody have a working build of clisp 2.49 on this
platform?  If so, what ffcall version are you using?

Thanks,
-- 
Jerry James
http://www.jamezone.org/

clisp-cvs Digest, Vol 69, 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: (c)year (cli...@li...)
   2. clisp: * src/error.d (error_pos_integer): add, based on
      src/char... (cli...@li...)


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

Message: 1
Date: Wed, 18 Apr 2012 21:10:25 +0000
From: cli...@li...
Subject: clisp: (c)year
To: cli...@li...
Message-ID:
	<hg....@vz...g>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/9735da4ebb9b
changeset: 15569:9735da4ebb9b90d1434dd881e557024f080d9143
user:      Sam Steingold <sd...@po...>
date:      2012-04-18 16:53:48 -0400
description:
(c)year

diffstat:

 modules/i18n/gettext.c |  2 +-
 modules/pcre/cpcre.c   |  2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)



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

Message: 2
Date: Wed, 18 Apr 2012 21:10:26 +0000
From: cli...@li...
Subject: clisp: * src/error.d (error_pos_integer): add, based on
	src/char...
To: cli...@li...
Message-ID:
	<hg....@vz...g>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/8cb53643d8e7
changeset: 15570:8cb53643d8e7594f40bae03f42644d6a9ad0decb
user:      Sam Steingold <sd...@po...>
date:      2012-04-18 16:59:29 -0400
description:
* src/error.d (error_pos_integer): add, based on src/charstrg.d:error_posint
* src/lispbibl.d (error_pos_integer): add the prototype
* charstrg.d (error_posint): remove
(test_index): use error_pos_integer instead
* src/sequence.d (error_posint): remove
(test_start_end, test_start_end_1, test_count_arg):
use error_pos_integer instead

diffstat:

 src/ChangeLog  |  10 ++++++++++
 src/charstrg.d |  18 ++----------------
 src/error.d    |  19 ++++++++++++++++++-
 src/lispbibl.d |   9 +++++++--
 src/sequence.d |  21 ++++++---------------
 5 files changed, 43 insertions(+), 34 deletions(-)



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

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2

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

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


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

[ clisp-Bugs-3512035 ] (require "linux") fails on undefined symbol rpl_ioctl

[SourceForge.net <no...@so...>]

Bugs item #3512035, was opened at 2012-03-27 10:36
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3512035&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: lisp error
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Pascal J. Bourguignon (informatimago)
Assigned to: Bruno Haible (haible)
Summary: (require "linux") fails on undefined symbol rpl_ioctl 

Initial Comment:
On gentoo: 

$ uname -a
Linux kuiper 2.6.38-gentoo-r6-pjb-c9 #2 SMP Wed Jul 13 00:23:08 CEST 2011 x86_64 Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz GenuineIntel GNU/Linux

I cannot load the linux module, because of some undefined symbol:

TEST> (lisp-implementation-version)
"2.49+ (2010-07-17) (built 3541129397) (memory 3541129660)"
TEST> (require "linux")
;; Loading file /data/languages/clisp-hg/lib/clisp-2.49+/dynmod/linux.lisp ...
;;  Loading module linux from /data/languages/clisp-hg/lib/clisp-2.49+/dynmod/lib-linux.so

*** - SYSTEM::DYNLOAD-MODULES: "dlopen" -> "/data/languages/clisp-hg/lib/clisp-2.49+/dynmod/lib-linux.so: undefined symbol: rpl_ioctl"
The following restarts are available:
SKIP           :R1      skip (DYNLOAD-MODULES # '#)
RETRY          :R2      retry (DYNLOAD-MODULES # '#)
STOP           :R3      stop loading file /data/languages/clisp-hg/lib/clisp-2.49+/dynmod/linux.lisp
RETRY          :R4      Retry SLIME REPL evaluation request.
PROCESS-INPUT  :R5      Continue reading input.
ABORT          :R6      Return to SLIME's top level.
CLOSE-CONNECTION :R7    Close SLIME connection.
ABORT          :R8      Abort main loop
C/Break 1 COM.INFORMATIMAGO.RUN-PROGRAM.TEST[2]> :bt



Indeed, there's a reference to rpl_ioctl in lib-linux.so:
[pjb@kuiper :0 tmp]$ nm /data/languages/clisp-hg/lib/clisp-2.49+/dynmod/lib-linux.so|grep rpl
                 U rpl_ioctl
[pjb@kuiper :0 tmp]$ ldd /data/languages/clisp-hg/lib/clisp-2.49+/dynmod/lib-linux.so
	linux-vdso.so.1 =>  (0x00007fff269ff000)
	libm.so.6 => /lib/libm.so.6 (0x00007f9738b13000)
	libpthread.so.0 => /lib/libpthread.so.0 (0x00007f97388f5000)
	libc.so.6 => /lib/libc.so.6 (0x00007f973858f000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f9738fa2000)

But I can't find it in those libraries.

[pjb@kuiper :0 tmp]$ nm /lib64/ld-linux-x86-64.so.2 | grep rpl
nm: /lib64/ld-linux-x86-64.so.2: no symbols
[pjb@kuiper :0 tmp]$ nm /lib/libc.so.6 | grep rpl
nm: /lib/libc.so.6: no symbols

Sam says:

rpl_* come from gnulib, so it is in libgnu.a;
libgnu.a is linked into lisp.run
(all of them: boot, base, and full, so "clisp -K full" works);
but since rpl_ioctl is not used by base,
it is dropped from base/lisp.run;
so when you try to load lib-linux.so which uses rpl_ioctl, it fails.

This patch fixes the error, but I don't like the solution because it means that
every module which uses rpl_ioctl will come with its own implementation.

A better solution is welcome.


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

>Comment By: Sam Steingold (sds)
Date: 2012-04-18 15:18

Message:
on linux my patch increases the sizes of dynamic libraries by less than
1%:

lib-linux.so: 138882 --> 139965
lib-rawsock.so: 265699  -->  266758

I guess this is not such a big deal on linux, but on other platforms, 
where libgnu is basically glibc in disguise, 
linking it in twice may not me such a good idea.

I think it would be great if you could complain to  bug...@gn...
about the lack of libgnu.so, see
http://article.gmane.org/gmane.comp.lib.gnulib.bugs:27753

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

Comment By: Sam Steingold (sds)
Date: 2012-03-27 11:15

Message:
at least rawsock needs a similar patch to fix require.
a better approach is necessary.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3512035&group_id=1355

Re: apply on dotted argument lists

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

Hi Bruno,

> * Sam Steingold <fq...@ta...t> [2012-04-15 21:49:03 -0400]:
> I think Occam requires the same behavior in both cases.

... including eval.

Do you object?

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X 11.0.11004000
http://www.childpsy.net/ http://dhimmi.com http://truepeace.org
http://americancensorship.org http://memri.org http://ffii.org
Nostalgia isn't what it used to be.

Re: What does this error mean in clisp?

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

"Yves S. Garret" <you...@gm...> writes:

> Oh, I didn't know that link even existed.  Thanks for letting me know!

Also have a look at http://www.cliki.net/TutorialClispDebugger

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

Re: What does this error mean in clisp?

[Yves S. G. <you...@gm...>]

Oh, I didn't know that link even existed.  Thanks for letting me know!

On Sun, Apr 15, 2012 at 10:11 PM, Sam Steingold <sd...@gn...> wrote:

> observe this note in the beginning of your paste:
>
> --8<---------------cut here---------------start------------->8---
> Type :h and hit Enter for context help.
> --8<---------------cut here---------------end--------------->8---
>
> I added it many years ago in the hope that it would be useful, but,
> apparently, it is not.
>
> Now,
>
> --8<---------------cut here---------------start------------->8---
> [7]> (expt 4 20))
> 1099511627776
> [8]>
> *** - READ from #<INPUT CONCATENATED-STREAM #<INPUT STRING-INPUT-STREAM>
> #<IO TERMINAL-STREAM>>: an object cannot start with #\)
> --8<---------------cut here---------------end--------------->8---
>
> so you typed 2 closing parens instead of one and clisp is telling you
> just that.
> clisp keeps reading your input, it is not limited to one form per line,
> e.g.:
>
> --8<---------------cut here---------------start------------->8---
> [1]> (1+ 1) (! 10)
> 2
> [2]>
> 3628800
> [3]>
> --8<---------------cut here---------------end--------------->8---
>
> so when it is done reading (expt 4 20), it reads ) and tells you that
> it's not okay.
>
> now, if you want to know how to debug an error or get out of the error
> prompts, you should either follow the first message you got from clisp
> (see above, i.e., type :h RET) or, better yet, RTFM
> (http://clisp.org/impnotes/repl.html).
>
>
> --
> Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X
> 11.0.11004000
> http://www.childpsy.net/ http://www.PetitionOnline.com/tap12009/
> http://openvotingconsortium.org http://memri.org http://mideasttruth.com
> UNIX is as friendly to you as you are to it. Windows is hostile no matter
> what.
>

Re: What does this error mean in clisp?

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

observe this note in the beginning of your paste:

--8<---------------cut here---------------start------------->8---
Type :h and hit Enter for context help.
--8<---------------cut here---------------end--------------->8---

I added it many years ago in the hope that it would be useful, but,
apparently, it is not.

Now,

--8<---------------cut here---------------start------------->8---
[7]> (expt 4 20))
1099511627776
[8]>
*** - READ from #<INPUT CONCATENATED-STREAM #<INPUT STRING-INPUT-STREAM> #<IO TERMINAL-STREAM>>: an object cannot start with #\)
--8<---------------cut here---------------end--------------->8---

so you typed 2 closing parens instead of one and clisp is telling you
just that.
clisp keeps reading your input, it is not limited to one form per line, e.g.:

--8<---------------cut here---------------start------------->8---
[1]> (1+ 1) (! 10)
2
[2]> 
3628800
[3]> 
--8<---------------cut here---------------end--------------->8---

so when it is done reading (expt 4 20), it reads ) and tells you that
it's not okay.

now, if you want to know how to debug an error or get out of the error
prompts, you should either follow the first message you got from clisp
(see above, i.e., type :h RET) or, better yet, RTFM
(http://clisp.org/impnotes/repl.html).


-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X 11.0.11004000
http://www.childpsy.net/ http://www.PetitionOnline.com/tap12009/
http://openvotingconsortium.org http://memri.org http://mideasttruth.com
UNIX is as friendly to you as you are to it. Windows is hostile no matter what.

What does this error mean in clisp?

[Yves S. G. <you...@gm...>]

I have to admit that I'm a Lisp n00b.  I've mucked with in college... 8
years ago :) .  I want to get back into the swing of things.

Here it is:
http://bin.cakephp.org/view/700929814

Re: apply on dotted argument lists

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

Hi Bruno,

> * Bruno Haible <oe...@py...t> [2012-04-13 02:42:16 +0200]:
>
> Moving the discussion from the bug tracker
> https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3517196&group_id=1355
> to the list.

bad idea.
before: both clisp-devel and sf bug tracker knew the reasoning.
now: only clisp-devel does.

>> 1. I don't think you can separate compiled from interpreted here:
>> both are done by apply_closure
>
> The compiled closure is handled in the first part of apply_closure,
> the interpreted one in the last 20 lines of apply_closure. This
> one-liner should produce an error in the interpreted case:

sure.

>> 2. I don't think adding an explicit list check to the evaluator makes
>> much sense.
>
> Why? I think it does: Any useful error message that occurs while a
> user is testing his program in interpreted mode is useful.

what I meant was something like

  object dotted;
  list_length(args,&dotted);
  if (!nullp(dotted))
    goto error_dotted;

>> 3. Bruno, why do you have error_apply_dotted signal a program-error and
>> error_apply_toofew signal an argument-list-dotted error? these look weird:
>> 
>> > (apply #'cons 1)
>> *** - APPLY: dotted argument list given to CONS : 1
>> > (apply #'read-from-string "a" 2)
>> *** - APPLY: argument list given to READ-FROM-STRING is dotted (terminated
>> by 2)
>> 
>> I think the messages (and errors) should be identical.
>
> I agree that the messages are unnecessarily different.
>
> About the error types: Since PROGRAM-ERROR is defined as errors relating
> to "program syntax"
> <http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/contyp_program-error.html>
> but here we don't have a wrong program (that could be caught at
> compile-time), just wrong data (at runtime), I think that PROGRAM-ERROR
> is wrong here, in both cases.

I am not so sure.  (apply #'foo 1) can be caught at compile time and is
probably second only to (format "..." ...) in frequency.

> But in the first case, CLHS section 3.5.1.2
> <http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/sec_3-5-1-2.html>
> forces us to signal a PROGRAM-ERROR (or subtype thereof), even though
> it's nonsense.
>
> In the second case, CLHS does not specify which error is signaled
> (see <http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_apply.html#apply>:
> "Exceptional Situations: None."). Why should we repeat the same nonsense here?

I think Occam requires the same behavior in both cases.
Moreover, your argument-list-dotted is already a subtype of
program-error, so I really see no reason for this dichotomy.

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X 11.0.11004000
http://www.childpsy.net/ http://americancensorship.org http://www.memritv.org
http://memri.org http://jihadwatch.org http://truepeace.org
You think Oedipus had a problem -- Adam was Eve's mother.

apply on dotted argument lists

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

Hi Sam,

Moving the discussion from the bug tracker
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3517196&group_id=1355
to the list.

I wrote:
> Confirmed:
> 
> > (defun something (a b &rest pieces) (type-of pieces))
> > (apply #'something 5 6 (append NIL "X"))
> NULL
> > (compile 'something)
> SOMETHING ;
> 2 ;
> NIL
> > (apply #'something 5 6 (append NIL "X"))
> (SIMPLE-BASE-STRING 1)
> 
> SBCL yields an error in this situation.
> 
> In CLHS
> http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/glo_f.html#function
> a function is supposed to be "called with zero or more arguments". A dotted
> argument list is not foreseen.
> 
> Also, in
> http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_apply.html#apply
> the arguments list is defined to be a "spreadable argument list
> designator", "whose last element is a list L2 of length m". This does not
> allow a dotted list.
> 
> See also CLHS
> http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/sec_3-4-1-3.html
> "The value of a rest parameter is permitted, but not required, to share
> structure with the last argument to apply."
> 
> From a user's perspective, I think it would be good if clisp would be
> changed to emit an error in this case as well, in interpreted mode only.
> In compiled mode, which is not designed to do maximum error checking, I
> would not change anything.

You replied:
> 1. I don't think you can separate compiled from interpreted here: both are
> done by apply_closure

The compiled closure is handled in the first part of apply_closure, the
interpreted one in the last 20 lines of apply_closure. This one-liner
should produce an error in the interpreted case:

--- eval.d	2011-08-02 00:53:00.000000000 +0200
+++ eval.d.mod	2012-04-13 02:29:07.000000000 +0200
@@ -4827,6 +4827,7 @@
       if (((uintL)~(uintL)0 > ca_limit_1) && (args_on_stack > ca_limit_1))
         goto error_toomany;
     }
+    if (!nullp(args)) goto error_dotted;
     var gcv_object_t* args_pointer = args_end_pointer STACKop args_on_stack;
     with_saved_back_trace_iclosure(closure,args_pointer,args_on_stack,
       funcall_iclosure(closure,args_pointer,args_on_stack); );


> 2. I don't think adding an explicit list check to the evaluator makes much
> sense.

Why? I think it does: Any useful error message that occurs while a user
is testing his program in interpreted mode is useful.

> 3. Bruno, why do you have error_apply_dotted signal a program-error and
> error_apply_toofew signal an argument-list-dotted error? these look weird:
> 
> > (apply #'cons 1)
> *** - APPLY: dotted argument list given to CONS : 1
> > (apply #'read-from-string "a" 2)
> *** - APPLY: argument list given to READ-FROM-STRING is dotted (terminated
> by 2)
> 
> I think the messages (and errors) should be identical.

I agree that the messages are unnecessarily different.

About the error types: Since PROGRAM-ERROR is defined as errors relating
to "program syntax"
<http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/contyp_program-error.html>
but here we don't have a wrong program (that could be caught at
compile-time), just wrong data (at runtime), I think that PROGRAM-ERROR
is wrong here, in both cases.

But in the first case, CLHS section 3.5.1.2
<http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/sec_3-5-1-2.html>
forces us to signal a PROGRAM-ERROR (or subtype thereof), even though
it's nonsense.

In the second case, CLHS does not specify which error is signaled
(see <http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_apply.html#apply>:
"Exceptional Situations: None."). Why should we repeat the same nonsense here?

Bruno

[ clisp-Bugs-3517196 ] #'apply reacts differently to dotted list when compiled

[SourceForge.net <no...@so...>]

Bugs item #3517196, was opened at 2012-04-12 06:23
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3517196&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Bill Evans (mariposabill)
Assigned to: Bruno Haible (haible)
Summary: #'apply reacts differently to dotted list when compiled

Initial Comment:
My abject apologies if this is a feature, not a bug.

If I (apply #'something 5 6 (append NIL "X")), where #'something begins with "defun something (a b &rest pieces)", then within #'something, (type-of pieces) will be either NULL (if the lisp program is interpreted) or (SIMPLE-BASE-STRING 1) (if the lisp program is compiled).  Granted, I shouldn't be doing that, but ...

=== platform:
Linux tiger 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux
=== glibc version:
GNU C Library (Debian EGLIBC 2.11.2-10) stable release version 2.11.2, by Roland McGrath et al.
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.4.5.
Compiled on a Linux 2.6.32 system on 2011-01-23.
Available extensions:
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        BIND-8.2.3-T5B
For bug reporting instructions, please see:
<http://www.debian.org/Bugs/>.
=== clisp version:
GNU CLISP 2.49 (2010-07-07) (built 3543225158) (memory 3543225458)
Software: GNU C 4.4.5 
gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_MODULES -I.  -lreadline -lncurses -ldl    libgnu_cl.a 
SAFETY=0 HEAPCODES LINUX_NOEXEC_HEAPCODES SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libreadline 6.1
Features: 
(REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL
 INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN GETTEXT UNICODE
 BASE-CHAR=CHARACTER PC386 UNIX)
C Modules: (clisp i18n syscalls regexp)
Installation directory: /u/home/clisp/bug4/home/lib/clisp-2.49/
User language: ENGLISH
Machine: I686 (I686) tiger.x441afea5.org [10.0.0.1]
=== build details:
I downloaded the currently released version of clisp today (12 Apr 2012) from http://ftp.gnu.org/pub/gnu/clisp/latest.

I built it the normal way, as shown in the attached script.  Placed into its own empty directory, that script downloads the source, builds and installs clisp, and runs the program, first interpreted and then compiled.

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

>Comment By: Sam Steingold (sds)
Date: 2012-04-12 13:15

Message:
1. I don't think you can separate compiled from interpreted here: both are
done by apply_closure

2. I don't think adding an explicit list check to the evaluator makes much
sense.

3. Bruno, why do you have error_apply_dotted signal a program-error and
error_apply_toofew signal an argument-list-dotted error? these look weird:

> (apply #'cons 1)
*** - APPLY: dotted argument list given to CONS : 1
> (apply #'read-from-string "a" 2)
*** - APPLY: argument list given to READ-FROM-STRING is dotted (terminated
by 2)

I think the messages (and errors) should be identical.

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

Comment By: Bruno Haible (haible)
Date: 2012-04-12 08:58

Message:
Confirmed:

> (defun something (a b &rest pieces) (type-of pieces))
> (apply #'something 5 6 (append NIL "X"))
NULL
> (compile 'something)
SOMETHING ;
2 ;
NIL
> (apply #'something 5 6 (append NIL "X"))
(SIMPLE-BASE-STRING 1)

SBCL yields an error in this situation.

In CLHS
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/glo_f.html#function
a function is supposed to be "called with zero or more arguments". A dotted
argument list is not foreseen.

Also, in
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_apply.html#apply
the arguments list is defined to be a "spreadable argument list
designator",
"whose last element is a list L2 of length m". This does not allow a dotted
list.

See also CLHS
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/sec_3-4-1-3.html
"The value of a rest parameter is permitted, but not required, to share
structure with the last argument to apply."

From a user's perspective, I think it would be good if clisp would be
changed to emit an error in this case as well, in interpreted mode only.
In compiled mode, which is not designed to do maximum error checking, I
would not change anything.


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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3517196&group_id=1355

[ clisp-Bugs-3517196 ] #'apply reacts differently to dotted list when compiled

[SourceForge.net <no...@so...>]

Bugs item #3517196, was opened at 2012-04-12 06:23
Message generated for change (Comment added) made by haible
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3517196&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Bill Evans (mariposabill)
Assigned to: Bruno Haible (haible)
Summary: #'apply reacts differently to dotted list when compiled

Initial Comment:
My abject apologies if this is a feature, not a bug.

If I (apply #'something 5 6 (append NIL "X")), where #'something begins with "defun something (a b &rest pieces)", then within #'something, (type-of pieces) will be either NULL (if the lisp program is interpreted) or (SIMPLE-BASE-STRING 1) (if the lisp program is compiled).  Granted, I shouldn't be doing that, but ...

=== platform:
Linux tiger 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux
=== glibc version:
GNU C Library (Debian EGLIBC 2.11.2-10) stable release version 2.11.2, by Roland McGrath et al.
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.4.5.
Compiled on a Linux 2.6.32 system on 2011-01-23.
Available extensions:
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        BIND-8.2.3-T5B
For bug reporting instructions, please see:
<http://www.debian.org/Bugs/>.
=== clisp version:
GNU CLISP 2.49 (2010-07-07) (built 3543225158) (memory 3543225458)
Software: GNU C 4.4.5 
gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_MODULES -I.  -lreadline -lncurses -ldl    libgnu_cl.a 
SAFETY=0 HEAPCODES LINUX_NOEXEC_HEAPCODES SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libreadline 6.1
Features: 
(REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL
 INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN GETTEXT UNICODE
 BASE-CHAR=CHARACTER PC386 UNIX)
C Modules: (clisp i18n syscalls regexp)
Installation directory: /u/home/clisp/bug4/home/lib/clisp-2.49/
User language: ENGLISH
Machine: I686 (I686) tiger.x441afea5.org [10.0.0.1]
=== build details:
I downloaded the currently released version of clisp today (12 Apr 2012) from http://ftp.gnu.org/pub/gnu/clisp/latest.

I built it the normal way, as shown in the attached script.  Placed into its own empty directory, that script downloads the source, builds and installs clisp, and runs the program, first interpreted and then compiled.

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

>Comment By: Bruno Haible (haible)
Date: 2012-04-12 08:58

Message:
Confirmed:

> (defun something (a b &rest pieces) (type-of pieces))
> (apply #'something 5 6 (append NIL "X"))
NULL
> (compile 'something)
SOMETHING ;
2 ;
NIL
> (apply #'something 5 6 (append NIL "X"))
(SIMPLE-BASE-STRING 1)

SBCL yields an error in this situation.

In CLHS
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/glo_f.html#function
a function is supposed to be "called with zero or more arguments". A dotted
argument list is not foreseen.

Also, in
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_apply.html#apply
the arguments list is defined to be a "spreadable argument list
designator",
"whose last element is a list L2 of length m". This does not allow a dotted
list.

See also CLHS
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/sec_3-4-1-3.html
"The value of a rest parameter is permitted, but not required, to share
structure with the last argument to apply."

From a user's perspective, I think it would be good if clisp would be
changed to emit an error in this case as well, in interpreted mode only.
In compiled mode, which is not designed to do maximum error checking, I
would not change anything.


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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3517196&group_id=1355

[ clisp-Bugs-3517196 ] #'apply reacts differently to dotted list when compiled

[SourceForge.net <no...@so...>]

Bugs item #3517196, was opened at 2012-04-12 06:23
Message generated for change (Tracker Item Submitted) made by mariposabill
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3517196&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Bill Evans (mariposabill)
Assigned to: Bruno Haible (haible)
Summary: #'apply reacts differently to dotted list when compiled

Initial Comment:
My abject apologies if this is a feature, not a bug.

If I (apply #'something 5 6 (append NIL "X")), where #'something begins with "defun something (a b &rest pieces)", then within #'something, (type-of pieces) will be either NULL (if the lisp program is interpreted) or (SIMPLE-BASE-STRING 1) (if the lisp program is compiled).  Granted, I shouldn't be doing that, but ...

=== platform:
Linux tiger 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux
=== glibc version:
GNU C Library (Debian EGLIBC 2.11.2-10) stable release version 2.11.2, by Roland McGrath et al.
Copyright (C) 2009 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.4.5.
Compiled on a Linux 2.6.32 system on 2011-01-23.
Available extensions:
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        BIND-8.2.3-T5B
For bug reporting instructions, please see:
<http://www.debian.org/Bugs/>.
=== clisp version:
GNU CLISP 2.49 (2010-07-07) (built 3543225158) (memory 3543225458)
Software: GNU C 4.4.5 
gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_MODULES -I.  -lreadline -lncurses -ldl    libgnu_cl.a 
SAFETY=0 HEAPCODES LINUX_NOEXEC_HEAPCODES SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libreadline 6.1
Features: 
(REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL
 INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN GETTEXT UNICODE
 BASE-CHAR=CHARACTER PC386 UNIX)
C Modules: (clisp i18n syscalls regexp)
Installation directory: /u/home/clisp/bug4/home/lib/clisp-2.49/
User language: ENGLISH
Machine: I686 (I686) tiger.x441afea5.org [10.0.0.1]
=== build details:
I downloaded the currently released version of clisp today (12 Apr 2012) from http://ftp.gnu.org/pub/gnu/clisp/latest.

I built it the normal way, as shown in the attached script.  Placed into its own empty directory, that script downloads the source, builds and installs clisp, and runs the program, first interpreted and then compiled.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3517196&group_id=1355

clisp-cvs Digest, Vol 69, 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: (mod-set-example): fix clisp-link arg order (reported
      by ... (cli...@li...)


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

Message: 1
Date: Mon, 09 Apr 2012 17:27:36 +0000
From: cli...@li...
Subject: clisp: (mod-set-example): fix clisp-link arg order (reported
	by ...
To: cli...@li...
Message-ID:
	<hg....@vz...g>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/daec29679221
changeset: 15568:daec29679221a1e38d2ce1a96fba5d143960d273
user:      Sam Steingold <sd...@po...>
date:      2012-04-09 13:24:34 -0400
description:
(mod-set-example): fix clisp-link arg order (reported by Michael Kappert)

diffstat:

 doc/impext.xml |  2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)



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

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

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

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


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