From pc at p-cos.net Wed Nov 1 14:16:48 2006 From: pc at p-cos.net (Pascal Costanza) Date: Wed, 1 Nov 2006 15:16:48 +0100 Subject: [portage-overlay-devel] [ann] [cdr-announce] CDR 3 accepted Message-ID: <8FFA74DF-AB1E-47E7-AA4C-AA1B3423A93C@p-cos.net> The document "Revisiting CONCATENATE-SEQUENCE" has been submitted by Christophe Rhodes and has been accepted as CDR document 3. According to the CDR process, this document is now in its initial stage and will be finalized on December 13, 2006, unless withdrawn by the author beforehand. See http://cdr.eurolisp.org/document/3/ for the details of this document. 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 _______________________________________________ cdr-announce mailing list cdr-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From mcclim-devel at common-lisp.net Thu Nov 2 18:24:11 2006 From: mcclim-devel at common-lisp.net (McCLIM developers) Date: Thu, 02 Nov 2006 19:24:11 +0100 Subject: [portage-overlay-devel] [ann] [mcclim-announce] Announcing McCLIM 0.9.3 "All Saints' Day" Message-ID: <454A37CB.8080507@common-lisp.net> The McCLIM developers are happy to release version 0.9.3 of McCLIM, code-named "All Saints' Day". This release was tested and found to work on the following implementations: * SBCL * OpenMCL * Allegro Common Lisp 8.0 in ANSI Mode * The Scieneer Common Lisp in ANSI Mode For compatibility with other implementations, please see the attached release notes. Get the tarball at or install McCLIM via asdf-install. We are looking forward to your comments and bug reports. Please send them to mcclim-devel at common-lisp.net. The list of currently known bugs can be found at . Have fun using McCLIM (and build good things with it), The McCLIM developers. RELEASE NOTES FOR McCLIM 0.9.2, "Laetare Sunday": Compatibility ============= This release was tested and found to work on the following implementations: * SBCL * OpenMCL * Allegro Common Lisp 8.0 in ANSI Mode * The Scieneer Common Lisp in ANSI Mode In our tests, this release of McCLIM did not work on the following implementations: * CLISP (there are some problems with CLISP at the moment, but it is possible to run McCLIM there; a HOWTO will be posted to http://planet.lisp.org). * CMUCL (at the time of this release, the released CMUCL has a bug that prevents successful loading of McCLIM; CMUCL 19d + patch 1 and the 2006-12 snapshot or later contain a fix for this problem) * LispWorks (no known workaround) Also, McCLIM currently does not support lisps with case-sensitive readers (ACL "modern mode" and lower-case SCL). Changes in mcclim-0.9.3 "All Souls' Day" relative to 0.9.2: =========================================================== From the NEWS file: * backend improvement: The Null backend now registers itself in the server search path * improvement: with-output-as-gadget now sets the correct cursor position when incremental redisplay is active. * specification compliance: INVOKE-WITH-NEW-OUTPUT-RECORD's argument list now is the same as the one in the Franz CLIM user guide. * improvement: The text field cursor is now a solid block again. * backend improvement: the PostScript backend now outputs correct EPS * improvement: Graph nodes can now be dragged * improvement: Possibilities when reading from COMPLETE-FROM-GENERATOR are now sorted alphabetically. * new experimental backend: gtkairo (loads on SBCL, CMUCL and SCL): Uses GTK+ for gadgets and cairo for rendering graphics. * Bug fix: incremental-redisplay does no longer leak memory * improvement: incremental-redisplay is now a little faster * Bug fix: Invisible text cursors no longer leave a dangling space behind the text output record * improvement: commands whose names are shadowed in child command tables are now suggested in preference to their parents. * Bug fix: (setf stream-cursor-position) and output record replay on encapsulating streams work now. * Bug fix: Invoking command menu items in frames with no interactor works now. * Bug fix: DESTROY-PORT removes the port even if an error occurs while closing the port * Bug fix: make-process now sets the process name on SBCL * specification compliance: MENU-CHOOSE now supports almost all features demanded in the CLIM 2.0 specification. * improvement: new and improved ACCEPT presentation method for expressions on interactive streams. * specification compliance: LOOKUP-KEYSTROKE-ITEM no longer accepts the :errorp argument. * Bug fix: incremental redisplay no longer breaks on output records that had no children. * Bug fix: arrow head sizes are now transformed along with the line thickness. * improvement: resizing a viewport's child will now move the viewport's focus. * improvement: loading mcclim.asd no longer shows a code deletion note on SBCL. * new demo: logic-cube * compatibility: Add support for post-1.0 openmcl, and for Allegro Common Lisp 8.0 (ansi mode). * new example application showing use of CLIM views. _______________________________________________ mcclim-announce mailing list mcclim-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/mcclim-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From mcclim-devel at common-lisp.net Thu Nov 2 18:43:20 2006 From: mcclim-devel at common-lisp.net (McCLIM developers) Date: Thu, 02 Nov 2006 19:43:20 +0100 Subject: [portage-overlay-devel] [ann] [mcclim-announce] (corrected) Announcing McCLIM 0.9.3 "All Souls' Day" Message-ID: <454A3C48.80600@common-lisp.net> The McCLIM developers are happy to release version 0.9.3 of McCLIM, code-named "All Saints' Day". This release was tested and found to work on the following implementations: * SBCL * OpenMCL * Allegro Common Lisp 8.0 in ANSI Mode * The Scieneer Common Lisp in ANSI Mode For compatibility with other implementations, please see the attached release notes. Get the tarball at or install McCLIM via asdf-install. We are looking forward to your comments and bug reports. Please send them to mcclim-devel at common-lisp.net. The list of currently known bugs can be found at . Have fun using McCLIM (and build good things with it), The McCLIM developers. RELEASE NOTES FOR McCLIM 0.9.3, "All Souls' Day": Compatibility ============= This release was tested and found to work on the following implementations: * SBCL * OpenMCL * Allegro Common Lisp 8.0 in ANSI Mode * The Scieneer Common Lisp in ANSI Mode In our tests, this release of McCLIM did not work on the following implementations: * CLISP (there are some problems with CLISP at the moment, but it is possible to run McCLIM there; a HOWTO will be posted to http://planet.lisp.org). * CMUCL (at the time of this release, the released CMUCL has a bug that prevents successful loading of McCLIM; CMUCL 19d + patch 1 and the 2006-12 snapshot or later contain a fix for this problem) * LispWorks (no known workaround) Also, McCLIM currently does not support lisps with case-sensitive readers (ACL "modern mode" and lower-case SCL). Changes in mcclim-0.9.3 "All Souls' Day" relative to 0.9.2: =========================================================== From the NEWS file: * backend improvement: The Null backend now registers itself in the server search path * improvement: with-output-as-gadget now sets the correct cursor position when incremental redisplay is active. * specification compliance: INVOKE-WITH-NEW-OUTPUT-RECORD's argument list now is the same as the one in the Franz CLIM user guide. * improvement: The text field cursor is now a solid block again. * backend improvement: the PostScript backend now outputs correct EPS * improvement: Graph nodes can now be dragged * improvement: Possibilities when reading from COMPLETE-FROM-GENERATOR are now sorted alphabetically. * new experimental backend: gtkairo (loads on SBCL, CMUCL and SCL): Uses GTK+ for gadgets and cairo for rendering graphics. * Bug fix: incremental-redisplay does no longer leak memory * improvement: incremental-redisplay is now a little faster * Bug fix: Invisible text cursors no longer leave a dangling space behind the text output record * improvement: commands whose names are shadowed in child command tables are now suggested in preference to their parents. * Bug fix: (setf stream-cursor-position) and output record replay on encapsulating streams work now. * Bug fix: Invoking command menu items in frames with no interactor works now. * Bug fix: DESTROY-PORT removes the port even if an error occurs while closing the port * Bug fix: make-process now sets the process name on SBCL * specification compliance: MENU-CHOOSE now supports almost all features demanded in the CLIM 2.0 specification. * improvement: new and improved ACCEPT presentation method for expressions on interactive streams. * specification compliance: LOOKUP-KEYSTROKE-ITEM no longer accepts the :errorp argument. * Bug fix: incremental redisplay no longer breaks on output records that had no children. * Bug fix: arrow head sizes are now transformed along with the line thickness. * improvement: resizing a viewport's child will now move the viewport's focus. * improvement: loading mcclim.asd no longer shows a code deletion note on SBCL. * new demo: logic-cube * compatibility: Add support for post-1.0 openmcl, and for Allegro Common Lisp 8.0 (ansi mode). * new example application showing use of CLIM views. _______________________________________________ mcclim-announce mailing list mcclim-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/mcclim-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From hhalvors at Princeton.EDU Sun Nov 5 01:17:43 2006 From: hhalvors at Princeton.EDU (Hans Halvorson) Date: Sat, 04 Nov 2006 20:17:43 -0500 Subject: [portage-overlay-devel] common-lisp-controller and slime Message-ID: <87odrm1yko.wl%hhalvors@Princeton.EDU> I just updated to the unstable version (5.13) of common-lisp-controller; I previously had 4.27 installed. I noted that the cmucl files changed places. They were previously in: /var/cache/common-lisp-controller/my-username/ and now are in /var/cache/common-lisp-controller/1000/ Is that the way it's supposed to be? What is this "1000"? Aren't the files supposed to be placed under my-username? Thanks, Hans From zedek at gnu.org Sun Nov 5 09:04:49 2006 From: zedek at gnu.org (Xavier Maillard) Date: Sun, 05 Nov 2006 10:04:49 +0100 Subject: [portage-overlay-devel] common-lisp-controller and slime In-Reply-To: <87odrm1yko.wl%hhalvors@Princeton.EDU> References: <87odrm1yko.wl%hhalvors@Princeton.EDU> Message-ID: <87zmb6w9fy.fsf@zogzog.gnu-rox.org> Is that the way it's supposed to be? What is this "1000"? Aren't the files supposed to be placed under my-username? That's ok. The "1000" is certainly the user id (that is to say, you). -- Xavier From edi at agharta.de Sun Nov 5 20:32:04 2006 From: edi at agharta.de (Edi Weitz) Date: Sun, 05 Nov 2006 21:32:04 +0100 Subject: [portage-overlay-devel] [ann] [hunchentoot-announce] New version 0.4.6 (Was: Confusing Hunchentoot behaviour) In-Reply-To: (Marijn Haverbeke's message of "Sat, 4 Nov 2006 21:48:24 +0100") References: Message-ID: On Sat, 4 Nov 2006 21:48:24 +0100, "Marijn Haverbeke" wrote: > A good fix would be to just call *meta-dispatcher* for every call to > dispatch-request, so that you've always got the most recent > dispatch-table and the programmer can fiddle with that variable from > the REPL and immediately see the result. I've implemented that now in the new version. *META-DISPATCHER* came in pretty late in the game, and it wasn't intended to behave like it did until 0.4.5. Thanks for the report. Cheers, Edi. _______________________________________________ tbnl-announce site list tbnl-announce at common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From edi at agharta.de Sun Nov 5 22:57:39 2006 From: edi at agharta.de (Edi Weitz) Date: Sun, 05 Nov 2006 23:57:39 +0100 Subject: [portage-overlay-devel] [ann] [hunchentoot-announce] New version 0.4.7 (Was: real-remote-addr and proxy chains) In-Reply-To: <20061105211850.GB14326@oja.no> (Robert J. Macomber's message of "Sun, 05 Nov 2006 14:18:50 -0700") References: <20061102181555.GA12734@oja.no> <20061105204818.GA14326@oja.no> <20061105211850.GB14326@oja.no> Message-ID: On Sun, 05 Nov 2006 14:18:50 -0700, "Robert J. Macomber" wrote: > Depends on whether you're interested in the user's (claimed) real > address, or the address the user presents to the web server to which > he thinks he's speaking. In my case, I'm interested in the latter > (that is, I'm just interested in what REMOTE-ADDR would be if > Hunchentoot weren't behind a server-side proxy). Having looked at > the documentation for sessions in the past five minutes, I see that > that machinery is interested in the former. OK, I've implemented the version I described in my previous email. The new release also fixes the bug in COOKIE-OUT you mentioned. Thanks, Edi. _______________________________________________ tbnl-announce site list tbnl-announce at common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From edi at agharta.de Sun Nov 5 23:48:43 2006 From: edi at agharta.de (Edi Weitz) Date: Mon, 06 Nov 2006 00:48:43 +0100 Subject: [portage-overlay-devel] [ann] [flexi-streams-announce] New version 0.7.2 Message-ID: ChangeLog: Version 0.7.2 2006-11-06 Removed unnecessary CHECK-EOF-NO-HANG also for in-memory streams (see 0.5.8) Download: http://weitz.de/files/flexi-streams.tar.gz Cheers, Edi. _______________________________________________ flexi-streams-announce mailing list flexi-streams-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/flexi-streams-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From edi at agharta.de Mon Nov 6 00:06:36 2006 From: edi at agharta.de (Edi Weitz) Date: Mon, 06 Nov 2006 01:06:36 +0100 Subject: [portage-overlay-devel] [ann] [hunchentoot-announce] New version 0.4.8 (Was: Problems with file uploads and mod_lisp) In-Reply-To: (Edi Weitz's message of "Sun, 29 Oct 2006 03:07:26 +0100") References: Message-ID: On Sun, 29 Oct 2006 03:07:26 +0100, Edi Weitz wrote: > I just realized that Hunchentoot in its current form has problems > with file uploads if it's used behind mod_lisp. I think I've fixed this in 0.4.8 now. At least I found something in START-OUTPUT which was obviously wrong and a result of my porting and re-factoring Hunchentoot/TBNL too hastily. Cheers, Edi. _______________________________________________ tbnl-announce site list tbnl-announce at common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From hhalvors at Princeton.EDU Thu Nov 9 22:09:13 2006 From: hhalvors at Princeton.EDU (Hans Halvorson) Date: Thu, 09 Nov 2006 17:09:13 -0500 Subject: [portage-overlay-devel] I broke cmucl Message-ID: <87r6wcs25y.wl%hhalvors@Princeton.EDU> I upgraded to cmucl-19d (unstable), and I was having trouble accessing the cmucl-clx libraries. (Are they not installed with 19d?) So, I downgraded to 19c. But now when I try to start cmucl, I get: "Strange ... dynamic space lossage Segmentation fault." Ouch!! I even re-emerged a couple of times to no avail -- still a segmentation fault. How can I recover? Thanks, Hans From mkennedy at gentoo.org Fri Nov 10 03:02:22 2006 From: mkennedy at gentoo.org (Matthew Kennedy) Date: Thu, 09 Nov 2006 21:02:22 -0600 Subject: [portage-overlay-devel] I broke cmucl In-Reply-To: <87r6wcs25y.wl%hhalvors@Princeton.EDU> (Hans Halvorson's message of "Thu\, 09 Nov 2006 17\:09\:13 -0500") References: <87r6wcs25y.wl%hhalvors@Princeton.EDU> Message-ID: <87irhoj96p.fsf@gentoo.org> Hans Halvorson writes: > I upgraded to cmucl-19d (unstable), and I was having trouble accessing > the cmucl-clx libraries. (Are they not installed with 19d?) So, I Hi Hans, With dev-lisp/cmucl-19d_pre1, dev-lisp/sbcl-0.9.18 and dev-lisp/clisp-2.41 (all committed to CVS last night), we've stopped using the Common Lisp Controller. Before with CMUCL 19c and the Common Lisp Controller, the clx subsystem, and other CMUCL subsystems (clm, gray-streams, simple-streams, hemlock etc.) were installed with ASDF system definitions. Now you need to do things the CMUCL way, the way the upstream developers intended: $ lisp CMU Common Lisp CVS Head 2006-10-28 01:59:57 (19D), running on localhost With core: /usr/lib/cmucl/lib/lisp.core Dumped on: Sat, 2006-10-28 02:17:51-05:00 on localhost See for support information. Loaded subsystems: Python 1.1, target Intel x86 CLOS based on Gerd's PCL 2004/04/14 03:32:47 * (require :clx) ; Loading #P"/usr/lib/cmucl/lib/subsystems/clx-library.x86f". ; [GC threshold exceeded with 12,011,280 bytes in use. Commencing GC.] ; [GC completed with 2,940,480 bytes retained and 9,070,800 bytes freed.] ; [GC will next occur when at least 14,940,480 bytes are in use.] ("CLX") * We have an upgrade guide here: http://www.gentoo.org/proj/en/common-lisp/guide.xml It describes how to use the Common Lisp libraries in the absence of the Common Lisp Controller. It doesn't mention the change to loading CLX for CMUCL though. I'll add a section on that tonight and also link the guide from the project page: http://www.gentoo.org/proj/en/common-lisp/index.xml > downgraded to 19c. But now when I try to start cmucl, I get: > > "Strange ... dynamic space lossage > Segmentation fault." I'm not sure what would cause that problem, especially since your CMUCL 19c ran fine under the same configuration. Could you file a bug report? Make sure to include the output of emerge --info. Best regards, Matt -- Matthew Kennedy Gentoo Linux Developer (Public Key 0x401903E0) From pc at p-cos.net Sat Nov 11 12:17:56 2006 From: pc at p-cos.net (Pascal Costanza) Date: Sat, 11 Nov 2006 13:17:56 +0100 Subject: [portage-overlay-devel] [ann] [cdr-announce] CDR 2 updated Message-ID: <36F0BA24-61AA-4D2F-A361-C544E6496D38@p-cos.net> Ingvar Mattsson has submitted a new version of CDR 2 which is now available at http://cdr.eurolisp.org/document/2/ 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 _______________________________________________ cdr-announce mailing list cdr-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From hhalvors at Princeton.EDU Sun Nov 12 13:19:03 2006 From: hhalvors at Princeton.EDU (Hans Halvorson) Date: Sun, 12 Nov 2006 08:19:03 -0500 Subject: [portage-overlay-devel] I broke cmucl In-Reply-To: <87irhoj96p.fsf@gentoo.org> References: <87r6wcs25y.wl%hhalvors@Princeton.EDU> <87irhoj96p.fsf@gentoo.org> Message-ID: <87zmawhkfs.wl%hhalvors@Princeton.EDU> Matt, Thanks for the very helpful information. Given the recent changes (namely, migration away from common-lisp-controller), I've decided I should try to continue to upgrade to the most recent versions (e.g. cmucl 19d). I'm trying to follow the directions on the Gentoo Common Lisp User Guide, but I'm having a bit of trouble -- I was getting an error message that fasl's (e.g. for clx) were compiled for 19c. I tried manually deleting the offending fasl (OK, I realize this was stupid), but then cmucl tells me it doesn't know how to require clx, because it can't find the source. (I am now also using asdf-binary-locations and gentoo-init.) I include the output below. -Hans ==================== # lisp ; Loading #P"/home/hhalvors/.cmucl-init.lisp". ;; Loading #P"/etc/gentoo-init.lisp". ;;; Loading #P"/usr/share/common-lisp/source/asdf/asdf.lisp". ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. X): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. X): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. X): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. X): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. X): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. X): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. X): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. X): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. X): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. X): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. C S): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. C S): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. COMPONENT): ; Compiling Top-Level Form: ; In: LAMBDA (PCL::.PV-CELL. PCL::.NEXT-METHOD-CALL. C STREAM) ; (KERNEL:FLOAT-WAIT) ; Note: Deleting unreachable code. ; ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. C STREAM): ; Compiling Top-Level Form: ; Compilation unit finished. ; 1 note ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. COMPONENT): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. COMPONENT): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. C PROPERTY): ; Compiling Top-Level Form: ; [GC threshold exceeded with 12,011,904 bytes in use. Commencing GC.] ; [GC completed with 4,077,968 bytes retained and 7,933,936 bytes freed.] --- approximately 50 lines cut --- ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. OPERATION C): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. PACKAGE NAME DOC-TYPE): ; Compiling Top-Level Form: ; loading system definition from ; /usr/share/common-lisp/systems/asdf-binary-locations.asd into ; # ;;; Loading #P"/usr/share/common-lisp/source/asdf-binary-locations/asdf-binary-locations.asd". ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. OP COMPONENT): ; Compiling Top-Level Form: ; [GC threshold exceeded with 22,701,096 bytes in use. Commencing GC.] ; [GC completed with 14,260,640 bytes retained and 8,440,456 bytes freed.] ; [GC will next occur when at least 26,260,640 bytes are in use.] ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. OP COMPONENT): ; Compiling Top-Level Form: ; registering # as ; ASDF-BINARY-LOCATIONS ;;; Loading #P"/usr/share/common-lisp/source/asdf-binary-locations/dev/main.lisp". ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. SYSTEM OPERATION COMPONENT SOURCE POSSIBLE-PATHS): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. SOURCE POSSIBLE-PATHS PATH-MAPPINGS): ; Compiling Top-Level Form: ; Compiling LAMBDA (.PV-CELL. .NEXT-METHOD-CALL. OPERATION COMPONENT): ; Compiling Top-Level Form: CMU Common Lisp CVS Head 2006-11-12 07:33:49 (19D), running on phi-ghk3981 With core: /usr/lib/cmucl/lib/lisp.core Dumped on: Sun, 2006-11-12 07:40:42-05:00 on phi-ghk3981 See for support information. Loaded subsystems: Python 1.1, target Intel x86 CLOS based on Gerd's PCL 2004/04/14 03:32:47 * (require :clx) Error in function REQUIRE: Don't know how to load CLX [Condition of type SIMPLE-ERROR] Restarts: 0: [ABORT] Return to Top-Level. Debug (type H for help) (REQUIRE :CLX NIL) Source: Error finding source: Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM: Source file no longer exists: target:code/module.lisp. At Thu, 09 Nov 2006 21:02:22 -0600, Matthew Kennedy wrote: > > Hans Halvorson writes: > > > I upgraded to cmucl-19d (unstable), and I was having trouble accessing > > the cmucl-clx libraries. (Are they not installed with 19d?) So, I > > Hi Hans, > > With dev-lisp/cmucl-19d_pre1, dev-lisp/sbcl-0.9.18 and > dev-lisp/clisp-2.41 (all committed to CVS last night), we've stopped > using the Common Lisp Controller. Before with CMUCL 19c and the > Common Lisp Controller, the clx subsystem, and other CMUCL subsystems > (clm, gray-streams, simple-streams, hemlock etc.) were installed with > ASDF system definitions. > > Now you need to do things the CMUCL way, the way the upstream > developers intended: > > $ lisp > CMU Common Lisp CVS Head 2006-10-28 01:59:57 (19D), running on localhost > With core: /usr/lib/cmucl/lib/lisp.core > Dumped on: Sat, 2006-10-28 02:17:51-05:00 on localhost > See for support information. > Loaded subsystems: > Python 1.1, target Intel x86 > CLOS based on Gerd's PCL 2004/04/14 03:32:47 > * (require :clx) > > ; Loading #P"/usr/lib/cmucl/lib/subsystems/clx-library.x86f". > ; [GC threshold exceeded with 12,011,280 bytes in use. Commencing GC.] > ; [GC completed with 2,940,480 bytes retained and 9,070,800 bytes freed.] > ; [GC will next occur when at least 14,940,480 bytes are in use.] > ("CLX") > * > > We have an upgrade guide here: > > http://www.gentoo.org/proj/en/common-lisp/guide.xml > > It describes how to use the Common Lisp libraries in the absence of > the Common Lisp Controller. It doesn't mention the change to loading > CLX for CMUCL though. I'll add a section on that tonight and also > link the guide from the project page: > > http://www.gentoo.org/proj/en/common-lisp/index.xml > > > downgraded to 19c. But now when I try to start cmucl, I get: > > > > "Strange ... dynamic space lossage > > Segmentation fault." > > I'm not sure what would cause that problem, especially since your > CMUCL 19c ran fine under the same configuration. Could you file a bug > report? Make sure to include the output of emerge --info. > > Best regards, > > Matt > > -- > Matthew Kennedy > Gentoo Linux Developer (Public Key 0x401903E0) From hhalvors at Princeton.EDU Sun Nov 12 13:45:50 2006 From: hhalvors at Princeton.EDU (Hans Halvorson) Date: Sun, 12 Nov 2006 08:45:50 -0500 Subject: [portage-overlay-devel] I broke cmucl In-Reply-To: <87irhoj96p.fsf@gentoo.org> References: <87r6wcs25y.wl%hhalvors@Princeton.EDU> <87irhoj96p.fsf@gentoo.org> Message-ID: <87ac2w22y9.wl%hhalvors@Princeton.EDU> PS to previous message: I unmerged and re-emerged cmucl (thinking that this would get rid of stale files from 19c.) Here is the output of (require :clx). Loaded subsystems: Python 1.1, target Intel x86 CLOS based on Gerd's PCL 2004/04/14 03:32:47 * (require :clx) Error in function REQUIRE: Don't know how to load CLX [Condition of type SIMPLE-ERROR] Restarts: 0: [ABORT] Return to Top-Level. Debug (type H for help) (REQUIRE :CLX NIL) Source: Error finding source: Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM: Source file no longer exists: target:code/module.lisp. At Thu, 09 Nov 2006 21:02:22 -0600, Matthew Kennedy wrote: > > Hans Halvorson writes: > > > I upgraded to cmucl-19d (unstable), and I was having trouble accessing > > the cmucl-clx libraries. (Are they not installed with 19d?) So, I > > Hi Hans, > > With dev-lisp/cmucl-19d_pre1, dev-lisp/sbcl-0.9.18 and > dev-lisp/clisp-2.41 (all committed to CVS last night), we've stopped > using the Common Lisp Controller. Before with CMUCL 19c and the > Common Lisp Controller, the clx subsystem, and other CMUCL subsystems > (clm, gray-streams, simple-streams, hemlock etc.) were installed with > ASDF system definitions. > > Now you need to do things the CMUCL way, the way the upstream > developers intended: > > $ lisp > CMU Common Lisp CVS Head 2006-10-28 01:59:57 (19D), running on localhost > With core: /usr/lib/cmucl/lib/lisp.core > Dumped on: Sat, 2006-10-28 02:17:51-05:00 on localhost > See for support information. > Loaded subsystems: > Python 1.1, target Intel x86 > CLOS based on Gerd's PCL 2004/04/14 03:32:47 > * (require :clx) > > ; Loading #P"/usr/lib/cmucl/lib/subsystems/clx-library.x86f". > ; [GC threshold exceeded with 12,011,280 bytes in use. Commencing GC.] > ; [GC completed with 2,940,480 bytes retained and 9,070,800 bytes freed.] > ; [GC will next occur when at least 14,940,480 bytes are in use.] > ("CLX") > * > > We have an upgrade guide here: > > http://www.gentoo.org/proj/en/common-lisp/guide.xml > > It describes how to use the Common Lisp libraries in the absence of > the Common Lisp Controller. It doesn't mention the change to loading > CLX for CMUCL though. I'll add a section on that tonight and also > link the guide from the project page: > > http://www.gentoo.org/proj/en/common-lisp/index.xml > > > downgraded to 19c. But now when I try to start cmucl, I get: > > > > "Strange ... dynamic space lossage > > Segmentation fault." > > I'm not sure what would cause that problem, especially since your > CMUCL 19c ran fine under the same configuration. Could you file a bug > report? Make sure to include the output of emerge --info. > > Best regards, > > Matt > > -- > Matthew Kennedy > Gentoo Linux Developer (Public Key 0x401903E0) From edi at agharta.de Sun Nov 12 13:44:13 2006 From: edi at agharta.de (Edi Weitz) Date: Sun, 12 Nov 2006 14:44:13 +0100 Subject: [portage-overlay-devel] [ann] [hunchentoot-announce] New release 0.4.9 (Was: header(s)-out) In-Reply-To: <20061109215558.GC7054@oja.no> (Robert J. Macomber's message of "Thu, 09 Nov 2006 14:55:58 -0700") References: <20061109215558.GC7054@oja.no> Message-ID: On Thu, 09 Nov 2006 14:55:58 -0700, "Robert J. Macomber" wrote: > There seems to be some small bugs involving header-out. The > accessor is documented to take both keywords and strings, but > neither works reliably because: > > [snip] Yes, you're absolutely right. Thanks for spotting that. As I said, there were obviously too many (untested) changes at once when I switched from TBNL to Hunchentoot. > Here's a patch which normalizes things so the keys of this alist are > always strings and the lookup is always done with strings. I've changed this a little bit because I prefer that the keys are strings. Thanks, Edi. _______________________________________________ tbnl-announce site list tbnl-announce at common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From vamlists at gmail.com Sun Nov 12 03:21:17 2006 From: vamlists at gmail.com (Vamsee Kanakala) Date: Sun, 12 Nov 2006 08:51:17 +0530 Subject: [portage-overlay-devel] [cl-migrations-announce] [ANN] cl-migrations 0.0.1 Message-ID: <4556932D.708@gmail.com> Hi all, I would like to announce the availability of cl-migrations, a port of the migrations feature of Ruby on Rails to Common Lisp. cl-migrations is a simple tool to manage your changes to a database as you develop your web application or any database-backed application. It works by generating a new file to put for each database change, which contains the ddl required to enable and disable that change. So, effectively you can version-control your database structure. You can move to a particular version (whether back or forth) of your database structure by simply doing: (cl-migrations:migrate :version 42) You can install this tool with asdf: (asdf-install:install :cl-migrations) This tool depends on clsql, so you can run migrations on any database that is supported by clsql. Many thanks to Kevin Rosenberg for maintaining such a useful library. For more info, please go to this page: http://common-lisp.net/project/cl-migrations/ Kindly raise any questions/feature requests/bug-reports here: http://common-lisp.net/cgi-bin/mailman/listinfo/cl-migrations-devel Regards, Vamsee Kanakala. _______________________________________________ cl-migrations-announce mailing list cl-migrations-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cl-migrations-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From edi at agharta.de Tue Nov 14 20:56:28 2006 From: edi at agharta.de (Edi Weitz) Date: Tue, 14 Nov 2006 21:56:28 +0100 Subject: [portage-overlay-devel] [ann] [flexi-streams-announce] New version 0.8.0 (Was: recovering from flexi-stream-encoding-error) In-Reply-To: (Anton Vodonosov's message of "Tue, 14 Nov 2006 20:34:07 +0200") References: Message-ID: On Tue, 14 Nov 2006 20:34:07 +0200, "Anton Vodonosov" wrote: > It sometimes necessary to recover from flexi-stream-encoding-error. > > For example, it's inconvenient now to use drakma for sites with > broken utf encoding (like this livejournal page > http://hzweiblum.livejournal.com/) > > I can see this page in my browser (with ? instead of badly encoded > chars), but (http-request "http://hzweiblum.livejournal.com/") fails > signaling flexi-stream-encoding-error. Hmm, works for me. > It will be good to have possibility to supply a character that will > be used as a substitution for invalid byte sequence. > > use-value restart is added to the get-char-code function in the > attached patch. I've added your code to the new release. See also the new special variable *SUBSTITUTION-CHAR*. Thanks, Edi. _______________________________________________ flexi-streams-announce mailing list flexi-streams-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/flexi-streams-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From edi at agharta.de Sun Nov 19 20:54:10 2006 From: edi at agharta.de (Edi Weitz) Date: Sun, 19 Nov 2006 21:54:10 +0100 Subject: [portage-overlay-devel] [ann] [hunchentoot-announce] New release 0.4.10 (Was: *http-error-handler* behaviour) In-Reply-To: (Marijn Haverbeke's message of "Sat, 18 Nov 2006 08:47:55 +0100") References: Message-ID: On Sat, 18 Nov 2006 08:47:55 +0100, "Marijn Haverbeke" wrote: > Attached is the patch, I went with the name *handle-http-errors-p* > instead. Thanks a lot - it's in the latest release. Cheers, Edi. _______________________________________________ tbnl-announce site list tbnl-announce at common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From pc at p-cos.net Sun Nov 19 22:14:11 2006 From: pc at p-cos.net (Pascal Costanza) Date: Sun, 19 Nov 2006 23:14:11 +0100 Subject: [portage-overlay-devel] [ann] [cdr-announce] Some changes to the Common Lisp Document Repository. Message-ID: Hello everybody, Based on the constructive feedback we have got on the CDR process so far, we have made some changes to CDR as follows. + First, due to the fact that the CDR process has been described as CDR 0 which has already been finalized, strictly speaking we aren't allowed to make changes to CDR anymore. We have solved this by resubmitting the CDR process itself as CDR 4. You can find the new version at http://cdr.eurolisp.org/document/4/ together with the changes compared to CDR 0 (which are also described below). Since we expect more suggestions for improvement in the near future, we use an exceptionally long initial period for CDR 4 until November 1, 2007. This allows us to make changes as we go along. At the same time, the CDR process in use will already be CDR 4. This means that the CDR process for submitted CDRs until then will be somewhat unstable, but we think that this gives us the advantage of being able to experiment a little such that the final result will hopefully be a better tested process. Consider this equivalent to the bootstrapping of a metacircular software architecture, or to the development of any new piece of software for that matter, where you have to test and change things as you go as well. ;) + We have added more details about submission of accompanying material, especially with regard to licenses that give us the right to publish it at the CDR website and related publications. We forgot about this issue in CDR 0. + We have added a section where we ask authors and submitters to provide rationales for changes they have made during the initial period. From now on, we also intend to add archives of previous versions of a CDR for better traceability of such changes. + We have added a mailing list cdr-discuss - see http://common- lisp.net/cgi-bin/mailman/listinfo/cdr-discuss for the mailing list page. This mailing list is supposed to be used for discussions about specific CDRs. This is especially useful when CDRs are in their initial period, but may also be useful afterwards. The already existing cdr-devel is purely for discussions about issues related to CDR itself (that go beyond the scope of what is described in CDR 0 and CDR 4). We hope that these changes address the suggestions we have got so far. Best, 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 _______________________________________________ cdr-announce mailing list cdr-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From pc at p-cos.net Tue Nov 21 20:20:40 2006 From: pc at p-cos.net (Pascal Costanza) Date: Tue, 21 Nov 2006 21:20:40 +0100 Subject: [portage-overlay-devel] [ann] [cdr-announce] Initial period for CDR 3 prolonged. Message-ID: <9A770ACE-BEC1-49E3-A96E-AD0A81F24B28@p-cos.net> Since the cdr-discuss mailing list is only a few days old, and on request by the author, we have prolonged the initial period before finalization of CDR 3 "Revisiting CONCATENATE-SEQUENCE" by Christophe Rhodes until January 15, 2007. Christophe Rhodes welcomes discussions about this CDR at cdr-discuss to which he is subscribed himself. Please mention CDR 3 in the subject line in your postings about this CDR. 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 _______________________________________________ cdr-announce mailing list cdr-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From pc at p-cos.net Wed Nov 22 10:03:29 2006 From: pc at p-cos.net (Pascal Costanza) Date: Wed, 22 Nov 2006 11:03:29 +0100 Subject: [portage-overlay-devel] [ann] [cdr-announce] Initial period for CDR 2 prolonged. Message-ID: <1A0FE98D-EB85-4777-A041-76525C8BD44B@p-cos.net> Since the cdr-discuss mailing list is only a few days old, and on request by the author, we have prolonged the initial period before finalization of CDR 2 "A generic hash table interface specification for Common Lisp" by Ingvar Mattsson until January 15, 2007. Ingvar Mattsson welcomes discussions about this CDR at cdr-discuss to which he is subscribed himself. Please mention CDR 2 in the subject line in your postings about this CDR. 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 _______________________________________________ cdr-announce mailing list cdr-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From pc at p-cos.net Wed Nov 22 10:14:56 2006 From: pc at p-cos.net (Pascal Costanza) Date: Wed, 22 Nov 2006 11:14:56 +0100 Subject: [portage-overlay-devel] [ann] [cdr-announce] CDR announcements / mailing lists Message-ID: Hi everyone, I have posted the recent two announcements about prolongation of CDRs to all three CDR-related mailing lists. We don't have the intention to post such and similar announcements to all three lists in the future. I have only done this because I assume that currently, people may not be signed up to the appropriate mailing lists, especially because cdr-discuss has only been a recent addition. In the future, we will restrict announcements to cdr-announce exclusively. As advertised, cdr-discuss is for discussion about specific CDRs, and cdr-devel is for discussion about CDR itself. There may be some overlap between cdr-discuss and cdr-devel when it comes to the CDR document describing the CDR process, but I guess this will pose no serious problems. 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 _______________________________________________ cdr-announce mailing list cdr-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From pc at p-cos.net Thu Nov 23 07:13:56 2006 From: pc at p-cos.net (Pascal Costanza) Date: Thu, 23 Nov 2006 08:13:56 +0100 Subject: [portage-overlay-devel] [ann] [cdr-announce] CDR mailing lists via gmane Message-ID: <04F72B6D-BDF3-4302-9691-BBAD5978E5FE@p-cos.net> Hi, The CDR mailing lists are now also available via gmane. They are mapped as follows: cdr-announce => gmane.lisp.cdr.announce cdr-discuss => gmane.lisp.cdr.general cdr-devel => gmane.lisp.cdr.devel See http://gmane.org/ for more information 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 _______________________________________________ cdr-announce mailing list cdr-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cdr-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From nallen05 at gmail.com Sun Nov 26 07:39:09 2006 From: nallen05 at gmail.com (Nick Allen) Date: Sat, 25 Nov 2006 23:39:09 -0800 Subject: [portage-overlay-devel] [ann] [cl-component-announce] ANN: CL-Component Message-ID: I finally got around to uploading the page and darcs repo for Cl-Component, a "simple CLOS solution for directed acyclic graphs". http://common-lisp.net/project/cl-component/ This is what you'd call a "pre-release". I plan to fully rework the API and implementation as soon as I get a chance, but unfortuanatly the project is somewhat on the back-burner right now. Fortuanatly this release features full documentation and unit-tests until then... Comments are welcome, my goal is to make dealing with dags of CLOS instances trivial, and make a useful tool for rolling object systems, system definition utilities, and scheduling utilities. Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- _______________________________________________ cl-component-announce mailing list cl-component-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/cl-component-announce -------------- next part -------------- _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements From edi at agharta.de Thu Nov 30 23:06:18 2006 From: edi at agharta.de (Edi Weitz) Date: Fri, 01 Dec 2006 00:06:18 +0100 Subject: [portage-overlay-devel] [ann] [drakma-announce] New release 0.5.4 Message-ID: ChangeLog: Version 0.5.4 2006-12-01 Workaround for servers which send headers after 100 status line (provided by Donavon Keithley) Download: http://weitz.de/files/drakma.tar.gz Cheers, Edi. _______________________________________________ drakma-announce mailing list drakma-announce at common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/drakma-announce _______________________________________________ announcements site list announcements at common-lisp.net http://common-lisp.net/mailman/listinfo/announcements