May 2009 - cells-devel - mailman3.common-lisp.net

[cells-devel] A few patches for making cells (3.0 from cvs) run on debian unstable using sbcl.
by Peder Chr. Nørgaard 14 Dec '09

14 Dec '09

Hello cells-devel list. I am investigating cells and cells-gtk3 for a project that I am planning. For a starter, I needed to get the software running on my Debian unstable system. It needed a few patches that you may wish to take into your development. The version of cells that I use is taken with cvs -z3 -d :pserver:anonymous:anonymous@common-lisp.net:/project/cells/cvsroot co cells That is the most actual one, yes? Well, the sbcl on Debian unstable (1.0.18) does not have nor need the EXCL package. So it must be configured out: diff -u -r cells/defpackage.lisp cl/cells/defpackage.lisp --- cells/defpackage.lisp 2008-10-12 03:21:07.000000000 +0200 +++ MDM/cl/cells/defpackage.lisp 2008-11-28 20:08:38.000000000 +0100 @@ -23,7 +23,7 @@ (in-package :common-lisp-user) (defpackage :cells - (:use #:common-lisp #:excl #:utils-kt) + (:use #:common-lisp #-sbcl #:excl #:utils-kt) (:import-from ;; MOP #+allegro #:excl diff -u -r cells/utils-kt/defpackage.lisp cl/cells/utils-kt/defpackage.lisp --- cells/utils-kt/defpackage.lisp 2008-10-12 03:21:10.000000000 +0200 +++ MDM/cl/cells/utils-kt/defpackage.lisp 2008-11-28 20:04:08.000000000 +0100 @@ -35,7 +35,8 @@ (defpackage :utils-kt (:nicknames #:ukt) - (:use #:common-lisp #:excl + (:use #:common-lisp + #-sbcl #:excl #+(or allegro lispworks clisp) #:clos #+cmu #:mop #+sbcl #:sb-mop The sbcl does not have the MOP package - it is called SB-MOP. Much of the code knows that already, but I had to patch one file: diff -u -r cells/utils-kt/detritus.lisp cl/cells/utils-kt/detritus.lisp --- cells/utils-kt/detritus.lisp 2008-10-12 03:21:10.000000000 +0200 +++ MDM/cl/cells/utils-kt/detritus.lisp 2008-11-28 20:07:57.000000000 +0100 @@ -33,7 +33,7 @@ (let ((cc (find-class c))) (when cc (finalize-inheritance cc)) - (mop::class-prototype cc))) + (#+sbcl sb-mop:class-prototype #-sbcl mop::class-prototype cc))) (defun brk (&rest args) After that, I tried to run the test suite. Worked fine, except that it is a little bit too Window'ish. I did this: diff -u -r cells/cells-test/test.lisp cl/cells/cells-test/test.lisp --- cells/cells-test/test.lisp 2008-10-12 03:21:09.000000000 +0200 +++ MDM/cl/cells/cells-test/test.lisp 2008-12-01 22:25:26.000000000 +0100 @@ -69,7 +69,7 @@ (defun test-cells () - (dribble "c:/0algebra/cells-test.txt") + (dribble "/tmp/cells-test.txt") (progn ;prof:with-profiling (:type :time) (time (progn but that is not what you want to go in the main sources. Maybe something based on the features - (dribble #+unix "/tmp/cells-test.txt" #-unix "c:/0algebra/cells-test.txt") - or perhaps just a file name parameter to TEST-CELLS with the above as the default value? Hope this is of a little help to you. I am sure to come back for assistance for my project later. best regards -- Peder Chr. Nørgaard e-mail: pcn(a)pogt.dk Gefionsvej 19 DK-8230 Åbyhøj tel: +45 87 44 11 99 Denmark mob: +45 30 91 84 31

6 5

[cells-devel] Fwd: Cells on ABCL
by Alessio Stalla 04 Jun '09

04 Jun '09

Sorry, I sent this directly to Kenny instead of to the mailing list. Alessio ---------- Forwarded message ---------- From: Alessio Stalla <alessiostalla(a)gmail.com> Date: Tue, May 26, 2009 at 10:53 PM Subject: Re: [cells-devel] Cells on ABCL To: Kenneth Tilton <kentilton(a)gmail.com> On Tue, May 26, 2009 at 2:17 PM, Kenneth Tilton <kentilton(a)gmail.com> wrote: > Does ABCL provide a backtrace that might show in which function the error > originates? abcl's backtrace does not seem very useful: [1] CL-USER(8): :bt 0: (BACKTRACE-AS-LIST) 1: (INVOKE-DEBUGGER #<TYPE-ERROR {7F84C9}>) 2: (CELLS::CV-TEST-PERSON-3) 3: (CELLS::CV-TEST-PERSON) 4: (FUNCALL CELLS::CV-TEST-PERSON) 5: (SYSTEM::%TIME #<FUNCTION (LAMBDA ()) {1E6DBAA}>) 6: (CELLS::TEST-CELLS) 7: (SYSTEM::%EVAL (CELLS::TEST-CELLS)) > Also: IIRC, ct-assert says what it is doing as it goes. So how far are you > getting? If I am wrong on that, just add some print statements so we can > narrow it down. This is what it prints before it fails: (CELLS::ATTEMPTING (EQL 1 (LENGTH (CELLS::CD-USEDS (CELLS::MD-SLOT-CELL CELLS::P (QUOTE CELLS::THOUGHT)))))) 0> output thought #<cells::person {15eb44d}> "speedy, slow down!"0> i am thinking "speedy, slow down!" (CELLS::ATTEMPTING (EQL 2 (LENGTH (CELLS::CD-USEDS (CELLS::MD-SLOT-CELL CELLS::P (QUOTE CELLS::THOUGHT)))))) 0> output thought #<cells::person {15eb44d}> "nice and easy does it"0> i am thinking "nice and easy does it" (CELLS::ATTEMPTING (EQL 1 (LENGTH (CELLS::CD-USEDS (CELLS::MD-SLOT-CELL CELLS::P (QUOTE CELLS::THOUGHT)))))) Debugger invoked on condition of type TYPE-ERROR: The value NIL is not of type STRUCTURE-OBJECT. Probably it's an abcl bug (I've seen other times bugs that were apparent in the form of "NIL is not of type X"). In the next few days I'll be at the ELS, so I won't have much time to spend on the subject, but asap I'll try to debug it. Bye, Alessio

3 3

[cells-devel] Cells on ABCL
by Alessio Stalla 26 May '09

26 May '09

Has anyone got Cells to work on ABCL? I've tried briefly (with Cells from CVS) and, with a couple minor modifications to it and to abcl, I got it to compile and load (despite the fact that CLOS & MOP are probably abcl's weakest point). Then I've tried to run the tests, but the last form in cv-test-person-3 makes it choke with: Debugger invoked on condition of type TYPE-ERROR: The value NIL is not of type STRUCTURE-OBJECT. Still, I've only spent a hour or so on this so far, and I'm pleased with the results. If anyone is interested, I'll keep you informed on my progress. Cheers, Alessio Stalla

2 1

[cells-devel] Celtk: Double click not being sent to Cello
by Frank Goenninger 24 May '09

24 May '09

Hi - I have: (eval-when (:compile-toplevel :load-toplevel :execute) (defparameter *tcl-bindings* nil) (defun make-binding (tcl-event tcl-command-string) (let ((tcl-binding (conc$ "bind . " tcl-event " " tcl-command- string))) (pushnew tcl-binding *tcl-bindings*)))) (defun apply-bindings (&optional (bindings *tcl-bindings*)) (loop for binding in bindings do (format *debug-io* "Celtk: Applying binding ~S.~%" binding) (tk-format-now binding))) (defmacro defbinding (tcl-event tcl-command-string) `(eval-when (:compile-toplevel :load-toplevel :execute) (make-binding ,tcl-event ,tcl-command-string))) (defmacro define-binding-and-command (command tcl-event tcl-command- string) `(progn (defcommand ,command) (defbinding ,tcl-event ,tcl-command-string))) (define-binding-and-command double-click-1 "<Double-ButtonPress-1>" "{do-double-click-1 %W %K; break}") (define-binding-and-command double-click-2 "<Double-ButtonPress-2>" "{do-double-click-2 %W %K; break}") (define-binding-and-command double-click-3 "<Double-ButtonPress-3>" "{do-double-click-3 %W %K; break}") and have extended #'run-window to call #'apply-bindings. Trace output shows that the bindings are actually executed as expected. I also extended class tk-object to have appropriate slots: (defmodel tk-object (model) ((.md-name :cell nil :initform (gentemp "TK") :initarg :id) (tk-class :cell nil :initform nil :initarg :tk-class :reader tk- class) (timers :owning t :initarg :timers :accessor timers :initform nil) (on-command :initarg :on-command :accessor on-command :initform nil) (on-key-down :initarg :on-key-down :accessor on-key-down :initform nil :documentation "Long story. Tcl C API weak for keypress events. This gets dispatched eventually thanks to DEFCOMMAND") (on-key-up :initarg :on-key-up :accessor on-key-up :initform nil) (on-double-click-1 :initarg :on-double-click-1 :accessor on-double- click-1 :initform nil) ;; <<< --- here (on-double-click-2 :initarg :on-double-click-2 :accessor on-double- click-2 :initform nil) ;; <<< --- and here (on-double-click-3 :initarg :on-double-click-3 :accessor on-double- click-3 :initform nil) ;; <<< --- and here (user-errors :initarg :user-errors :accessor user-errors :initform nil) (tile? :initform t :cell nil :reader tile? :initarg :tile?)) (:documentation "Root class for widgets and (canvas) items")) From the code I am reading that if any of the slots on-double- click-1 ... is assigned a function this function gets called as soon as a double-click-n is received... Yet Celtk always delivers a normal ButtonPress event ... Do I need to extend #'widget-event-handle of Celtk to make this work? Kenny, did this ever work for you? Any ideas ? Thx! Best, Frank -- Frank Goenninger Cell: +49 175 4321058 E-Mail: frgo(a)me.com

1 0

Re: [cells-devel] A thing that does not work well with Cells... SOLVED! well, kind of...
by Peder Chr. Nørgaard 22 May '09

22 May '09

Hello Jakub, Kenny Jakub beat me into making the PRINT-OBJECT method more robust. Nevertheless: my problem - whatever it is - has disappeared. I am not all that comfortable leaving behind me a problem (in SBCL or CELLS) that I don't understand. But at least this solution of Jakub's cannot possible have any negative side effects. I still don't have a clue what the basic problem is - I have spent a few hours today trying to get the modified PRINT-OBJECT method print something or enter the debugger - no such luck. I never see the output of the code snippet "(format s \"UNINITIALIZED-~a\" (type-of self)". It seems that when the method is recoded to be more robust, it stops being invoked. You confused? I am! At any rate, thanks for the support, I can now get on with my project. Kenny, you might wish to enter this small modification in the main Cells CVS source. Jakub, you write "Perhaps I do not understand your problem". I have been amiss explaining the manifestation of the problem. It comes here: with the origical Cells code, the first time I access - SETF or not - the PROTOTYPE slot af a newly defined PCL-CLASS - if the class in question is a model - the access fails. The access should trigger an allocation of the prototype object. The failure - whatever it is - is shadowed by the problem with PRINT-OBJECT. But the result is, that the PROTOTYPE slot in the PCL-CLASS object representing the MODEL class - is no longer NIL, it is unbound. But never mind, don't worry about this. Jakub's fix pushes this problem out of the real world, at least for me. best regards --peder chr. On Thursday 21 May 2009, you wrote: > Hello, > > On Thu, May 21, 2009 at 1:08 PM, Peder Chr. Nørgaard <pcn(a)pogt.dk> wrote: > > Modifying the content of the prototype object of a class - which > > is what your proposal does - is too likely to have some devastating side > > effects - now .MD-STATE and .MD-NAME are no longer NIL by default, as > > specified in the definition of MODEL, they are :PROTOTYPE... > > But in the prototype object they are not NIL anyway, but unbound, > which is the problem. As far as I can tell the prototype object is > used mostly for method computation. > > In any case changing relevant print-object method in family.lisp to [I > pushed it to my mostly cosmetic fork of cells at > http://github.com/Ramarren/cells/commit/b808dbd7cceea5573f09a1e02abbfb08e20 >478c7 ] > > (defmethod print-object ((self model) s) > #+shhh (format s "~a" (type-of self)) > (if (and (slot-boundp self '.md-state) > (slot-boundp self '.md-name)) > (format s "~a~a" (if (mdead self) "DEAD!" "") > (or (md-name self) (type-of self))) > (format s "UNINITIALIZED-~a" (type-of self)))) > > seems to work as well. Perhaps I do not understand your problem, what > I do is this (with the change above): > > CL-USER> (defmodel my-model (model) > ((my-class-slot :cell nil :ALLOCATION :CLASS))) > #<STANDARD-CLASS MY-MODEL> > CL-USER> (sb-mop:finalize-inheritance (find-class 'my-model)) > NIL > CL-USER> (setf (slot-value (sb-mop:class-prototype (FIND-CLASS 'my-model)) > 'my-class-slot) 'a-value) > A-VALUE > CL-USER> (slot-value (sb-mop:class-prototype (find-class 'my-model)) > 'my-class-slot) > A-VALUE > > Regards, > Jakub Higersberger -- Peder Chr. Nørgaard e-mail: pcn(a)pogt.dk Gefionsvej 19 DK-8230 Åbyhøj tel: +45 87 44 11 99 Denmark mob: +45 30 91 84 31

1 0

[cells-devel] Cells: Why am I put in the debugger here ?
by Frank Goenninger 21 May '09

21 May '09

Hi ! I have: (defmd color () red green blue alpha foreign-object :md-name (gensym "CELLO-COLOR-") :red (c-in 0) :green (c-in 0) :blue (c-in 0) :alpha (c-in 0) :foreign-object (c? (progn (when (and (^foreign-object) (not (null-pointer-p (^foreign- object)))) (foreign-free (^foreign-object))) (let ((fo (foreign-alloc :float :count 4))) (when (not (null-pointer-p fo)) (progn (setf (mem-aref fo :float 0) (/ (^red) 255.00000000000f0)) (setf (mem-aref fo :float 1) (/ (^green) 255.0000000000f0)) (setf (mem-aref fo :float 2) (/ (^blue) 255.0000000000f0)) (setf (mem-aref fo :float 3) (/ (^alpha) 255.0000000000f0)))))))) So far so good. Compiling this works ok. Now I do: CL-USER> (make-instance 'cnx::color :red 255 :green 128 :blue 0 :alpha 0) A NEW CELLS::C-DEPENDENT struct @ #x10c95502 = <...> 0 Class --------> #<STRUCTURE-CLASS CELLS::C-DEPENDENT> 1 MODEL --------> CELLO-COLOR-12992 2 SLOT-NAME ----> The symbol CNX::FOREIGN-OBJECT 3 VALUE --------> The symbol NIL 4 INPUTP -------> The symbol NIL 5 SYNAPTIC -----> The symbol NIL 6 CALLER-STORE -> (NIL), a proper list with 1 element 7 STATE --------> The symbol :AWAKE 8 VALUE-STATE --> The symbol :UNEVALUATED 9 PULSE --------> fixnum 0 [#x00000000] 10 PULSE-LAST-CHANGED -> fixnum 0 [#x00000000] 11 PULSE-OBSERVED -> fixnum 0 [#x00000000] 12 LAZY ---------> The symbol NIL 13 OPTIMIZE -----> The symbol T 14 DEBUG --------> The symbol NIL 15 MD-INFO ------> The symbol NIL 16 CODE ---------> ((PROGN ...)), a proper list with 1 element 17 RULE ---------> #<Function (:INTERNAL (MOP:CLASS-DEFAULT-INITARGS CNX::COLOR :FOREIGN-OBJECT) 0) @ #x10cb44ca> 18 USEDS --------> The symbol NIL 19 USAGE --------> A simple-bit-vector (16) #*0000000000000000 [Current process: new-repl-thread] [1i] CL-USER(1): The only way out is a :reset - not good. What I am doing wrong ? (This is on AllegroCL 8.1). Thanks for any hints. Frank -- Frank Goenninger Cell: +49 175 4321058 E-Mail: frgo(a)me.com

3 4

[cells-devel] A thing that does not work well with Cells...
by Peder Chr. Nørgaard 21 May '09

21 May '09

Hi, fellow-cell'ers. I have this problem: I am attempting to port an existing bunch of software to Cells - to "cellulize" it. But there is one specific aspect - a "feature" that I am using - that does not work with Cells. I ask for advice. The "existing bunch" has made a habit of using classes with a number of ":allocation :class" slots. We occasionally have to access these slots without having access to an instance of the class; therefore we use the trick of accessing the slot-in-case of "sb-mop:class-prototype <class>". Now this has worked just fine until I start to cellulize the classes. Then it does not work at all. I have spent some time cooking down the problem. The attached file manifests the problem when you run it on an Sbcl system. To answer the most obvious question: no. No, I haven't tried it on CMUCL or any other LISP system capable of supporting Cells. And to the second-most obvious question, also no. No, I don't want to rewrite my current implementation to use some other technique to access class-specific information. My - shall we call it - hope is that someone with an in-deep knowledge of Cells can spot what aspect of SBCL class implementation that Cell fails to respect. I have spent a number of days digging into this, and I must admit failure. I simply cannot figure out why Cells make this otherwise fine working feature of SBCL fail. The failure happens someplace deep down in the PCL instance allocation, where all traces of Cells override ought to have disappeared... The problem seems to be, that when a class defined with DEFMODEL, subclass of MODEL, has a class-allocated slot, the initialization of the SB-PCL:PROTOTYPE slot triggered by the first use of SB-MOP:CLASS-PROTOTYPE - fails. Actually, it fails so thoroughly, that even the error report from the failure - eh - fails. When the access attempt is finished and the error break terminated, the SB-PCL:PROTOTYPE slot is not NIL, as it was after DEFMODEL and FINALIZE-INHERITANCE. It is unbound. However that happens - I haven't got the foggiest idea. The attached file contains a few failed attempts to work around the problem by digging deeper into the SBCL CLOS implementation. best regards --peder chr. -- Peder Chr. Nørgaard e-mail: pcn(a)pogt.dk Gefionsvej 19 DK-8230 Åbyhøj tel: +45 87 44 11 99 Denmark mob: +45 30 91 84 31

3 3

[cells-devel] [ELS 2009] Call for participation
by Marco Antoniotti 20 May '09

20 May '09

Apologies for multiple postings.... ************************************************************************ 2nd European Lisp Symposium (ELS 2009) Milan, Italy, May 27-29, 2009 Universita` degli Studi di Milano-Bicocca www.european-lisp-symposium.org ************************************************************************ CALL FOR PARTICIPATION ********************** REGISTRATION IS OPEN AT www.european-lisp-symposium.org. Check out the updated program. Scope and Program Highlights: ***************************** The purpose of the European Lisp Symposium is to provide a forum for the discussion of all aspects of the design, implementation and application of any of the Lisp dialects. We encourage everyone interested in Lisp to participate. The European Lisp Symposium 2009 program includes presentations of high quality papers about novel research results, insights and lessons learned from practical applications, and educational perspectives, all involving Lisp dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, and so on. The European Lisp Symposium will feature the following highlights: - Scott McKay of ITA Software will talk about how Lisp use has evolved in his circannual industry work. - Mark Tarver of Lambda Associates will talk about Qi as a viral mutation of the Lisp DNA. - Mauro Pezze` of University of Milan-Bicocca will host a panel on Programmers' Productivity from a Software Engineering point of view. - Joao Pavao Martins and Ernesto Morgado of SISCOG will talk about the role of LISP in the success of SISCOG - Christophe Rhodes will give an unportable tutorial. - Michele Simionato will give a tutorial on Scheme module system and Scheme libraries portability issues across implementations. Social Events: ************** Friday 29th evening, Conference Banquet Saturday 30th morning, Guided tour to the "Futurismo" Exhibit in the center of Milan; 2009 marks the 100th anniversary of the Futurism Manifesto; stretching it, the harbinger of Lisp 50 years later. Program Chair: ************** * Antonio Leitao, Technical University of Lisbon, Portugal Local Chair: ************ * Marco Antoniotti, DISCo, Universita`† Milano Bicocca, Italy Program committee: ****************** * Giuseppe Attardi, Universita` di Pisa , Italy * Pascal Costanza, Vrije Universiteit Brussel, Belgium * Irene Durand, Universite` Bordeaux 1, France * Marc Feeley, Universite` de Montreal, Canada * Ron Garret, Amalgamated Widgets Unlimited, USA * Gregor Kiczales, University of British Columbia, Canada * Scott McKay, ITA Software, Inc., USA * Peter Norvig, Google Inc., USA * Julian Padget, University of Bath, UK * Kent Pitman, HyperMeta, USA * Christian Queinnec, Universite` Pierre et Marie Curie, France * Christophe Rhodes, Goldsmiths College, University of London, UK * Robert Strandh, Universite` Bordeaux 1, France * Mark Tarver, Lambda Associates, UK * Didier Verna, EPITA Research and Development Laboratory, France * JonL White, TheGingerIceCreamFactory of Palo Alto, USA * Taiichi Yuasa, Kyoto University, Japan Registration Fees: ****************** * Students EU100, regular EU220. Registration will include the proceedings, coffee breaks, the symposium dinner and other amenities. Accommodation is not included.

1 0

Re: [cells-devel] A question about the use of vectors in CELLS
by Kenneth Tilton 18 May '09

18 May '09

Frank Goenninger wrote: > It just occurred to me that a simple :unchanged-if function should do > the trick, no ? That is always my first reaction, too. Two problems: Cells works off (setf slot-value) if you will, and no code goes through that on (setf aref). The second problem is almost the same. Even this sequence: (setf (aref (myvector self) 42) 'hi-mom) (setf (myvector self) (myvector self)) ;; to get to unchanged-if ...would not work because Cells saves the slot-value for comparison and in this case before and after are the same vector -- so the old element 42 of course now holds 'hi-mom. kt

1 1

[cells-devel] A question about the use of vectors in CELLS
by Peder Chr. Nørgaard 18 May '09

18 May '09

Hello I am attempting to use a vector as the value in a slot. It does not work well in first attempt: CL-USER> (use-package :cells) T CL-USER> (defparameter a1 (make-instance 'model :value (c-in #(1 2 3 4)))) A1 CL-USER> (defparameter a2 (make-instance 'model :value (c? (apply #'+ (map 'list #'identity (value a1)))))) A2 CL-USER> (value a2) 10 CL-USER> (setf (elt (value a1) 1) 5) 5 CL-USER> (value a1) #(1 5 3 4) CL-USER> (value a2) 10 The VALUE slot of A2, depending on (VALUE A1) is not changing when (VALUE A1) is, shall we call it "changed in place". The cells version is from :pserver:anonymous:anonymous@common-lisp.net:/project/cells/cvsroot. The Lisp system is SBCL is 1.0.18.0-2. I would like to enquire whether I am simply doing something trivially wrong, or whether this is something that simply cannot be done without a major CELLS extension for support of vector values (like, FAMILY, can be viewed as a kind of support for list values). The latter answer may force me to reconsider an implementation that I had in mind. Thank you in advance for any information -- Peder Chr. Nørgaard e-mail: pcn(a)pogt.dk Gefionsvej 19 DK-8230 Åbyhøj tel: +45 87 44 11 99 Denmark mob: +45 30 91 84 31

3 4