gmane.lisp.clisp.general

"Readable" library for Common Lisp now available!

David A. Wheeler — 2013-05-15T12:50:21

(I posted a longer version of this on comp.lang.lisp, but I suspect not everyone saw it there.)

FYI:

I've just released a Common Lisp library called "readable".
It adds a new abbreviations to the Common Lisp reader for data and programs
(by modifying the readtable).

It provides 3 notational tiers, which are cumulative. Here's a summary:
1. Curly-infix-expressions (c-expressions): Add a Lispy infix notation, so
   {a op b op c ...} => (op a b c...).  No precedence, by intent.
2. Neoteric-expressions (n-expressions): An e(...) maps to (e ...),
   and e{...} maps to e({...}).
3. Sweet-expressions (t-expressions): Parentheses are
   deduced from indentation.

Unlike practically all past efforts to improve Lisp readability
(such as M-expressions), these notations are general, homoiconic,
and backwards-compatible with well-formatted s-expressions.
Macros, quasiquoting, special forms, and so on work just fine.
You can mix them with traditional s-expression notation, too.

You can get the Common Lisp tutorial (wh

ASDF 3.0.0

Faré — 2013-05-15T05:06:30

Dear CLISP hackers,

I'm proud to announce the release of release ASDF 3.0.0.
Please test it and include it in CLISP.
(And thanks for previously upgrading to 2.33; it was a much needed update.)

I'll have to produce some document explaining the innovations since
ASDF 2.26, 2.000 and/or 1.369, but for now here are just the changes
since 2.33.

As you can see, it's very minor stuff, and ASDF has been mostly stable
these last two months, which is a good sign and the reason why I'm
making an official 3.0.0 release.

I'm also inserting a new digit in the version, so releases will have
three digits:
3.0.0, 3.0.1, etc. will be minor continuations of 3.0. 3.1.0 will be
the next "major"
milestone in a series that preserves backward compatibility, and 4.0 (if ever)
will be the next major release that doesn't.
But I probably won't be there to see it, because I'm moving away from
my Common Lisp job in Cambridge MA
to some new as yet undetermined opportunities in NYC that
are unlikely to see me do Common Lisp for a livin

xlib:window-map-state error in stumpwm

z_axis — 2013-05-09T05:34:27

Lisp: "CLISP" "2.49 (2010-07-07) (built 3558763409) (memory 3576884804)"

#<PACKAGE STUMPWM>
STUMPWM> (current-screen)
#S<screen #<XLIB:SCREEN :0.0 1440x900x24 TRUE-COLOR>>
STUMPWM> (screen-message-window (current-screen))
#<XLIB:WINDOW :0 400004>
STUMPWM> (xlib:window-map-state (screen-message-window (current-screen)))
; Evaluation aborted on #<SIMPLE-ERROR #x3AB2080D>.
STUMPWM>

Program tried to wait with no scheduler.
    [Condition of type SIMPLE-ERROR]

Restarts:
  0: [RETRY] Retry SLIME REPL evaluation request.
  1: [*ABORT] Return to SLIME's top level.
...

Both sbcl and ccl works without any problem.


Sincerely!


------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neot

Re: How can I override readtable capital letters and avoid |barring-all-symbols| ?

David A. Wheeler — 2013-05-07T03:41:13

Pascal J. Bourguignon:

That's not sufficient control for my purposes.

My goal is to bind the readtable and have it *STAY* that way.  Even during the REPL, even after it returns a value, and so on.  (Another approach would be to have a way to replace "read", though that would not be portable.)

--- David A. Wheeler

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and 
their applications. This 200-page book is written by three acclaimed 
leaders in the field. The early access version is available now. 
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
clisp-list mailing list
clisp-list< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clisp-list

Re: How can I override readtable capital letters andavoid |barring-all-symbols| ?

Pascal J. Bourguignon — 2013-05-07T03:16:50


No.  As I demonstrated, you can already control it, binding *readtable*
when it matters to you.

Re: How can I override readtable capital letters and avoid |barring-all-symbols| ?

David A. Wheeler — 2013-05-07T00:57:56

I asked:

"Pascal J. Bourguignon" <pjb< at >informatimago.com> wrote: 

Okay, I've looked through the clisp code and I found the problem.
The issue is in file "src/io.d" function "pr_symbol_part"
(which starts line 7004 on 2013-05-06), with this code.
It forces |...| around symbols based on what happens to be in the current readtable:

======================================================
    var object syntax_table; /* syntaxcode-table, with char_code_limit elements */
    var uintW rtcase;        /* readtable-case */
    {
      var object readtable;
      get_readtable(readtable = ); /* current Readtable */
      syntax_table = TheReadtable(readtable)->readtable_syntax_table;
      rtcase = RTCase(readtable);
    }
    /* traverse string: */
    SstringDispatch(string,X, {
...
      if (!(syntax_table_get(syntax_table,c) == syntax_constituent))
        goto surround;          /* no -> must use |...| */
======================================================



Would the clisp folks be willing to entertain a tw

Re: How can I override readtable capital letters andavoid |barring-all-symbols| ?

Pascal J. Bourguignon — 2013-05-06T13:33:27


Yes.  That is the suggestion in my new answer.



I don't know.  One would have to have a look at the sources.

Re: How can I override readtable capital letters andavoid |barring-all-symbols| ?

Pascal J. Bourguignon — 2013-05-06T13:32:13


But they are needed!  Since you put a reader macro on #\A, the printer
cannot assume that ABC will be read as the symbol ABC.  The printer has
to print a symbol named "ABC" so that it is read back as the symbol
named "ABC".  With an overriden reader macro, it has to escape it.


I won't comment on sbcl here…



You could revert to a natural *readtable* when printing.




(defvar *original-readtable* (copy-readtable))
(defvar *ugly-readtable*     (copy-readtable))

(defun ugly (stream char)
  (unread-char char stream)
  (let ((*readtable* *original-readtable*))
    (read-preserving-whitespace stream)))

(dolist (c '(#\! #\$ #\% #\& #\* #\+ #\- #\. #\/
             #\A))
  (set-macro-character c #'ugly t *ugly-readtable*))



;; reading using the ugly readtable by default:

[5]> (setf *readtable* *ugly-readtable*)
#<READTABLE #x0003343FD4F8>
[6]> (read-from-string "abc")
|ABC| ;
3


;; reading by explicitely specifying the ugly readtable, using the
;; standard or original readtable by default:

[7]> (setf

Re: How can I override readtable capital letters and avoid |barring-all-symbols| ?

David A. Wheeler — 2013-05-06T04:41:50

Your previous email gave me a useful hint, thanks.   It appears that the behavior of clisp's WRITE is affected by the currently-active readtable.  If I read in stuff, then switch to the traditional readtable, the extra vertical bars are no longer displayed by clisp.

So... is there a way to disable that clisp feature of adding |...| when the readtable is different?

--- David A. Wheeler

------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
clisp-list mailing list
clisp-list< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clisp-list

Re: How can I override readtable capital letters and avoid |barring-all-symbols| ?

David A. Wheeler — 2013-05-06T04:28:20

Pascal J. Bourguignon:


Thanks very much for the response!

Sadly, that's not what I want.   If I then (without "-modern") read |abc|, the printer will print abc *WITHOUT* the vertical bars.  The problem is that then, when I read it back in later, it will no longer really be |abc| but be ABC... not the same.

I *want* clisp to print vertical bars when they are needed... but only when they are needed.  Sbcl does this, and clisp normally does this.  Some special mode or flag setting seems to happen when clisp reads through a capital later constituent if that letter has had its readtable set-macro-character.



Already have; this seems to be clisp-unique behavior.

...

I appreciate the note that it's easier to just catch {...},
but I really want to catch all text, from the outset, even if it's trickier.

Also, a clarification:  My goal isn't to translate Scheme to Common Lisp,
it's to create a variant of s-expression notation where (for example)
indentation implies parentheses.
If someone wants "defun", they'

Re: How can I override readtable capital letters andavoid |barring-all-symbols| ?

Pascal J. Bourguignon — 2013-05-05T04:21:03


Bouahahahaha, bouahahaha, bouahahahaha!


Well, at least you'll learn about CL reader macros.




That's because you have *print-escape* set to true.  


Try:

   (setf *print-escape* nil)

and of course:

  (setf *print-readably* nil)

but if that wasn't the case, you'd get:

  |COMMON-LISP-USER|::|ABC|



Well, we could, but perhaps it'd be better if you just read the printer
chapter of CLHS (along with the syntax chapter and the reader chapter).



No, it's totally unrelated to the modern mode.  It's just one
interpretation of the CLHS.




While it's possible to hack the lisp reader by making a lot of reader
macros, for your purpose it's probably much simplier to have a single
reader macro, and to write a normal parser.  Since you seem to like
braces, you could write a #\{ reader macro that would read up to the
next balanced #\}, and parse the content with a normal scanner and
parser, returning the sexp you want.

See for example:
http://groups.google.com/group/comp.lang.lisp/browse_frm/thread/24534242

How can I override readtable capital letters and avoid |barring-all-symbols| ?

David A. Wheeler — 2013-05-05T03:27:58

Can anyone suggest help/insight involving clisp's readtable when capital letters are overridden?

I'm implementing some extensions to the Common Lisp reader that, I hope, is more readable.  My implementation works in clisp, but there's an oddity that I hope someone here can answer.

Basically, when in clisp I override the readtable's *capital* letters, all the produced symbols are later written with vertical bars.  I don't want that, and sbcl doesn't do this.

Is there a way to prevent this behavior?  Or at least, can someone who's more familiar with clisp's implementation explain what's going on and why?  I presume this involves the "modern" mechanisms, which I'm happy to support, but no matter what happens the vertical-bars seem to be forced.

One reason I'm doing this is because I want "f(a b c)" to be interpreted as "(f a b c)" in my reader.  If you're curious about the details, please check us out at readable.sourceforge.net.

--- David A. Wheeler

P.S. Here's sample code that demonstrates this:

======

Re: Can't compile clisp on ubuntu LTS

Faré — 2013-04-14T20:16:40

By removing ubuntu's libffcall1-dev, and following the instructions
provided by clisp to compile libffcall from cvs, I could compile a
working clisp. However, when I try to (require "linux"), it fails
with:
[1]> (require "linux")
;; Loading file /home/tunes/local/lib/clisp-2.49+/dynmod/linux.lisp ...
;;  Loading module linux from
/home/tunes/local/lib/clisp-2.49+/dynmod/lib-linux.so
*** - SYSTEM::DYNLOAD-MODULES: "dlopen" ->
      "/home/tunes/local/lib/clisp-2.49+/dynmod/lib-linux.so:
undefined symbol: rpl_ioctl"
I see that rpl_ioctl is a replacement for ioctl provided by
src/gllib/ioctl.c:rpl_ioctl (int fd, int request, ... /* {void *,char *} arg */)
src/gllib/sys_ioctl.in.h:#   define ioctl rpl_ioctl
but it looks like something is inconsistent in the clisp build so that
it's compiled into the linux module but not exported by the lisp.run
executable, or something.

Incidentally, I was trying to use fork, which is exported by the linux
module but not the posix builtin package.

—♯ƒ • François-René

Can't compile clisp on ubuntu LTS

Faré — 2013-04-14T19:31:42

Using Ubuntu 12.04.02LTS, and trying to compile a hg clone
http://clisp.hg.sourceforge.net:8000/hgroot/clisp/clisp
with

#!/bin/zsh -f
A=(
./configure
--with-ffcall --with-libffcall-prefix=/usr
--with-readline # --with-libreadline-prefix=/usr
--with-sigsegv # --with-libsigsegv-prefix=/usr
--with-module=bindings/glibc
--with-module=asdf
--with-module=clx/new-clx
--with-module=dbus
--with-module=readline
--with-module=regexp
--with-module=rawsock
--with-module=syscalls
--with-module=i18n
--with-module=zlib
--cbc build-dir
--prefix=/home/tunes/local
)
$A

It compiles a whole lot of stuff, then reproducibly dies during ffi tests with:
(PROGN (DEF-CALL-OUT C-SELF (:NAME "ffi_identity") (:ARGUMENTS (OBJ
(C-PTR (C-ARRAY-MAX SINT16 17)) :OUT)) (:RETURN-TYPE NIL) (:LANGUAGE
:STDC)) (C-SELF))
EQUALP-OK: #()
(WITH-FOREIGN-OBJECT (FV 'LONG -12345678) (TYPEP FV 'FOREIGN-VARIABLE))
EQL-OK: T
(PROGN (DEFPARAMETER *X* 0) (DEFUN CALLBACK (X) (SETF *X* (THE
(UNSIGNED-BYTE 16) X)) (THE (UNSIGNED-BYTE 16) (1+ (* 2 X)))) *X*)
EQ

CLISP-threaded is the best implementation to buildstumpwm

z_axis — 2013-04-12T02:43:21

Now i am using stumpwm built with clisp-threaded everyday.


Thanks for such a great CL implementation.


Best Regards!


------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
clisp-list mailing list
clisp-list< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clisp-list

Program tried to wait with no scheduler ...

z_axis — 2013-03-24T02:41:42

This is a small problem which i cannot understand. The stumpwm built using  
CCL and SBCL works well. However, the CLISP built stumpwm always canot  
disppear the message window automatically.

By debugging, I found an error is throwed by (xlib:window-map-state  
(screen-message-window (current-screen))) before #'unmap-message-window.  
which reports:"Program tried to wait with no scheduler ..."
so that it doesnot ummap the messge window.


Any suggestion is appreciated!


------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
clisp-list mailing list
clisp-list< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clisp-list

Re: [BUG?] Complex numbers transtyping

Didier Verna — 2013-03-20T16:57:04


  Thank you.

Re: [BUG?] Complex numbers transtyping

Sam Steingold — 2013-03-20T16:40:34

this non-conformance is documented
http://www.clisp.org/impnotes/num-concepts.html#complex-comp
http://www.clisp.org/impnotes/num-concepts.html#complex-rational

[BUG?] Complex numbers transtyping

Didier Verna — 2013-03-20T14:18:06

  Hello,

this is with a recent build of CLisp from the HG repository:

2.49+ (2010-07-17) (built 3572776794) (memory 3572776868)


It seems to me that the behavior of complex numbers with floating real
parts is not conformant, but maybe my interpretation of the standard is
too rigid. At least, some examples don't behave as in section 12.1.5.3.1
of CLHS, and differ from at least 5 other CL implementations. For
instance:

#c(1.0 1) => #C(1.0 1) ;; expected #C(1.0 1.0)
#c(0.0 0) => 0.0       ;; expected #C(0.0 0.0)


Comments ?

Re: socket-connect error

Sam Steingold — 2013-03-13T14:22:34

no, alas, this means that the bug is present in 2.49 too and will be
fixed in 2.50 when that is released.
your best option is to build clisp yourself from hg tip.

Re: socket-connect error

Mirko Vukovic — 2013-03-12T15:16:01

Does this mean that the bug is present in 2.48 (I don't have 2.49 on
cygwin), and will
be fixed in the next release?

Mirko

------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
clisp-list mailing list
clisp-list< at >lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/clisp-list