gmane.lisp.clisp.devel

[ clisp-Patches-3529607 ] Format specifier patch

SourceForge.net — 2012-05-25T01:37:08

Patches item #3529607, was opened at 2012-05-24 15:52
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=301355&aid=3529607&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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jerry James (jjames)
Assigned to: Nobody/Anonymous (nobody)
Summary: Format specifier patch

Initial Comment:
While compiling on a 32-bit platform, I saw some GCC warnings about printf arguments not matching the corresponding format specifiers.  This patch fixes all of the warnings I saw on that platform.

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

Date: 2012-05-24 18:37

Message:
this patch results in these warnings on amd64:

In file included from ../src/spvw.d:161:0:
../src/spvw_debug.d: In function

[ clisp-Patches-3529615 ] ARM fixes

SourceForge.net — 2012-05-24T23:02:27

Patches item #3529615, was opened at 2012-05-24 16:02
Message generated for change (Tracker Item Submitted) made by jjames
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=301355&aid=3529615&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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jerry James (jjames)
Assigned to: Nobody/Anonymous (nobody)
Summary: ARM fixes

Initial Comment:
As reported recently on the mailing list, I have had some problems with clisp failing to build on ARM platforms.  WIth the help of Google and the ARM assembly language reference manual, I think I have all the problems sorted out now.  The illegal instruction problem I reported is due to lines like this:

LDMFD sp!, {v1,v2,v3,v4,v5,v6,pc}^

The trailing carat indicates that this is a return-from-exception.  But it isn't.  All i

[ clisp-Patches-3529607 ] Format specifier patch

SourceForge.net — 2012-05-24T22:52:20

Patches item #3529607, was opened at 2012-05-24 15:52
Message generated for change (Tracker Item Submitted) made by jjames
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=301355&aid=3529607&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: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jerry James (jjames)
Assigned to: Nobody/Anonymous (nobody)
Summary: Format specifier patch

Initial Comment:
While compiling on a 32-bit platform, I saw some GCC warnings about printf arguments not matching the corresponding format specifiers.  This patch fixes all of the warnings I saw on that platform.

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

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

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

[ clisp-Bugs-3525509 ] CLISP treats CL:REQUIRE specially at compiletime

SourceForge.net — 2012-05-10T12:51:54

Bugs item #3525509, was opened at 2012-05-10 05:48
Message generated for change (Comment added) made by xach
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3525509&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: lisp error
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Zach Beane (xach)
Assigned to: Bruno Haible (haible)
Summary: CLISP treats CL:REQUIRE specially at compile time

