Code

Programming Languages: Lisp, C, Assembly

License: GNU General Public License version 2.0 (GPLv2)

Repositories

browse code, statistics, last commit on 2012-05-03 http://clisp.hg.sourceforge.net:8000/hgroot/clisp/clisp (read-only)

Show:

What's happening?

  • Comment: Format specifier patch

    this patch results in these warnings on amd64: In file included from ../src/spvw.d:161:0: ../src/spvw_debug.d: In function ‘nobject_out1’: ../src/spvw_debug.d:123:5: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘uintWL’ [-Wformat] ../src/spvw_debug.d:124:5: warning: format ‘%lu’ expects argument of type ‘long unsigned...

    2012-05-24 18:37:08 PDT by sds

  • ARM fixes

    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...

    2012-05-24 16:02:28 PDT by jjames

  • Format specifier patch

    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.

    2012-05-24 15:52:21 PDT by jjames

  • Comment: CLISP treats CL:REQUIRE specially at compile time

    Well, duh, I now see this is documented in the manual. However, this causes a problem for a real program that does (ignore-errors (require 'asdf)) in an attempt to load the "system" ASDF if it is available. Since REQUIRE is eagerly evaluated at compile time, the error isn't ignored as it should be. Any suggestions?.

    2012-05-10 05:51:53 PDT by xach

  • CLISP treats CL:REQUIRE specially at compile time

    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.

    2012-05-10 05:48:33 PDT by xach

  • Comment: ANSI CL forbids mixed-type complex numbers

    http://www.cygwin.com/acronyms/#PTC.

    2012-05-07 07:40:14 PDT by sds

  • Comment: ANSI CL forbids mixed-type complex numbers

    I agree that it is documented, but deny that it is a valid ANSI CL extension. Section 1.6 of the CLHS says: "An implementation can have extensions, provided they do not alter the behavior of conforming code and provided they are not explicitly prohibited by this standard." But (integerp (realpart (complex 1 2.0))) is conforming code, and the standard requires that it return NIL due...

    2012-05-07 07:11:01 PDT by johnwcowan

  • Comment: ANSI CL forbids mixed-type complex numbers

    This bug report is now marked as "pending"/"invalid". This means that we think that the problem you report is not a problem with CLISP. Unless you - the reporter - act within 2 weeks, the bug will be permanently closed. Sorry about the inconvenience - we hope your silence means that you agree that this is not a bug in CLISP.

    2012-05-07 06:51:50 PDT by sds

  • Comment: ANSI CL forbids mixed-type complex numbers

    This is a documented feature, not a bug: http://www.clisp.org/impnotes.html#complex-comp.

    2012-05-07 04:42:42 PDT by haible

  • ANSI CL forbids mixed-type complex numbers

    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...

    2012-05-06 22:38:39 PDT by johnwcowan

Our Numbers