From eenge at common-lisp.net Mon Aug 7 13:27:51 2006 From: eenge at common-lisp.net (Erik Enge) Date: Mon, 7 Aug 2006 09:27:51 -0400 (EDT) Subject: [closer-devel] Please move your files off ofcommon-lisp.net FTP Message-ID: <20060807132751.E6E822F028@common-lisp.net> As mentioned in http://common-lisp.net/pipermail/users/2006-August/000006.html FTP will soon be going away on common-lisp.net. Your project showed up in a grep for ftp in your public_html suggests that you either store files in your ftp directory or that you link to files in FTP on common-lisp.net. This email serves as a second notice that you'll want to update your links and move your files. Move them into your public_html directory and link to them there, Apache will happily serve them for you. Thanks, Erik. From pc at p-cos.net Wed Aug 9 21:08:52 2006 From: pc at p-cos.net (Pascal Costanza) Date: Wed, 9 Aug 2006 23:08:52 +0200 Subject: [closer-devel] Please move your files off ofcommon-lisp.net FTP In-Reply-To: <20060807132751.E6E822F028@common-lisp.net> References: <20060807132751.E6E822F028@common-lisp.net> Message-ID: Hi Erik, For the closer project, I have just removed the files from the ftp directory and moved them to public html. Cheers, Pascal On 7 Aug 2006, at 15:27, Erik Enge wrote: > As mentioned in http://common-lisp.net/pipermail/users/2006-August/ > 000006.html > FTP will soon be going away on common-lisp.net. Your project > showed up in a grep > for ftp in your public_html suggests that you either store files in > your ftp directory > or that you link to files in FTP on common-lisp.net. > > This email serves as a second notice that you'll want to update > your links > and move your files. Move them into your public_html directory and > link to > them there, Apache will happily serve them for you. > > Thanks, > Erik. > _______________________________________________ > closer-devel mailing list > closer-devel at common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/closer-devel -- Pascal Costanza, mailto:pc at p-cos.net, http://p-cos.net Vrije Universiteit Brussel, Programming Technology Lab Pleinlaan 2, B-1050 Brussel, Belgium From gimmal at gmail.com Tue Aug 15 02:50:55 2006 From: gimmal at gmail.com (Sean Champ) Date: Mon, 14 Aug 2006 19:50:55 -0700 Subject: [closer-devel] cross-platform identification of slot-protocol class, metaclass Message-ID: Hello, There have been some methods I have defined, which I wanted to specialize on either the slot-protocol class or slot-protocol metaclass for the current implementation. In PCL environments, I know that those classes are, respectively, SLOT-OBJECT and SLOT-CLASS (within the correct PCL package, of course). In other implementations -- my not being aware of how structure classes and condition classes may be implemented, in those, while they are types of slot-class in PCL -- in implementations neither CMUCL nor SBCL, rather, I had simply used STANDARD-OBJECT and STANDARD-CLASS, respectively. Upon my having noticed the following, in some older code on my host, and my now being aware of the closer-mop project, I would like to propose if it form would be considered for addition into closer-mop. Of course, the final form of the implementation-specific code would need to be split, so as to be added into the support code for each respective implementation. ------- (export '(+slot-protocol-class+ +slot-protocol-class+ ;; type specifiers slot-protocol-instance slot-protocol-class)) (eval-when (:compile-toplevel :load-toplevel :execute) (defconstant +slot-protocol-class+ #+SBCL 'sb-pcl::slot-object #+PCL 'pcl::slot-object #-(or SBCL PCL) 'standard-object) (defconstant +slot-protocol-class+ #+SBCL 'sb-pcl::slot-class #+PCL 'pcl::slot-class #-(or SBCL PCL) 'standard-object) ) (deftype slot-protocol-instance () (quote #.+slot-protocol-class+)) (deftype slot-protocol-class () (quote #.+slot-protocol-class+)) ------- I could submit a patch, so as to add that into the closer-mop codebase. I had wanted to propose the matter, firsly, as I was not aware if it would be wanted to be added. Before I would make a patch for it, I would hope if other folks might know what the correct classes would be, for closer-mop-supported implementations neither SBCL nor CMUCL. Perhaps STANDARD-OBJECT and STANDARD-CLASS would be too general, as specializers, in some implementations.. For now, I will leave that stuff defined, as above; it is being added into in he Auxiliary Library code to the Tioga Project. If it would be wanted in closer-mop, I would be glad to remove it from there. I consider that it would be appropriate, if forms like the above would be located in a place more central to the origin of the type specifiers used in the forms. In my own stuff, I need that those forms would be defined, somewhere, so that those variables may be used in the initialization of method specializers -- viz. #.+slot-protocol-class+ in the specializer spot to a standard method lambda-list -- and that those type specifiers would be available. Initially, those forms will be available in TAL; it should be to no issue, if they would be made available, most directly, via Closer-MOP. With a shout-out across the world wide code house, yo' -- Sean Champ Tioga Project - http://www.common-lisp.net/project/tioga/ From pc at p-cos.net Mon Aug 21 20:48:56 2006 From: pc at p-cos.net (Pascal Costanza) Date: Mon, 21 Aug 2006 22:48:56 +0200 Subject: [closer-devel] .asd files changed. Message-ID: <22222C8B-3428-4F30-8BB1-057A241FB891@p-cos.net> Hi, I have just made the following change to the .asd files in all the Closer projects: I have removed the initial (in-package :cl-user) declarations. I have been told that this is not necessary and may actually confuse ASDF. Please let me know if this causes any problems. On an unrelated note, I will wait a few more days before I will make the next "official" tar balls available. The reason is that the CVS version of SBCL has made a quantum leap forward with regard to CLOS MOP support, and I would like to match the releases of the Closer project with that version of SBCL (that would be 0.9.16). I have also tested everything against OpenMCL 1.1, and everything seems to work fine. Currently, I don't have a copy of LispWorks 5.0 at hand, so I cannot say anything about it. I hope I can test the Closer software against LW 5.0 soon. Cheers, Pascal -- Pascal Costanza, mailto:pc at p-cos.net, http://p-cos.net Vrije Universiteit Brussel, Programming Technology Lab Pleinlaan 2, B-1050 Brussel, Belgium From pc at p-cos.net Thu Aug 24 12:49:19 2006 From: pc at p-cos.net (Pascal Costanza) Date: Thu, 24 Aug 2006 14:49:19 +0200 Subject: [closer-devel] Efficient Layer Activation Message-ID: Hi everyone, Springer Verlag has changed its regulations about copyrights, so it's now possible to publish papers that are published in a Springer publication on one's own website. Therefore, the paper about the implementation of ContextL can now be downloaded from http://p-cos.net/documents/context-switch.pdf - together with a benchmark that suggests that ContextL is quite efficient. Cheers, Pascal -- Pascal Costanza, mailto:pc at p-cos.net, http://p-cos.net Vrije Universiteit Brussel, Programming Technology Lab Pleinlaan 2, B-1050 Brussel, Belgium From pc at p-cos.net Sat Aug 26 15:14:43 2006 From: pc at p-cos.net (Pascal Costanza) Date: Sat, 26 Aug 2006 17:14:43 +0200 Subject: [closer-devel] New releases in the Closer project. Message-ID: <4D842F02-9A6C-4AEE-890F-3648CF7B2A23@p-cos.net> Hi everyone, I have just uploaded new versions of all packages in the Closer project. They are all tagged with new version numbers, and tar balls of the new versions are also available. Please see http://common- lisp.net/project/closer for more details. Pascal -- Pascal Costanza, mailto:pc at p-cos.net, http://p-cos.net Vrije Universiteit Brussel, Programming Technology Lab Pleinlaan 2, B-1050 Brussel, Belgium