Initial Comment:
I have a file "test.lisp" that contains only this:

  (require 'bogus)

When I start "clisp -ansi -norc" and issue (compile-file "test.lisp"), I get this:

    [1]> (compile-file "test.lisp")
    ;; Compiling file /home/xach/test.lisp ...
    *** - LOAD: A file with name BOGUS does not exist
    The following restarts are available:
    ABORT          :R1      Abort main loop
    Break 1 [2]> :bt

[ clisp-Bugs-3525509 ] CLISP treats CL:REQUIRE specially at compiletime

SourceForge.net — 2012-05-10T12:48:32

Bugs item #3525509, was opened at 2012-05-10 05:48
Message generated for change (Tracker Item Submitted) made by xach
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3525509&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: lisp error
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Zach Beane (xach)
Assigned to: Bruno Haible (haible)
Summary: CLISP treats CL:REQUIRE specially at compile time

Initial Comment:
I have a file "test.lisp" that contains only this:

  (require 'bogus)

When I start "clisp -ansi -norc" and issue (compile-file "test.lisp"), I get this:

    [1]> (compile-file "test.lisp")
    ;; Compiling file /home/xach/test.lisp ...
    *** - LOAD: A file with name BOGUS does not exist
    The following restarts are available:
    ABORT          :R1      Abort main loop
    Break 1 [2]>

[ clisp-Bugs-3524255 ] ANSI CL forbids mixed-type complex numbers

SourceForge.net — 2012-05-07T14:40:14

Bugs item #3524255, was opened at 2012-05-06 22:38
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3524255&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
Resolution: Invalid
Priority: 5
Private: No
Submitted By: John Cowan (johnwcowan)
Assigned to: Bruno Haible (haible)
Summary: ANSI CL forbids mixed-type complex numbers

Initial Comment:
CLHS (under Function COMPLEX) says that the real and imaginary parts of a complex numbers must either be both rational or both of the same float type, and if they are not, floating-point coercion must be done.  One of the given examples is (complex 1 .99) =>  #C(1.0 0.99).

But in CLISP, (integerp (realpart (complex 1 .99)) => #t.  This means that the real part is being stored as a rational number, sin

[ clisp-Bugs-3524255 ] ANSI CL forbids mixed-type complex numbers

SourceForge.net — 2012-05-07T14:11:02

Bugs item #3524255, was opened at 2012-05-06 22:38
Message generated for change (Comment added) made by johnwcowan
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3524255&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
Resolution: Invalid
Priority: 5
Private: No
Submitted By: John Cowan (johnwcowan)
Assigned to: Bruno Haible (haible)
Summary: ANSI CL forbids mixed-type complex numbers

Initial Comment:
CLHS (under Function COMPLEX) says that the real and imaginary parts of a complex numbers must either be both rational or both of the same float type, and if they are not, floating-point coercion must be done.  One of the given examples is (complex 1 .99) =>  #C(1.0 0.99).

But in CLISP, (integerp (realpart (complex 1 .99)) => #t.  This means that the real part is being stored as a rational numb

[ clisp-Bugs-3524255 ] ANSI CL forbids mixed-type complex numbers

SourceForge.net — 2012-05-07T13:51:50

Bugs item #3524255, was opened at 2012-05-06 22:38
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3524255&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
Priority: 5
Private: No
Submitted By: John Cowan (johnwcowan)
Assigned to: Bruno Haible (haible)
Summary: ANSI CL forbids mixed-type complex numbers

Initial Comment:
CLHS (under Function COMPLEX) says that the real and imaginary parts of a complex numbers must either be both rational or both of the same float type, and if they are not, floating-point coercion must be done.  One of the given examples is (complex 1 .99) =>  #C(1.0 0.99).

But in CLISP, (integerp (realpart (complex 1 .99)) => #t.  This means that the real part is being stored as a rational number, since there is no coerc

[ clisp-Bugs-3524255 ] ANSI CL forbids mixed-type complex numbers

SourceForge.net — 2012-05-07T05:38:38

Bugs item #3524255, was opened at 2012-05-06 22:38
Message generated for change (Tracker Item Submitted) made by johnwcowan
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3524255&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: John Cowan (johnwcowan)
Assigned to: Bruno Haible (haible)
Summary: ANSI CL forbids mixed-type complex numbers

Initial Comment:
CLHS (under Function COMPLEX) says that the real and imaginary parts of a complex numbers must either be both rational or both of the same float type, and if they are not, floating-point coercion must be done.  One of the given examples is (complex 1 .99) =>  #C(1.0 0.99).

But in CLISP, (integerp (realpart (complex 1 .99)) => #t.  This means that the real part is being stored

clisp-cvs Digest, Vol 70, Issue 1

2012-05-04T12:05:07

Send clisp-cvs mailing list submissions to
clisp-cvs< at >lists.sourceforge.net

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
clisp-cvs-request< at >lists.sourceforge.net

You can reach the person managing the list at
clisp-cvs-owner< at >lists.sourceforge.net

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: update berkeley-db to 5.1
      (clisp-cvs-request< at >lists.sourceforge.net)


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

Message: 1
Date: Fri, 04 May 2012 05:04:37 +0000
From: clisp-cvs-request< at >lists.sourceforge.net
Subject: clisp: update berkeley-db to 5.1
To: clisp-cvs< at >lists.sourceforge.net
Message-ID:
<hg.3d1765c46a62.1336107877.-3352671374714820773< at >vz-hg-2.sog>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.so

clisp-cvs Digest, Vol 69, Issue 6

2012-04-28T12:05:01

Send clisp-cvs mailing list submissions to
clisp-cvs< at >lists.sourceforge.net

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
clisp-cvs-request< at >lists.sourceforge.net

You can reach the person managing the list at
clisp-cvs-owner< at >lists.sourceforge.net

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: Fix bug#3467762: symlink to directory handling
      (clisp-cvs-request< at >lists.sourceforge.net)


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

Message: 1
Date: Fri, 27 Apr 2012 19:29:03 +0000
From: clisp-cvs-request< at >lists.sourceforge.net
Subject: clisp: Fix bug#3467762: symlink to directory handling
To: clisp-cvs< at >lists.sourceforge.net
Message-ID:
<hg.c88260c2da71.1335554943.-3352671374714820773< at >vz-hg-3.sog>
Content-Type: text/plain; charset

[ clisp-Bugs-3521402 ] ffcall-1.10 (or CVS head) fails to buildx86_64 on OS X

SourceForge.net — 2012-04-27T22:10:55

Bugs item #3521402, was opened at 2012-04-25 11:26
Message generated for change (Settings changed) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3521402&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: ffcall
Group: build problems
Priority: 5
Private: No
Submitted By: Hanspeter Niederstrasser (nieder)
Assigned to: Bruno Haible (haible)
Summary: ffcall-1.10 (or CVS head) fails to build x86_64 on OS X

Initial Comment:
On OS X 10.6 (and 10.7) which builds as 64bit by default, ffcall fails to build with the following error:

./configure --host=x86_64-apple-darwin10 (explicit --host is needed or it misidentifies as a 32 bit and that also fails in a 64bit environment [1] )
...
cd avcall; make all
/bin/sh ./libtool --mode=compile gcc -x none -c ./avcall-x86_64.s
gcc -x none -c ./avcall-x86_64.s -o avcall-x86_64.o
avcall-

[ clisp-Bugs-3521402 ] ffcall-1.10 (or CVS head) fails to buildx86_64 on OS X

SourceForge.net — 2012-04-27T21:03:21

Bugs item #3521402, was opened at 2012-04-25 11:26
Message generated for change (Comment added) made by nieder
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3521402&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: ffcall
Group: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hanspeter Niederstrasser (nieder)
Assigned to: Bruno Haible (haible)
Summary: ffcall-1.10 (or CVS head) fails to build x86_64 on OS X

Initial Comment:
On OS X 10.6 (and 10.7) which builds as 64bit by default, ffcall fails to build with the following error:

./configure --host=x86_64-apple-darwin10 (explicit --host is needed or it misidentifies as a 32 bit and that also fails in a 64bit environment [1] )
...
cd avcall; make all
/bin/sh ./libtool --mode=compile gcc -x none -c ./avcall-x86_64.s
gcc -x none -c ./avcall-x86_6

[ clisp-Bugs-3467762 ] delete-file cannot delete directory symlink

SourceForge.net — 2012-04-27T19:30:59

Bugs item #3467762, was opened at 2011-12-30 18:52
Message generated for change (Settings changed) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3467762&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: lisp error
Priority: 5
Private: No
Submitted By: Gabor Balazs (gabalz)
Summary: delete-file cannot delete directory symlink

Initial Comment:

The delete-file function can remove file and dead symlinks but not (alive) directory symlinks, because it always resolves the provided pathname in the directory symlink case even if it should not (according to the CLISP documentation) :

    "(DELETE-FILE pathname) deletes the pathname PATHNAME, not its TRUENAME, ..."

Problem reconstruction:
~~~~~~~~~~~~~~~~~~

ls -lR
drwxr-xr-x 2 bege users 4096 Dec 30 19:40 dir
-rw-r--r-- 1 bege users    0 Dec 30 19:26 file
lrw

[ clisp-Bugs-3521402 ] ffcall-1.10 (or CVS head) fails to buildx86_64 on OS X

SourceForge.net — 2012-04-27T17:51:06

Bugs item #3521402, was opened at 2012-04-25 11:26
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3521402&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: ffcall
Group: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hanspeter Niederstrasser (nieder)
Assigned to: Bruno Haible (haible)
Summary: ffcall-1.10 (or CVS head) fails to build x86_64 on OS X

Initial Comment:
On OS X 10.6 (and 10.7) which builds as 64bit by default, ffcall fails to build with the following error:

./configure --host=x86_64-apple-darwin10 (explicit --host is needed or it misidentifies as a 32 bit and that also fails in a 64bit environment [1] )
...
cd avcall; make all
/bin/sh ./libtool --mode=compile gcc -x none -c ./avcall-x86_64.s
gcc -x none -c ./avcall-x86_64.s

[ clisp-Bugs-3521402 ] ffcall-1.10 (or CVS head) fails to buildx86_64 on OS X

SourceForge.net — 2012-04-27T17:50:46

Bugs item #3521402, was opened at 2012-04-25 11:26
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3521402&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: ffcall
Group: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hanspeter Niederstrasser (nieder)
Assigned to: Bruno Haible (haible)
Summary: ffcall-1.10 (or CVS head) fails to build x86_64 on OS X

Initial Comment:
On OS X 10.6 (and 10.7) which builds as 64bit by default, ffcall fails to build with the following error:

./configure --host=x86_64-apple-darwin10 (explicit --host is needed or it misidentifies as a 32 bit and that also fails in a 64bit environment [1] )
...
cd avcall; make all
/bin/sh ./libtool --mode=compile gcc -x none -c ./avcall-x86_64.s
gcc -x none -c ./avcall-x86_64.s

A few newbie questions

Yves S. Garret — 2012-04-25T21:04:33

Hi all,

   Still learning about Lisp and I have a few questions.


   1. Are there any differences between CLISP and Clozure?  If so, how
   substantial are they?  Which one would be a good place to start for someone
   new?
   2. Say I have a file hello_world.lisp.  In that file I have the function
   print.  How do I execute that function from the command line?  $ clisp
   hello_world:print ?


I'd appreciate your help.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________
clisp-devel mailing list
clisp-devel< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clisp-devel

[ clisp-Bugs-3521402 ] ffcall-1.10 (or CVS head) fails to buildx86_64 on OS X

SourceForge.net — 2012-04-25T18:26:38

Bugs item #3521402, was opened at 2012-04-25 11:26
Message generated for change (Tracker Item Submitted) made by nieder
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3521402&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: ffcall
Group: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hanspeter Niederstrasser (nieder)
Assigned to: Bruno Haible (haible)
Summary: ffcall-1.10 (or CVS head) fails to build x86_64 on OS X

Initial Comment:
On OS X 10.6 (and 10.7) which builds as 64bit by default, ffcall fails to build with the following error:

./configure --host=x86_64-apple-darwin10 (explicit --host is needed or it misidentifies as a 32 bit and that also fails in a 64bit environment [1] )
...
cd avcall; make all
/bin/sh ./libtool --mode=compile gcc -x none -c ./avcall-x86_64.s
gcc -x none -c ./avc

clisp-cvs Digest, Vol 69, Issue 5

2012-04-25T12:06:06

Send clisp-cvs mailing list submissions to
clisp-cvs< at >lists.sourceforge.net

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
clisp-cvs-request< at >lists.sourceforge.net

You can reach the person managing the list at
clisp-cvs-owner< at >lists.sourceforge.net

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: setq->defparameter
      (clisp-cvs-request< at >lists.sourceforge.net)


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

Message: 1
Date: Tue, 24 Apr 2012 15:07:37 +0000
From: clisp-cvs-request< at >lists.sourceforge.net
Subject: clisp: setq->defparameter
To: clisp-cvs< at >lists.sourceforge.net
Message-ID:
<hg.9c27cf4b8349.1335280057.-3352671374714820773< at >vz-hg-3.sog>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/

[ clisp-Bugs-3521153 ] mt: module/linux error

SourceForge.net — 2012-04-25T11:15:48

Bugs item #3521153, was opened at 2012-04-24 12:59
Message generated for change (Comment added) made by vtz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3521153&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: multithreading
Group: lisp error
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Sam Steingold (sds)
Assigned to: Vladimir Tzankov (vtz)
Summary: mt: module/linux error

Initial Comment:
$ make full-mod-check MODULES=bindings/glibc
...


(DEFPARAMETER *SIGACT* (SHOW (LINUX:signal-action-retrieve LINUX:SIGINT)))
#S(LINUX:sigaction :SA_HANDLER NIL :SA_MASK #S(LINUX:sigset_t :VAL #()) :SA_FLAGS 0 :SA_RESTORER #<FOREIGN-ADDRESS #x00002AB7D29E4420>)
EQL-OK: *SIGACT*
(DEFPARAMETER *SAVEHANDLER* (LINUX:sa-handler *SIGACT*))
EQL-OK: *SAVEHANDLER*
(DEFPARAMETER *SIGNALS* NIL)
EQL-OK: *SIGNALS*
(DEFUN TEST-HAN

[ clisp-Bugs-3514029 ] clisp does not build on OSX (Macports)

SourceForge.net — 2012-04-25T05:59:48

Bugs item #3514029, was opened at 2012-04-01 21:40
Message generated for change (Comment added) made by cstacy
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3514029&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: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Christopher Stacy (cstacy)
Assigned to: Bruno Haible (haible)
Summary: clisp does not build on OSX (Macports)

Initial Comment:
Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386 i386

System Version: Mac OS X 10.6.8 (10K549)
Kernel Version: Darwin 10.8.0
Secure Virtual Memory:  Enabled
64-bit Kernel and Extensions: No

Model Name:   Mac mini
Model Identifier:     Macmini3,1
Processor Name:       Intel Core 2 Duo
Processor Speed:      2.26 GHz
Number Of Processors: 1
Total Number