From pupeno at pupeno.com  Sun May  1 12:48:05 2005
From: pupeno at pupeno.com (Pupeno)
Date: Sun, 1 May 2005 09:48:05 -0300
Subject: [Bese-devel] Using araneida
Message-ID: <200505010948.07869.pupeno@pupeno.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,
I'm trying to use the Araneida backend. Having a standard UCW (bleeding edge, 
from tla), I just commented:
(use-httpd-backend)
and uncommented 
(use-araneida-backend)
and I've loaded start.lisp.
Everything seems to be fine:
[..............................]
;; Swank started at port: 4005.
2005-05-06T09:42.09 +INFO+ IT.BESE.UCW::UCW-LOGGER: Starting up standard 
server #<STANDARD-SERVER ARANEIDA-BACKEND 2 {A84E739}>.
2005-05-06T09:42.09 +INFO+ IT.BESE.UCW::UCW.BACKEND: Starting up ARANEIDA 
backend #<ARANEIDA-BACKEND {A43A189}> on http://127.0.0.1:8080/

But when I put http://127.0.0.1:8080/ in my browser it goes on forever without 
showing anything, I even tried other URLs: http://127.0.0.1:8080/ucw, 
http://127.0.0.1:8080/ucw/examples, 
http://127.0.0.1:8080/ucw/examples/index.ucw.
Nothing worked.

Any idea ? Should I not use Araneida ?
Thanks.
- -- 
Pupeno: pupeno at pupeno.com - http://pupeno.com
Reading Science Fiction ? http://sfreaders.com.ar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCdNAHfW48a9PWGkURAv0jAJ9V7dyvHvMe8MbdoI8EJh35yBGSFQCfcT0d
tdna87Sx14EkTaCus+WoBr0=
=5ahD
-----END PGP SIGNATURE-----


From mb at bese.it  Sun May  1 13:48:49 2005
From: mb at bese.it (Marco Baringer)
Date: Sun, 01 May 2005 15:48:49 +0200
Subject: [Bese-devel] Using araneida
In-Reply-To: <200505010948.07869.pupeno@pupeno.com> (pupeno@pupeno.com's
	message of "Sun, 1 May 2005 09:48:05 -0300")
References: <200505010948.07869.pupeno@pupeno.com>
Message-ID: <m2mzrfvyym.fsf@soma.local>

Pupeno <pupeno at pupeno.com> writes:

> Hello,
> I'm trying to use the Araneida backend. Having a standard UCW (bleeding edge, 
> from tla), I just commented:
> (use-httpd-backend)
> and uncommented 
> (use-araneida-backend)
> and I've loaded start.lisp.
> Everything seems to be fine:
> [..............................]
> ;; Swank started at port: 4005.
> 2005-05-06T09:42.09 +INFO+ IT.BESE.UCW::UCW-LOGGER: Starting up standard 
> server #<STANDARD-SERVER ARANEIDA-BACKEND 2 {A84E739}>.
> 2005-05-06T09:42.09 +INFO+ IT.BESE.UCW::UCW.BACKEND: Starting up ARANEIDA 
> backend #<ARANEIDA-BACKEND {A43A189}> on http://127.0.0.1:8080/
>
> But when I put http://127.0.0.1:8080/ in my browser it goes on forever without 
> showing anything, I even tried other URLs: http://127.0.0.1:8080/ucw, 
> http://127.0.0.1:8080/ucw/examples, 
> http://127.0.0.1:8080/ucw/examples/index.ucw.
> Nothing worked.
>
> Any idea ? Should I not use Araneida ?

using araneida should "just work," so please keep trying and we'll see
what the issue is. the first thing to do is figure out if this an
araneida issue (possible, but i doubt it), a ucw issue (probably), or
just a setup issue (i'd bet on this).

Since you get no output the first thing i'd suggest doing is uping
ucw's log level, go to bin/utils.lisp find the constant +info+ in
thesetup-logger function and change it to +dribble+. Now we need to
see if the request is getting into araneida, try tracing
araneida:handle-request-response (or you could just put a format
statement in ucw's handle-request-response method (see
src/backend/araneida.lisp)). Assuming the rest of this is "normal"
you'll need to go and see what ucw's doing, the logging output will be
helpfull in doing this so try that first and then get back to me.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From bdowning at lavos.net  Sun May  1 16:32:50 2005
From: bdowning at lavos.net (Brian Downing)
Date: Sun, 1 May 2005 11:32:50 -0500
Subject: [Bese-devel] Using araneida
In-Reply-To: <m2mzrfvyym.fsf@soma.local>;
	from mb@bese.it on Sun, May 01, 2005 at 03:48:49PM +0200
References: <200505010948.07869.pupeno@pupeno.com> <m2mzrfvyym.fsf@soma.local>
Message-ID: <20050501113250.N659@lavos.net>

On Sun, May 01, 2005 at 03:48:49PM +0200, Marco Baringer wrote:
> using araneida should "just work," so please keep trying and we'll see
> what the issue is.

I had a different (intermittent) issue with Araneida which eventually
led me to find a problem in the Araneida backend.

It looks like the backend was written to expect keywords in the header
alist, but there are strings there now.

The result of this was that I was getting "HTTP/1.0 NIL OK" coming out
of it, which occasionally caused my proxy to lose its mind.  I have _no_
idea why it ever worked.

Here are my changes - definitely not the best way to fix it, but it worked
without changing the case logic (as case is always an EQL test).

--- orig/src/backend/araneida.lisp
+++ mod/src/backend/araneida.lisp
@@ -152,7 +152,7 @@
   (let (content-type content-length expires cache-control location refresh
        pragma set-cookie conditional www-authenticate last-modified extra-headers)
   (dolist* (header-cons (headers r))
-    (case (car header-cons)
+    (case (intern (car header-cons) "KEYWORD")
       (:content-type     (setf content-type     (cdr header-cons)))
       (:content-length   (setf content-length   (cdr header-cons)))
       (:expires          (setf expires          (cdr header-cons)))
@@ -167,7 +167,7 @@
       (t (push header-cons extra-headers))))
   (let ((content (get-output-stream-string (content-stream r))))
     (araneida:request-send-headers (request r)
-                                  :response-code (cdr (assoc :status (headers r)))
+                                  :response-code (cdr (assoc "Status" (headers r) :test #'string=))
                                   :content-type (or content-type "text/html")
                                   :content-length (or content-length (length content))
                                   :expires expires



-bcd


From randomtalk at gmail.com  Mon May  2 23:52:05 2005
From: randomtalk at gmail.com (Jason Wang)
Date: Mon, 2 May 2005 19:52:05 -0400
Subject: [Bese-devel] undefined-function parsing request?
In-Reply-To: <m2u0lqc7vz.fsf@soma.local>
References: <20050428193335.I659@lavos.net> <m2u0lqc7vz.fsf@soma.local>
Message-ID: <939cf2005050216525e8577e8@mail.gmail.com>

hi, i just got the latest version of ucw from tla, May 1st, 2005.. the
server is up and running fine. However, when i try to access the
examples page, it gave me a function undefined message: debugger
invoked on a UNDEFINED-FUNCTION in thread 5746:
 The function IT.BESE.UCW::PARSE-REQUEST is undefined.
-- 
www.programer.name - my own personal blog : )


From mb at bese.it  Tue May  3 09:00:37 2005
From: mb at bese.it (Marco Baringer)
Date: Tue, 03 May 2005 11:00:37 +0200
Subject: [Bese-devel] undefined-function parsing request?
In-Reply-To: <939cf2005050216525e8577e8@mail.gmail.com> (Jason Wang's
	message of "Mon, 2 May 2005 19:52:05 -0400")
References: <20050428193335.I659@lavos.net> <m2u0lqc7vz.fsf@soma.local>
	<939cf2005050216525e8577e8@mail.gmail.com>
Message-ID: <m27jigsmyy.fsf@soma.local>

Jason Wang <randomtalk at gmail.com> writes:

> hi, i just got the latest version of ucw from tla, May 1st, 2005.. the
> server is up and running fine. However, when i try to access the
> examples page, it gave me a function undefined message: debugger
> invoked on a UNDEFINED-FUNCTION in thread 5746:
>  The function IT.BESE.UCW::PARSE-REQUEST is undefined.

The function parse-request doesn't exist (anymore). It was removed by
patch-357 which introduced the httpd backend and made the mod_lisp
backend multithreaded. (the latest ucw is ucw--dev--0.3--patch-402)

maybe you have stale fasl files lying around? (it's certainly strange
but i can't, atm, think of anything else)

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From mb at bese.it  Tue May  3 14:24:44 2005
From: mb at bese.it (Marco Baringer)
Date: Tue, 03 May 2005 16:24:44 +0200
Subject: [Bese-devel] UnCommon Web version 0.3.8 - "learning to climb up ice"
Message-ID: <m2oebspetv.fsf@soma.local>


UnCommon Web version 0.3.8 - "learning to climb up ice"
Released 2005-05-03

This release: improves the documentation; adds a completely new
back-end; adds multi-threading support to the mod_lisp back-end; provides
a large number of bug fixes and minor improvements.

* Home page

http://common-lisp.net/project/ucw/

* Download

ftp://ftp.common-lisp.net/pub/project/ucw/ucw_0.3.8.tar.gz
ftp://ftp.common-lisp.net/pub/project/ucw/ucw_0.3.8.tar.bz2

* Changes (since 0.3.7)

** System

- UCW will now attempt to load asdf system definitions manually if
  asdf:*central-registry* isn't properly configured. This should make
  it easier for lisp newbies to start with UCW.

- All the scripts and lisp files required for starting and stopping
  UCW are now in the bin directory. The unused file src/bin.lisp has
  been removed.

- The default log level has been turned down to avoid uninformative
  messages being constantly written to the console.

** RERL

- The Content-Type header is explicitly set in the standard-server's
  handle-request method.

- HTTP headers are now always passed as strings. Automatic
  keyword->string conversion has been eliminated.

** Components

- New REDIRECT component.

- New convenience macro initialize-container.

- *debug-on-error* and *inspect-components* are now exported from the
   UCW package.

** Back-ends

- All back-ends now use the ucw.backend logger, this is much simpler
  than having each backend have its own logger.

- The mod_lisp backend now supports parsing mime encoded POST
  data. The current API is not definitive and will change in the near
  future.

- mod_lisp backend now support multiple worker threads.

- Added httpd backend.

** YACLML/TAL

- <ucw:select :multiple t now works as expected.

- New convenience tags <ucw:text, <ucw:password and <ucw:submit.

- :action attribute now allowed on regular A and INPUT tags in TAL
  files.

** Documentation

- Added the wiki example.

- Improved users manual.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From mb at bese.it  Tue May  3 21:24:19 2005
From: mb at bese.it (Marco Baringer)
Date: Tue, 03 May 2005 23:24:19 +0200
Subject: [Bese-devel] ucw release cycle
Message-ID: <m2d5s8gfzw.fsf@soma.local>


anybody want to help me make a monthly ucw release? 

there's usually enoguh activity in a month to warrant a new minor
release of ucw. i just need someone to prode me into actually doing
it, and help with testing ucw (at least the examples) on the various
platforms.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From der_julian at web.de  Tue May  3 21:33:26 2005
From: der_julian at web.de (Julian Stecklina)
Date: Tue, 3 May 2005 23:33:26 +0200
Subject: [Bese-devel] ucw release cycle
In-Reply-To: <m2d5s8gfzw.fsf@soma.local>
References: <m2d5s8gfzw.fsf@soma.local>
Message-ID: <20050503233326.62e6395c@localhost>

On Tue, 03 May 2005 23:24:19 +0200
"Marco Baringer" <mb at bese.it> wrote:

> anybody want to help me make a monthly ucw release? 
> 
> there's usually enoguh activity in a month to warrant a new minor
> release of ucw. i just need someone to prode me into actually doing
> it, and help with testing ucw (at least the examples) on the various
> platforms.

I probably could test it on CMUCL/FreeBSD, if you like, but I still have
problems with telling arch what to do. ;)

Regards,
-- 
Julian Stecklina

Greenspun's Tenth Rule of Programming: "Any sufficiently complicated C
or Fortran program contains an ad-hoc, informally-specified bug-ridden
slow implementation of half of Common Lisp."


From mb at bese.it  Wed May  4 11:02:02 2005
From: mb at bese.it (Marco Baringer)
Date: Wed, 04 May 2005 13:02:02 +0200
Subject: [Bese-devel] enviroment redux
Message-ID: <m23bt36yqd.fsf@soma.local>


matley (Luigi Panzeri) pointed out that there were a LOT of places, in
ucw, yaclml and arnesi, where i'd misspelt enviroment. I fixed them
all, the patches are all more or less independent so if get one of
these make sure you get the others as well:

ucw--dev--0.3--patch-403
yaclml--dev--0.5--patch-26
arnesi--dev--1.4--patch-5

(bin/update.sh should get all of them for you)

Since i'd misspelt enviroment in macros as well as functions you will
probably need remove all existing fasl files and recompile.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From mb at bese.it  Wed May  4 11:46:43 2005
From: mb at bese.it (Marco Baringer)
Date: Wed, 04 May 2005 13:46:43 +0200
Subject: [Bese-devel] ucw 0.3.9
Message-ID: <m2fyx343j0.fsf@soma.local>


this is for luigi, julian and anyone else who wants to improve the
qualitiy of the "official" ucw releases.

I've commited the spelling fixs and created a new ucw release (0.3.9)
containig those changes and some minor tweaks to the httpd backend
(proper handling of #\+ chars in urls).

So, here's what i would like people to do if they have some free time
(my guess is that it will take between 10 and 30 minutes to do this):

1) Get the tarballs from:

ftp://ftp.common-lisp.net/pub/project/ucw/

[gz and bz2 versions available]

2) Make sure that arnesi and yaclml are included.

3) Make sure that, with asdf properly configured, loading
   bin/start.lisp loads up the httpd backend and example and admin
   apps.

4) make sure the examples work (clik on the countre a bit, maybe mess
   with the presentation stuff).

5) check the contents of CHANGES and see if it makes sense.

6) see if there are any other stupid mistakes (missing files, backup files).

7) tell me what platforms (hardware, os, lisp implementation, backend
   type) it worked (and didn't work) on.

I've set the release date in CHANGES to 2005-05-09 (monday), Hopefully
that's enough time to get feedback and work out any bugs.

thanks in advance.
-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From pjb at informatimago.com  Wed May  4 23:28:38 2005
From: pjb at informatimago.com (Pascal J.Bourguignon)
Date: Thu, 5 May 2005 01:28:38 +0200
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <m2fyx343j0.fsf@soma.local>
References: <m2fyx343j0.fsf@soma.local>
Message-ID: <17017.23206.632105.973953@thalassa.informatimago.com>


Marco Baringer writes:
> 
> this is for luigi, julian and anyone else who wants to improve the
> qualitiy of the "official" ucw releases.
> 
> I've commited the spelling fixs and created a new ucw release (0.3.9)
> containig those changes and some minor tweaks to the httpd backend
> (proper handling of #\+ chars in urls).
> 
> So, here's what i would like people to do if they have some free time
> (my guess is that it will take between 10 and 30 minutes to do this):
> 
> 1) Get the tarballs from:
> 
> ftp://ftp.common-lisp.net/pub/project/ucw/


The release notes should indicate that RFC2388 and ITERATE are new
dependencies.  (This seems to be true already of 0.3.8, so it could go
in these release notes).

Also, there's probably a dependency on an exact version of ITERATE.  I
fetched the "current" one, iterate version 1.3.pre1 and it fails to
compile:


[1]> (load"src/loader")
;; Loading file $PRJ/src/loader.lisp ...
;;  Loading file $PRJ/init.lisp ...
;;  Loaded file $PRJ/init.lisp
;;  Loading file $PACKAGES/com/informatimago/common-lisp/package.lisp ...
;;  Loaded file $PACKAGES/com/informatimago/common-lisp/package.lisp
;;  Loading file $PACKAGES/net/sourceforge/cclan/asdf/asdf.lisp ...
;;  Loaded file $PACKAGES/net/sourceforge/cclan/asdf/asdf.lisp
;; Scanning ASDF packages...
;; Done.
; loading system definition from $PACKAGES/net/common-lisp/ucw/ucw.asd into #<PACKAGE ASDF3859>
;;  Loading file $PACKAGES/net/common-lisp/ucw/ucw.asd ...
; registering #<SYSTEM :UCW #x2044852E> as UCW
; registering #<SYSTEM :UCW.ADMIN #x204832B6> as UCW.ADMIN
; registering #<SYSTEM :UCW.EXAMPLES #x203D3606> as UCW.EXAMPLES
; registering #<SYSTEM :UCW.HTTPD #x203E70E6> as UCW.HTTPD
; registering #<SYSTEM :UCW.MOD-LISP #x203F882E> as UCW.MOD-LISP
; registering #<SYSTEM :UCW.ASERVE #x2040A126> as UCW.ASERVE
; registering #<SYSTEM :UCW.ARANEIDA #x2041C17E> as UCW.ARANEIDA
; registering #<SYSTEM :UCW.CL-ICU #x2042D9FE> as UCW.CL-ICU
; registering #<SYSTEM :UCW.EXAMPLES.I18N #x2043F976> as UCW.EXAMPLES.I18N
;;  Loaded file $PACKAGES/net/common-lisp/ucw/ucw.asd
; loading system definition from $PACKAGES/net/common-lisp/rfc2388/rfc2388.asd into #<PACKAGE ASDF4243>
;;  Loading file $PACKAGES/net/common-lisp/rfc2388/rfc2388.asd ...
; registering #<SYSTEM :RFC2388 #x20486AFE> as RFC2388
;;  Loaded file $PACKAGES/net/common-lisp/rfc2388/rfc2388.asd
; loading system definition from $PACKAGES/net/common-lisp/iterate/iterate.asd into #<PACKAGE ASDF4478>
;;  Loading file $PACKAGES/net/common-lisp/iterate/iterate.asd ...
; registering #<SYSTEM ITERATE #x2044E76E> as ITERATE
; registering #<SYSTEM ITERATE-PG #x2045558E> as ITERATE-PG
; registering #<SYSTEM ITERATE-TESTS #x20466476> as ITERATE-TESTS
;;  Loaded file $PACKAGES/net/common-lisp/iterate/iterate.asd
; loading system definition from $PACKAGES/net/common-lisp/slime/swank.asd into #<PACKAGE ASDF4515>
;;  Loading file $PACKAGES/net/common-lisp/slime/swank.asd ...
; registering #<SYSTEM :SWANK #x204273AE> as SWANK
;;  Loaded file $PACKAGES/net/common-lisp/slime/swank.asd
; loading system definition from $PACKAGES/net/common-lisp/ucw/libs/yaclml/yaclml.asd into #<PACKAGE ASDF4528>
;;  Loading file $PACKAGES/net/common-lisp/ucw/libs/yaclml/yaclml.asd ...
; registering #<SYSTEM :YACLML #x20457846> as YACLML
; registering #<SYSTEM :YACLML.TEST #x20468B56> as YACLML.TEST
;;  Loaded file $PACKAGES/net/common-lisp/ucw/libs/yaclml/yaclml.asd
; loading system definition from $PACKAGES/net/common-lisp/ucw/libs/arnesi/arnesi.asd into #<PACKAGE ASDF4541>
;;  Loading file $PACKAGES/net/common-lisp/ucw/libs/arnesi/arnesi.asd ...
; registering #<SYSTEM :ARNESI #x203E2476> as ARNESI
; registering #<SYSTEM :ARNESI.TEST #x203F9E4E> as ARNESI.TEST
; registering #<SYSTEM :ARNESI.CL-PPCRE-EXTRAS #x2040F2A6> as ARNESI.CL-PPCRE-EXTRAS
;;  Loaded file $PACKAGES/net/common-lisp/ucw/libs/arnesi/arnesi.asd
;; Compiling file $PACKAGES/net/common-lisp/rfc2388/packages.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/rfc2388/packages.fas
;;  Loading file $PACKAGES/net/common-lisp/rfc2388/packages.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/rfc2388/packages.fas
;; Compiling file $PACKAGES/net/common-lisp/rfc2388/rfc2388.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/rfc2388/rfc2388.fas
;; Compiling file $PACKAGES/net/common-lisp/iterate-1.3.pre1/package.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/iterate-1.3.pre1/package.fas
;;  Loading file $PACKAGES/net/common-lisp/iterate-1.3.pre1/package.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/iterate-1.3.pre1/package.fas
;; Compiling file $PACKAGES/net/common-lisp/iterate-1.3.pre1/iterate.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/iterate-1.3.pre1/iterate.fas
;; Compiling file $PACKAGES/net/common-lisp/slime/swank-loader.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/slime/swank-loader.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/packages.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/packages.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/packages.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/packages.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/one-liners.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/one-liners.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/one-liners.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/one-liners.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/accumulation.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/accumulation.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/flow-control.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/flow-control.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/flow-control.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/flow-control.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/io.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/io.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/io.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/io.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/asdf.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/asdf.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/accumulation.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/accumulation.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/list.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/list.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/list.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/list.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/string.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/string.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/string.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/string.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/csv.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/csv.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/compat.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/compat.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/cps.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/cps.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/debug.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/debug.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/decimal-arithmetic.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/decimal-arithmetic.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/defclass-struct.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/defclass-struct.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/hash.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/hash.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/vector.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/vector.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/vector.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/vector.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/http.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/http.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/lambda.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/lambda.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/numbers.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/numbers.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/numbers.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/numbers.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/hash.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/hash.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/log.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/log.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/matcher.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/matcher.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/mopp.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/mopp.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/mopp.fas ...
WARNING: Unimplemented MOP symbol: IT.BESE.ARNESI.MOPP:MAKE-METHOD-LAMBDA
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/mopp.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/mop.lisp ...
WARNING in METHOD-COMBINATION-OPTION-CHECKER in lines 18..91 :
variable AROUND-ORDER is not used.
Misspelled or missing IGNORE declaration?
WARNING in METHOD-COMBINATION-OPTION-CHECKER in lines 18..91 :
variable BEFORE-ORDER is not used.
Misspelled or missing IGNORE declaration?
WARNING in METHOD-COMBINATION-OPTION-CHECKER in lines 18..91 :
variable PRIMARY-ORDER is not used.
Misspelled or missing IGNORE declaration?
WARNING in METHOD-COMBINATION-OPTION-CHECKER in lines 18..91 :
variable AFTER-ORDER is not used.
Misspelled or missing IGNORE declaration?
WARNING in METHOD-COMBINATION-OPTION-CHECKER in lines 18..91 :
variable WRAPPING-ORDER is not used.
Misspelled or missing IGNORE declaration?
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/mop.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203DBE06> on
         #<CL-SOURCE-FILE "mop" #x203DA3EE>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/sequence.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/sequence.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203DBDE6> on
         #<CL-SOURCE-FILE "sequence" #x203DA616>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/sharpl-reader.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/sharpl-reader.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203DBDE6> on
         #<CL-SOURCE-FILE "sharpl-reader" #x203DA6BE>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/specials.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/specials.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203DBDE6> on
         #<CL-SOURCE-FILE "specials" #x203DA766>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/asdf.fas ...
WARNING: The generic function #<STANDARD-GENERIC-FUNCTION ASDF:PERFORM> is
         being modified, but has already been called.
WARNING: The generic function
          #<STANDARD-GENERIC-FUNCTION ASDF:OPERATION-DONE-P>
         is being modified, but has already been called.
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/asdf.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/csv.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/csv.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/compat.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/compat.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/cps.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/cps.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/debug.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/debug.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/decimal-arithmetic.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/decimal-arithmetic.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/defclass-struct.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/defclass-struct.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/http.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/http.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/lambda.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/lambda.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/log.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/log.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/matcher.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/matcher.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/mop.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/mop.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/sequence.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/sequence.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/sharpl-reader.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/sharpl-reader.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/specials.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/arnesi/src/specials.fas
;;  Loading file $PACKAGES/net/common-lisp/iterate-1.3.pre1/iterate.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/iterate-1.3.pre1/iterate.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/packages.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/packages.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203D851E> on
         #<CL-SOURCE-FILE "packages" #x203D7586>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/packages.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/packages.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/attribute-bind.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/attribute-bind.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203D851E> on
         #<CL-SOURCE-FILE "attribute-bind" #x203D76D6>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/attribute-bind.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/attribute-bind.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/yaclml.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/yaclml.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203D849E> on
         #<CL-SOURCE-FILE "yaclml" #x203D75EE>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/yaclml.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/yaclml.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tags/html4.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tags/html4.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203D845E> on
         #<CL-SOURCE-FILE "html4" #x203D782E>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tags/html4.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tags/html4.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tags/standard-yaclml.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tags/standard-yaclml.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203D845E> on
         #<CL-SOURCE-FILE "standard-yaclml" #x203D78D6>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tags/standard-yaclml.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tags/standard-yaclml.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tags/html+.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tags/html+.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203D83DE> on
         #<CL-SOURCE-FILE "html+" #x203D78FE>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tags/html+.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tags/html+.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/bracket-reader.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/bracket-reader.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203D83DE> on
         #<CL-SOURCE-FILE "bracket-reader" #x203D76BE>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/xmls.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/xmls.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203D835E> on
         #<CL-SOURCE-FILE "xmls" #x203D79EE>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/tal-environment.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/tal-environment.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203D835E> on
         #<CL-SOURCE-FILE "tal-environment" #x203D7C8E>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/xmls.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/xmls.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/tal-environment.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/tal-environment.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/compile.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/compile.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203D8126> on
         #<CL-SOURCE-FILE "compile" #x203D789E>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/compile.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/compile.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/generator.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/generator.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203D80E6> on
         #<CL-SOURCE-FILE "generator" #x203D7906>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/handlers.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/handlers.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203D80E6> on
         #<CL-SOURCE-FILE "handlers" #x203D79AE>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/bracket-reader.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/bracket-reader.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/generator.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/generator.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/handlers.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/libs/yaclml/src/tal/handlers.fas
;;  Loading file $PACKAGES/net/common-lisp/slime/swank-loader.fas ...
;;   Loading file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/swank-backend.fas ...
;;   Loaded file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/swank-backend.fas
;;   Loading file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/nregex.fas ...
;;   Loaded file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/nregex.fas
;;   Loading file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/xref.fas ...
;;   Loaded file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/xref.fas
;;   Loading file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/metering.fas ...
;;   Loaded file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/metering.fas
;;   Loading file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/swank-clisp.fas ...
WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in
          #<STANDARD-GENERIC-FUNCTION CALL-WITHOUT-INTERRUPTS>

WARNING: Replacing method #<STANDARD-METHOD NIL> in
          #<STANDARD-GENERIC-FUNCTION LISP-IMPLEMENTATION-TYPE-NAME>

WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in
          #<STANDARD-GENERIC-FUNCTION SET-DEFAULT-DIRECTORY>

WARNING: Replacing method #<STANDARD-METHOD (#<BUILT-IN-CLASS T>)> in
          #<STANDARD-GENERIC-FUNCTION ARGLIST>

WARNING: Replacing method #<STANDARD-METHOD NIL> in
          #<STANDARD-GENERIC-FUNCTION UNPROFILE-ALL>

WARNING: DEFUN/DEFMACRO: redefining function BREAK in
         /local/users/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/swank-clisp.fas,
         was defined in
         $PRJ/clisp-2.33.83-cvs/src/condition.fas
;;   Loaded file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/swank-clisp.fas
;;   Loading file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/swank-gray.fas ...
WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-LINE-COLUMN>
         is being modified, but has already been called.
WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-FORCE-OUTPUT>
         is being modified, but has already been called.
WARNING: The generic function #<STANDARD-GENERIC-FUNCTION STREAM-LINE-COLUMN>
         is being modified, but has already been called.
;;   Loaded file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/swank-gray.fas
;;   Loading file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/swank.fas ...
;;   Loaded file /home/pjb/.slime/fasl/clisp-2.33.83-unix-pc386/swank.fas
WARNING: These Swank interfaces are unimplemented:
         (ACTIVATE-STEPPING ADD-FD-HANDLER ADD-SIGIO-HANDLER ALL-THREADS
         CALLS-WHO
         DISASSEMBLE-FRAME FIND-THREAD GETPID INSPECT-FOR-EMACS
         INTERRUPT-THREAD RECEIVE
         REMOVE-FD-HANDLERS REMOVE-SIGIO-HANDLERS SEND SLDB-BREAK-AT-START
         SLDB-BREAK-ON-RETURN SPAWN THREAD-ID TOGGLE-TRACE WHO-MACROEXPANDS
         WHO-SPECIALIZES)
;;   Loading file /home/pjb/.swank.lisp ...
;;   Loaded file /home/pjb/.swank.lisp
;;  Loaded file $PACKAGES/net/common-lisp/slime/swank-loader.fas
;;  Loading file $PACKAGES/net/common-lisp/rfc2388/rfc2388.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/rfc2388/rfc2388.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/packages.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/packages.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFFB6> on
         #<CL-SOURCE-FILE "packages" #x203BA14E>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/packages.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/packages.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/helpers.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/helpers.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFE46> on
         #<CL-SOURCE-FILE "helpers" #x203BA376>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/loggers.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/loggers.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFE46> on
         #<CL-SOURCE-FILE "loggers" #x203BA41E>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/vars.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/vars.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFE46> on
         #<CL-SOURCE-FILE "vars" #x203BA4C6>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/wall-time.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/wall-time.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFE46> on
         #<CL-SOURCE-FILE "wall-time" #x203BA56E>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/loggers.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/loggers.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/backend/accept.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/backend/accept.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFE06> on
         #<CL-SOURCE-FILE "accept" #x203BA69E>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/backend/protocol.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/backend/protocol.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFE06> on
         #<CL-SOURCE-FILE "protocol" #x203BA746>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/backend/protocol.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/backend/protocol.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/backend/cookie.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/backend/cookie.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFDC6> on
         #<CL-SOURCE-FILE "cookie" #x203BA7AE>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/backend/accept.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/backend/accept.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/backend/cookie.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/backend/cookie.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/helpers.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/helpers.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/vars.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/vars.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/protocol.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/protocol.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFC86> on
         #<CL-SOURCE-FILE "protocol" #x203BAA66>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/protocol.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/protocol.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/conditions.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/conditions.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFC46> on
         #<CL-SOURCE-FILE "conditions" #x203BA86E>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-vars.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-vars.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFC46> on
         #<CL-SOURCE-FILE "standard-vars" #x203BB386>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-classes.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-classes.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFC46> on
         #<CL-SOURCE-FILE "standard-classes" #x203BAB76>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-classes.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-classes.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-vars.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-vars.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-application.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-application.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFBC6> on
         #<CL-SOURCE-FILE "standard-application" #x203BAC86>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-application.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-application.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/cookie-session.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/cookie-session.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFB66> on
         #<CL-SOURCE-FILE "cookie-session" #x203BA8F6>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/backtracking.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/backtracking.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFB66> on
         #<CL-SOURCE-FILE "backtracking" #x203BA99E>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/conditions.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/conditions.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/request-loop-error.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/request-loop-error.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFB26> on
         #<CL-SOURCE-FILE "request-loop-error" #x203BAA6E>.
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-action.lisp ...
;; Wrote file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-action.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x203BFB26> on
         #<CL-SOURCE-FILE "standard-action" #x203BAB7E>.
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/backtracking.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/backtracking.fas
;;  Loading file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-action.fas ...
;;  Loaded file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-action.fas
;; Compiling file $PACKAGES/net/common-lisp/ucw-0.3.9/src/rerl/standard-component/standard-component-class.lisp ...
*** - Iterate, in
      (LET* ((G47836 CLASS))
      ((SETF COMPONENT-CLASS.BACKTRACK-SLOTS)
      (CONS G47837 (COMPONENT-CLASS.BACKTRACK-SLOTS G47836)) G47836)):
      The form
      ((SETF COMPONENT-CLASS.BACKTRACK-SLOTS)
      (CONS G47837 (COMPONENT-CLASS.BACKTRACK-SLOTS G47836)) G47836) is not a
      valid Lisp expression
The following restarts are available:
RETRY          :R1      Retry performing #<ASDF:COMPILE-OP NIL #x203BFB26> on #<ASDF:CL-SOURCE-FILE "standard-component-class" #x203BAEB6>.
ACCEPT         :R2      Continue, treating #<ASDF:COMPILE-OP NIL #x203BFB26> on #<ASDF:CL-SOURCE-FILE "standard-component-class" #x203BAEB6> as having been successful.
SKIP           :R3      skip this form and proceed
STOP           :R4      stop loading file
ABORT          :R5      ABORT
Break 1 UCW[2]> :bt
<1> #<SYSTEM-FUNCTION EXT:SHOW-STACK>
<2> #<COMPILED-FUNCTION SYSTEM::PRINT-BACKTRACE>
<3> #<COMPILED-FUNCTION SYSTEM::DEBUG-BACKTRACE>
<4> #<SYSTEM-FUNCTION SYSTEM::READ-EVAL-PRINT>
<5> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP-2-2>
<6> #<SYSTEM-FUNCTION SYSTEM::SAME-ENV-AS>
<7> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP-2>
<8> #<SYSTEM-FUNCTION SYSTEM::DRIVER>
<9> #<COMPILED-FUNCTION SYSTEM::BREAK-LOOP>
<10> #<SYSTEM-FUNCTION INVOKE-DEBUGGER>
<11> #<SYSTEM-FUNCTION ERROR> 3
<12> #<COMPILED-FUNCTION ITERATE::CLAUSE-ERROR>
<13> #<COMPILED-FUNCTION ITERATE::WALK>
<14> #<COMPILED-FUNCTION ITERATE::WALK-LIST-NCONCING>
<15> #<COMPILED-FUNCTION ITERATE::WALK-LIST>
<16> #<COMPILED-FUNCTION ITERATE::WALK-LET>
<17> #<COMPILED-FUNCTION ITERATE::WALK-SPECIAL-FORM>
<18> #<COMPILED-FUNCTION ITERATE::WALK>
<19> #<COMPILED-FUNCTION ITERATE::WALK-LIST-NCONCING>
<20> #<COMPILED-FUNCTION ITERATE::WALK-LIST>
<21> #<COMPILED-FUNCTION ITERATE::WALK-LET>
<22> #<COMPILED-FUNCTION ITERATE::WALK-SPECIAL-FORM>
<23> #<COMPILED-FUNCTION ITERATE::WALK>
<24> #<COMPILED-FUNCTION ITERATE::WALK-LIST-NCONCING>
<25> #<COMPILED-FUNCTION ITERATE::WALK-LIST>
<26> #<COMPILED-FUNCTION ITERATE::RETURN-CODE-MODIFYING-BODY>
<27> #<COMPILED-FUNCTION ITERATE::WALK-PROGN>
<28> #<COMPILED-FUNCTION ITERATE::WALK-SPECIAL-FORM>
<29> #<COMPILED-FUNCTION ITERATE::WALK>
<30> #<COMPILED-FUNCTION ITERATE::WALK-IF>
<31> #<COMPILED-FUNCTION ITERATE::WALK-SPECIAL-FORM>
<32> #<COMPILED-FUNCTION ITERATE::WALK>
<33> #<COMPILED-FUNCTION ITERATE::WALK-LIST-NCONCING>
<34> #<COMPILED-FUNCTION ITERATE::WALK-LIST>
<35> #<COMPILED-FUNCTION ITERATE::RETURN-CODE-MODIFYING-BODY>
<36> #<COMPILED-FUNCTION ITERATE::WALK-PROGN>
<37> #<COMPILED-FUNCTION ITERATE::WALK-SPECIAL-FORM>
<38> #<COMPILED-FUNCTION ITERATE::WALK>
<39> #<COMPILED-FUNCTION ITERATE::WALK-IF>
<40> #<COMPILED-FUNCTION ITERATE::WALK-SPECIAL-FORM>
<41> #<COMPILED-FUNCTION ITERATE::WALK>
<42> #<COMPILED-FUNCTION ITERATE::WALK-LIST-NCONCING>
<43> #<COMPILED-FUNCTION ITERATE::WALK-LIST>
<44> #<COMPILED-FUNCTION ITER>
<45> #<SYSTEM-FUNCTION FUNCALL> 3
<46> #<COMPILED-FUNCTION SYSTEM::C-FORM>
<47> #<COMPILED-FUNCTION SYSTEM::C-FORM>
<48> #<COMPILED-FUNCTION SYSTEM::C-PROGN>
<49> #<COMPILED-FUNCTION SYSTEM::C-FORM>
<50> #<COMPILED-FUNCTION SYSTEM::C-BLOCK>
<51> #<COMPILED-FUNCTION SYSTEM::C-FORM>
<52> #<COMPILED-FUNCTION SYSTEM::C-PROGN>
<53> #<COMPILED-FUNCTION SYSTEM::C-FORM>
<54> #<COMPILED-FUNCTION SYSTEM::C-LAMBDABODY>
<55> #<COMPILED-FUNCTION SYSTEM::C-FUNCTION>
<56> #<COMPILED-FUNCTION SYSTEM::C-FORM>
<57> #<COMPILED-FUNCTION SYSTEM::C-DIRECT-FUNCTION-CALL>
<58> #<COMPILED-FUNCTION SYSTEM::C-GLOBAL-FUNCTION-CALL>
<59> #<COMPILED-FUNCTION SYSTEM::C-FORM>
<60> #<COMPILED-FUNCTION SYSTEM::C-PROGN>
<61> #<COMPILED-FUNCTION SYSTEM::C-FORM>
<62> #<COMPILED-FUNCTION SYSTEM::C-LET/LET*>
<63> #<COMPILED-FUNCTION #:|(DEFCONSTANT C-FORM-TABLE (LET # # ...))-168-1|>
<64> #<COMPILED-FUNCTION SYSTEM::C-FORM>
<65> #<COMPILED-FUNCTION SYSTEM::C-PROGN>
<66> #<COMPILED-FUNCTION SYSTEM::C-FORM>
<67> #<COMPILED-FUNCTION SYSTEM::C-LAMBDABODY>
<68> #<COMPILED-FUNCTION SYSTEM::COMPILE-LAMBDABODY>
<69> #<COMPILED-FUNCTION SYSTEM::COMPILE-TOPLEVEL-FORM>
<70> #<COMPILED-FUNCTION SYSTEM::COMPILE-TOPLEVEL-FORM>
<71> #<COMPILED-FUNCTION COMPILE-FILE>
<72> #<SPECIAL-OPERATOR MULTIPLE-VALUE-BIND>
EVAL frame for form 
(MULTIPLE-VALUE-BIND (ASDF::OUTPUT ASDF::WARNINGS-P ASDF::FAILURE-P)
 (COMPILE-FILE ASDF:SOURCE-FILE :OUTPUT-FILE ASDF::OUTPUT-FILE)
 (WHEN ASDF::WARNINGS-P
  (CASE (ASDF:OPERATION-ON-WARNINGS ASDF:OPERATION)
   (:WARN
    (WARN "~@<COMPILE-FILE warned while performing ~A on ~A.~@:>" ASDF:OPERATION
     ASDF::C))
   (:ERROR
    (ERROR 'ASDF:COMPILE-WARNED :COMPONENT ASDF::C :OPERATION ASDF:OPERATION))
   (:IGNORE NIL)))
 (WHEN ASDF::FAILURE-P
  (CASE (ASDF:OPERATION-ON-FAILURE ASDF:OPERATION)
   (:WARN
    (WARN "~@<COMPILE-FILE failed while performing ~A on ~A.~@:>" ASDF:OPERATION
     ASDF::C))
   (:ERROR
    (ERROR 'ASDF:COMPILE-FAILED :COMPONENT ASDF::C :OPERATION ASDF:OPERATION))
   (:IGNORE NIL)))
 (UNLESS ASDF::OUTPUT
  (ERROR 'ASDF:COMPILE-ERROR :COMPONENT ASDF::C :OPERATION ASDF:OPERATION)))


-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
I need a new toy.
Tail of black dog keeps good time.
Pounce! Good dog! Good dog!


From mb at bese.it  Thu May  5 11:22:24 2005
From: mb at bese.it (Marco Baringer)
Date: Thu, 05 May 2005 13:22:24 +0200
Subject: [Bese-devel] following along with ucw--dev
Message-ID: <m2acn9nci7.fsf@soma.local>


the arch browser on cl.net was just upgraded to archzoom-0.5.0. If you
want to see what has changed in ucw recently, but don't want to mess
with tla just go to:

http://common-lisp.net/cgi-bin/archzoom.cgi/ucw-2004 at common-lisp.net/ucw--dev--0.3

archzoom provides, among other things, the possibilty of downloading a
tarball of a particular version, per file annotate (ala cvs) and
history (all patches applied to a particular file). i've been using it
locally for quite a while now and its a great way to figure when you
did what (and maybe even why).

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From mb at bese.it  Thu May  5 16:22:45 2005
From: mb at bese.it (Marco Baringer)
Date: Thu, 05 May 2005 18:22:45 +0200
Subject: [Bese-devel] ucw 0.3.9
References: <m2fyx343j0.fsf@soma.local>
	<17017.23206.632105.973953@thalassa.informatimago.com>
Message-ID: <m2is1xlk16.fsf@soma.local>

Pascal J.Bourguignon <pjb at informatimago.com> writes:

> Also, there's probably a dependency on an exact version of ITERATE.  I
> fetched the "current" one, iterate version 1.3.pre1 and it fails to
> compile:

I have _finally_ gotten around to releasing the new version of iterate
(1.4). Its not been announced publicaly but if you re download
iterate-current.tar.gz it should work.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From randomtalk at gmail.com  Thu May  5 23:47:09 2005
From: randomtalk at gmail.com (Jason Wang)
Date: Thu, 5 May 2005 19:47:09 -0400
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <m2is1xlk16.fsf@soma.local>
References: <m2fyx343j0.fsf@soma.local>
	<17017.23206.632105.973953@thalassa.informatimago.com>
	<m2is1xlk16.fsf@soma.local>
Message-ID: <939cf20050505164711bb3e6a@mail.gmail.com>

mmm.. now they give me a new message after i run ./ucwctl start and
./ucwctl attach

;;; attachtty: 1115336641: connecting directly to /var/www/ucw/var/ucw.socket

0] 

ucw still doesn't work :|
-- 
www.programer.name - my own personal blog : )


From pupeno at pupeno.com  Fri May  6 02:11:57 2005
From: pupeno at pupeno.com (Pupeno)
Date: Thu, 5 May 2005 23:11:57 -0300
Subject: [Bese-devel] Iterate ebuild created
Message-ID: <200505052312.00196.pupeno@pupeno.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I have just created a new ebuild (packages for Gentoo) for Iterate 1.4, I've 
submited and it can be found here: 
http://bugs.gentoo.org/show_bug.cgi?id=91636
I hope it'll soon will get its way into portage and we are one step closer to 
having an UCW ebuild :)
Thank you.
- -- 
Pupeno: pupeno at pupeno.com - http://pupeno.com
Reading Science Fiction ? http://sfreaders.com.ar

PS: For those interesting in tracking the process of the UCW ebuild, you can 
do it on: http://bugs.gentoo.org/show_bug.cgi?id=87377
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCetJwfW48a9PWGkURAtSYAKCRUj5sFH74YlMaTVbpqYYCo8lqSQCfRaE6
9/GY4KWq6zZuWrjbm47rIDU=
=QW11
-----END PGP SIGNATURE-----


From randomtalk at gmail.com  Thu May  5 23:48:21 2005
From: randomtalk at gmail.com (Jason Wang)
Date: Thu, 5 May 2005 19:48:21 -0400
Subject: [Bese-devel] connecting directly to socket?
In-Reply-To: <m2is1xlk16.fsf@soma.local>
References: <m2fyx343j0.fsf@soma.local>
	<17017.23206.632105.973953@thalassa.informatimago.com>
	<m2is1xlk16.fsf@soma.local>
Message-ID: <939cf2005050516487ba14dc0@mail.gmail.com>

mmm.. now they give me a new message after i run ./ucwctl start and
./ucwctl attach

;;; attachtty: 1115336641: connecting directly to /var/www/ucw/var/ucw.socket

0]

ucw still doesn't work :|

thanks :D


From pupeno at pupeno.com  Fri May  6 02:47:15 2005
From: pupeno at pupeno.com (Pupeno)
Date: Thu, 5 May 2005 23:47:15 -0300
Subject: [Bese-devel] New README
Message-ID: <200505052347.17988.pupeno@pupeno.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sorry for not attaching a patch instead of the full file, but I couldn't 
figure it out how to make it with tla, yet.
So here it is, a new README, stating the need for iterate.
See you.
- -- 
Pupeno: pupeno at pupeno.com - http://pupeno.com
Reading Science Fiction ? http://sfreaders.com.ar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCetq1fW48a9PWGkURAhGCAKCQwSgZUml22FuMe73dO+5sUkgtJwCgjhQF
BQR5SY7HvFpFkqkv7PPpa5c=
=lfvo
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: README
Type: text/x-diff
Size: 7927 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/bese-devel/attachments/20050505/97ee424b/attachment.diff>

From mb at bese.it  Fri May  6 06:01:53 2005
From: mb at bese.it (Marco Baringer)
Date: Fri, 06 May 2005 08:01:53 +0200
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <939cf20050505164711bb3e6a@mail.gmail.com> (Jason Wang's
	message of "Thu, 5 May 2005 19:47:09 -0400")
References: <m2fyx343j0.fsf@soma.local>
	<17017.23206.632105.973953@thalassa.informatimago.com>
	<m2is1xlk16.fsf@soma.local> <939cf20050505164711bb3e6a@mail.gmail.com>
Message-ID: <m2oeboriy6.fsf@soma.local>

Jason Wang <randomtalk at gmail.com> writes:

> mmm.. now they give me a new message after i run ./ucwctl start and
> ./ucwctl attach
>
> ;;; attachtty: 1115336641: connecting directly to /var/www/ucw/var/ucw.socket
>
> 0] 

that looks like a debug prompt. try typing backtrace (or see what's in
ucw/logs/ucw.dribble which should contain all the output which went by
between ucwctl start and ucwctl attach)

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From mb at bese.it  Fri May  6 06:13:01 2005
From: mb at bese.it (Marco Baringer)
Date: Fri, 06 May 2005 08:13:01 +0200
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <m2oeboriy6.fsf@soma.local> (Marco Baringer's message of "Fri,
	06 May 2005 08:01:53 +0200")
References: <m2fyx343j0.fsf@soma.local>
	<17017.23206.632105.973953@thalassa.informatimago.com>
	<m2is1xlk16.fsf@soma.local> <939cf20050505164711bb3e6a@mail.gmail.com>
	<m2oeboriy6.fsf@soma.local>
Message-ID: <m2br7orifm.fsf@soma.local>

"Marco Baringer" <mb at bese.it> writes:

> Jason Wang <randomtalk at gmail.com> writes:
>
>> mmm.. now they give me a new message after i run ./ucwctl start and
>> ./ucwctl attach
>>
>> ;;; attachtty: 1115336641: connecting directly to /var/www/ucw/var/ucw.socket
>>
>> 0] 
>
> that looks like a debug prompt. try typing backtrace (or see what's in
> ucw/logs/ucw.dribble which should contain all the output which went by
> between ucwctl start and ucwctl attach)

and, if it is in fact a debug prompt, typing error will get sbcl to
print out the condition and its description.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From mb at bese.it  Fri May  6 06:12:09 2005
From: mb at bese.it (Marco Baringer)
Date: Fri, 06 May 2005 08:12:09 +0200
Subject: [Bese-devel] New README
In-Reply-To: <200505052347.17988.pupeno@pupeno.com> (pupeno@pupeno.com's
	message of "Thu, 5 May 2005 23:47:15 -0300")
References: <200505052347.17988.pupeno@pupeno.com>
Message-ID: <m2fyx0rih2.fsf@soma.local>

Pupeno <pupeno at pupeno.com> writes:

> --Boundary-00=_1qteC/G9EP+mRWD
> Content-Type: text/plain;
>   charset="utf-8"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> Sorry for not attaching a patch instead of the full file, but I couldn't 
> figure it out how to make it with tla, yet.

$ tla file-diffs README > README.patch

or

$ tla changes -o DIRNAME
$ tar -jcf DIRNAME.tar.gz

then send an email and attach DIRNAME.tar.gz. The later is preferable
if you change multiple files or if you create/delete files and/or
directories. However even full files, like you did, or not a problem
for me and i'd much much prefer that people spend time fixing ucw than
messing with tla.

> So here it is, a new README, stating the need for iterate.
> See you.

applied, thanks.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From bdowning at lavos.net  Fri May  6 15:12:18 2005
From: bdowning at lavos.net (Brian Downing)
Date: Fri, 6 May 2005 10:12:18 -0500
Subject: [Bese-devel] Using araneida
In-Reply-To: <20050501113250.N659@lavos.net>;
	from bdowning@lavos.net on Sun, May 01, 2005 at 11:32:50AM -0500
References: <200505010948.07869.pupeno@pupeno.com> <m2mzrfvyym.fsf@soma.local>
	<20050501113250.N659@lavos.net>
Message-ID: <20050506101218.G659@lavos.net>

On Sun, May 01, 2005 at 11:32:50AM -0500, Brian Downing wrote:
> --- orig/src/backend/araneida.lisp
> +++ mod/src/backend/araneida.lisp
> @@ -152,7 +152,7 @@
>    (let (content-type content-length expires cache-control location refresh
>         pragma set-cookie conditional www-authenticate last-modified extra-headers)
>    (dolist* (header-cons (headers r))
> -    (case (car header-cons)
> +    (case (intern (car header-cons) "KEYWORD")
>        (:content-type     (setf content-type     (cdr header-cons)))
>        (:content-length   (setf content-length   (cdr header-cons)))
>        (:expires          (setf expires          (cdr header-cons)))

This won't work, of course - I don't know what I was thinking.

-bcd


From mb at bese.it  Fri May  6 15:34:27 2005
From: mb at bese.it (Marco Baringer)
Date: Fri, 06 May 2005 17:34:27 +0200
Subject: [Bese-devel] Using araneida
In-Reply-To: <20050506101218.G659@lavos.net> (Brian Downing's message of
	"Fri, 6 May 2005 10:12:18 -0500")
References: <200505010948.07869.pupeno@pupeno.com> <m2mzrfvyym.fsf@soma.local>
	<20050501113250.N659@lavos.net> <20050506101218.G659@lavos.net>
Message-ID: <m24qdgnzb0.fsf@soma.local>

Brian Downing <bdowning at lavos.net> writes:

> On Sun, May 01, 2005 at 11:32:50AM -0500, Brian Downing wrote:
>> --- orig/src/backend/araneida.lisp
>> +++ mod/src/backend/araneida.lisp
>> @@ -152,7 +152,7 @@
>>    (let (content-type content-length expires cache-control location refresh
>>         pragma set-cookie conditional www-authenticate last-modified extra-headers)
>>    (dolist* (header-cons (headers r))
>> -    (case (car header-cons)
>> +    (case (intern (car header-cons) "KEYWORD")
>>        (:content-type     (setf content-type     (cdr header-cons)))
>>        (:content-length   (setf content-length   (cdr header-cons)))
>>        (:expires          (setf expires          (cdr header-cons)))
>
> This won't work, of course - I don't know what I was thinking.

I just applied what I believe to be a "proper" fix to this (ucw
doesn't try to use keywords for header names anymore so i was able to
delete some code while i was in that file): ucw--dev--0.3--patch-410.
can you try it and tell me what you think?

p.s. - the log and the diffs for that patch can be viewed at:

http://common-lisp.net/cgi-bin/archzoom.cgi/ucw-2004 at common-lisp.net/ucw--dev--0.3--patch-410?log

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From bdowning at lavos.net  Fri May  6 15:44:43 2005
From: bdowning at lavos.net (Brian Downing)
Date: Fri, 6 May 2005 10:44:43 -0500
Subject: [Bese-devel] Using araneida
In-Reply-To: <m24qdgnzb0.fsf@soma.local>;
	from mb@bese.it on Fri, May 06, 2005 at 05:34:27PM +0200
References: <200505010948.07869.pupeno@pupeno.com> <m2mzrfvyym.fsf@soma.local>
	<20050501113250.N659@lavos.net> <20050506101218.G659@lavos.net>
	<m24qdgnzb0.fsf@soma.local>
Message-ID: <20050506104443.H659@lavos.net>

On Fri, May 06, 2005 at 05:34:27PM +0200, Marco Baringer wrote:
> I just applied what I believe to be a "proper" fix to this (ucw
> doesn't try to use keywords for header names anymore so i was able to
> delete some code while i was in that file): ucw--dev--0.3--patch-410.
> can you try it and tell me what you think?

I'm not at home now to try it, but the :response-code is still broken,
which was my primary problem (browsers don't accept "HTTP/1.1 NIL OK" for
some reason.  :)

(araneida:request-send-headers (request r)
                               :response-code (cdr (assoc :status (headers r)))
			       ...)

-bcd


From mb at bese.it  Fri May  6 15:56:29 2005
From: mb at bese.it (Marco Baringer)
Date: Fri, 06 May 2005 17:56:29 +0200
Subject: [Bese-devel] Using araneida
In-Reply-To: <20050506104443.H659@lavos.net> (Brian Downing's message of
	"Fri, 6 May 2005 10:44:43 -0500")
References: <200505010948.07869.pupeno@pupeno.com> <m2mzrfvyym.fsf@soma.local>
	<20050501113250.N659@lavos.net> <20050506101218.G659@lavos.net>
	<m24qdgnzb0.fsf@soma.local> <20050506104443.H659@lavos.net>
Message-ID: <m2wtqcmjpu.fsf@soma.local>

Brian Downing <bdowning at lavos.net> writes:

> I'm not at home now to try it, but the :response-code is still broken,
> which was my primary problem (browsers don't accept "HTTP/1.1 NIL OK" for
> some reason.  :)

what's wrong with them?!?! :)

> (araneida:request-send-headers (request r)
>                                :response-code (cdr (assoc :status (headers r)))
> 			       ...)

ucw--dev--0.3--patch-411 stops curl from warning, we're getting there...


-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From bdowning at lavos.net  Sat May  7 00:06:41 2005
From: bdowning at lavos.net (Brian Downing)
Date: Fri, 6 May 2005 19:06:41 -0500
Subject: [Bese-devel] Using araneida
In-Reply-To: <m2wtqcmjpu.fsf@soma.local>;
	from mb@bese.it on Fri, May 06, 2005 at 05:56:29PM +0200
References: <200505010948.07869.pupeno@pupeno.com> <m2mzrfvyym.fsf@soma.local>
	<20050501113250.N659@lavos.net> <20050506101218.G659@lavos.net>
	<m24qdgnzb0.fsf@soma.local> <20050506104443.H659@lavos.net>
	<m2wtqcmjpu.fsf@soma.local>
Message-ID: <20050506190640.K659@lavos.net>

On Fri, May 06, 2005 at 05:56:29PM +0200, Marco Baringer wrote:
> Brian Downing <bdowning at lavos.net> writes:
> > I'm not at home now to try it, but the :response-code is still broken,
> > which was my primary problem (browsers don't accept "HTTP/1.1 NIL OK" for
> > some reason.  :)
> 
> what's wrong with them?!?! :)
> 
> ucw--dev--0.3--patch-411 stops curl from warning, we're getting there...

Seems to work for me, too, with my silly application.

-bcd


From pupeno at pupeno.com  Sat May  7 16:03:30 2005
From: pupeno at pupeno.com (Pupeno)
Date: Sat, 7 May 2005 13:03:30 -0300
Subject: [Bese-devel] More iterate-related patch
Message-ID: <200505071303.34101.pupeno@pupeno.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The update script was trying to update iterate, which is no longer part of the 
'ucw distribution', so, I patched, and attached it.
- -- 
Pupeno: pupeno at pupeno.com - http://pupeno.com
Reading Science Fiction ? http://sfreaders.com.ar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCfObWfW48a9PWGkURAqV/AJ4k6VdT+MeyFFvvQVaPc62/eHXGBwCdFkTj
cM3vYaGcMinRUeLoivPSiHM=
=D10E
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: update.sh.patch
Type: text/x-diff
Size: 309 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/bese-devel/attachments/20050507/973f3a57/attachment.patch>

From mb at bese.it  Sat May  7 17:38:40 2005
From: mb at bese.it (Marco Baringer)
Date: Sat, 07 May 2005 19:38:40 +0200
Subject: [Bese-devel] More iterate-related patch
In-Reply-To: <200505071303.34101.pupeno@pupeno.com> (pupeno@pupeno.com's
	message of "Sat, 7 May 2005 13:03:30 -0300")
References: <200505071303.34101.pupeno@pupeno.com>
Message-ID: <m23bsz6in3.fsf@soma.local>

Pupeno <pupeno at pupeno.com> writes:

> The update script was trying to update iterate, which is no longer part of the 
> 'ucw distribution', so, I patched, and attached it.

thanks. applied.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From mb at bese.it  Sat May  7 17:54:20 2005
From: mb at bese.it (Marco Baringer)
Date: Sat, 07 May 2005 19:54:20 +0200
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <939cf20050507104229b6ae7f@mail.gmail.com> (Jason Wang's
	message of "Sat, 7 May 2005 13:42:01 -0400")
References: <m2fyx343j0.fsf@soma.local>
	<17017.23206.632105.973953@thalassa.informatimago.com>
	<m2is1xlk16.fsf@soma.local> <939cf20050505164711bb3e6a@mail.gmail.com>
	<m2oeboriy6.fsf@soma.local> <m2br7orifm.fsf@soma.local>
	<939cf20050507104229b6ae7f@mail.gmail.com>
Message-ID: <m2wtqa6hwz.fsf@soma.local>

Jason Wang <randomtalk at gmail.com> writes:

>   Unable to find the system for :ARNESI.
> asdf:*central-registry* is ((MERGE-PATHNAMES ".clc/systems/"
>                                              (USER-HOMEDIR-PATHNAME))
>                             #P"/usr/share/common-lisp/systems/"
>                             (MERGE-PATHNAMES ".sbcl/systems/"
>                                              (USER-HOMEDIR-PATHNAME))
>                             (MERGE-PATHNAMES "site-systems/"
>                                              (TRUENAME
>                                               (POSIX-GETENV "SBCL_HOME")))
>                             (MERGE-PATHNAMES "systems/"
>                                              (TRUENAME
>                                               (POSIX-GETENV "SBCL_HOME")))
>                             *DEFAULT-PATHNAME-DEFAULTS*).

andf needs to know about the ucw/systems/ directory, apparently it
does not. add something like this:

(pushnew "/path/to/ucw/systems/" asdf:*central-registry* :test #'string=)

to your .sbclrc

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From randomtalk at gmail.com  Sat May  7 17:42:01 2005
From: randomtalk at gmail.com (Jason Wang)
Date: Sat, 7 May 2005 13:42:01 -0400
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <m2br7orifm.fsf@soma.local>
References: <m2fyx343j0.fsf@soma.local>
	<17017.23206.632105.973953@thalassa.informatimago.com>
	<m2is1xlk16.fsf@soma.local> <939cf20050505164711bb3e6a@mail.gmail.com>
	<m2oeboriy6.fsf@soma.local> <m2br7orifm.fsf@soma.local>
Message-ID: <939cf20050507104229b6ae7f@mail.gmail.com>

mmm.. that is indeed an error.. when i typed in error in sbcl, it
prints the following:

;;; attachtty: 1115487479: connecting directly to /var/www/ucw/var/ucw.socket

0] error
Error during processing of --eval option "(|LOAD|
\"/var/www/ucw/bin/start.lisp\")":

  Unable to find the system for :ARNESI.
asdf:*central-registry* is ((MERGE-PATHNAMES ".clc/systems/"
                                             (USER-HOMEDIR-PATHNAME))
                            #P"/usr/share/common-lisp/systems/"
                            (MERGE-PATHNAMES ".sbcl/systems/"
                                             (USER-HOMEDIR-PATHNAME))
                            (MERGE-PATHNAMES "site-systems/"
                                             (TRUENAME
                                              (POSIX-GETENV "SBCL_HOME")))
                            (MERGE-PATHNAMES "systems/"
                                             (TRUENAME
                                              (POSIX-GETENV "SBCL_HOME")))
                            *DEFAULT-PATHNAME-DEFAULTS*).
Are the symlinks and asdf:*central-registry* properly setup?
restarts (invokable by number or by possibly-abbreviated name):
  0: [CONTINUE] Ignore and continue with next --eval option.
  1: [ABORT   ] Skip rest of --eval options.
  2:            Skip to toplevel READ/EVAL/PRINT loop.
  3: [QUIT    ] Quit SBCL (calling #'QUIT, killing the process).

apparently a system is missing..  but when i go into the system
folder, the required file is there :| anyone know what's wrong?
-- 
www.programer.name - my own personal blog : )


From randomtalk at gmail.com  Sat May  7 19:27:42 2005
From: randomtalk at gmail.com (Jason Wang)
Date: Sat, 7 May 2005 15:27:42 -0400
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <m2wtqa6hwz.fsf@soma.local>
References: <m2fyx343j0.fsf@soma.local>
	<17017.23206.632105.973953@thalassa.informatimago.com>
	<m2is1xlk16.fsf@soma.local> <939cf20050505164711bb3e6a@mail.gmail.com>
	<m2oeboriy6.fsf@soma.local> <m2br7orifm.fsf@soma.local>
	<939cf20050507104229b6ae7f@mail.gmail.com> <m2wtqa6hwz.fsf@soma.local>
Message-ID: <939cf2005050712274fd1ea20@mail.gmail.com>

On 5/7/05, Marco Baringer <mb at bese.it> wrote:
> Jason Wang <randomtalk at gmail.com> writes:
> 
> >   Unable to find the system for :ARNESI.
> > asdf:*central-registry* is ((MERGE-PATHNAMES ".clc/systems/"
> >                                              (USER-HOMEDIR-PATHNAME))
> >                             #P"/usr/share/common-lisp/systems/"
> >                             (MERGE-PATHNAMES ".sbcl/systems/"
> >                                              (USER-HOMEDIR-PATHNAME))
> >                             (MERGE-PATHNAMES "site-systems/"
> >                                              (TRUENAME
> >                                               (POSIX-GETENV "SBCL_HOME")))
> >                             (MERGE-PATHNAMES "systems/"
> >                                              (TRUENAME
> >                                               (POSIX-GETENV "SBCL_HOME")))
> >                             *DEFAULT-PATHNAME-DEFAULTS*).
> 
> andf needs to know about the ucw/systems/ directory, apparently it
> does not. add something like this:
> 
> (pushnew "/path/to/ucw/systems/" asdf:*central-registry* :test #'string=)
> 
> to your .sbclrc
> 

mmm.. i can't find my .sbclrc, i have no idea where the debian package
might have put the file.. i searched online, the man page said that
/etc/sbclrc and /usr/local/etc/sbclrc are the standard locations for
system-wide SBCL initialization files, unless overridden by the
SBCL_HOME variable or the --sysinit command line option. Though, i
can't find it in these folders, even with show hidden files turned
on..

so i put the (pushnew "/path/to/ucw/systems/" asdf:*central-registry*
:test #'string=) replacing /path/to/ucw/systems/ to my own path..
after i run the script, they give me a different error:
;;; attachtty: 1115494031: connecting directly to /var/www/ucw/var/ucw.socket

0] error
Error during processing of --eval option "(|LOAD|
\"/var/www/ucw/bin/start.lisp\")":

  The value (MERGE-PATHNAMES ".clc/systems/" (USER-HOMEDIR-PATHNAME))
  is not of type
    (OR (VECTOR CHARACTER) (VECTOR NIL) BASE-STRING SYMBOL CHARACTER).
restarts (invokable by number or by possibly-abbreviated name):
  0: [CONTINUE] Ignore and continue with next --eval option.
  1: [ABORT   ] Skip rest of --eval options.
  2:            Skip to toplevel READ/EVAL/PRINT loop.
  3: [QUIT    ] Quit SBCL (calling #'QUIT, killing the process).

anyone know what's going on?

-- 
www.programer.name - my own personal blog : )


From der_julian at web.de  Sun May  8 03:26:30 2005
From: der_julian at web.de (Julian Stecklina)
Date: Sun, 8 May 2005 05:26:30 +0200
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <m2fyx343j0.fsf@soma.local>
References: <m2fyx343j0.fsf@soma.local>
Message-ID: <20050508052630.13f86558@localhost>

On Wed, 04 May 2005 13:46:43 +0200
"Marco Baringer" <mb at bese.it> wrote:

> 7) tell me what platforms (hardware, os, lisp implementation, backend
>    type) it worked (and didn't work) on.

Works perfectly on CMUCL 19a on FreeBSD 5.4 (x86) with the paserve
backend. The httpd backend works as well, but the examples application
looks somewhat different: The example index is at the top of the page,
no border around the links. If I have time I am going to look into this
later today.

Regards,
-- 
Julian Stecklina

Greenspun's Tenth Rule of Programming: "Any sufficiently complicated C
or Fortran program contains an ad-hoc, informally-specified bug-ridden
slow implementation of half of Common Lisp."


From der_julian at web.de  Sun May  8 15:00:29 2005
From: der_julian at web.de (Julian Stecklina)
Date: Sun, 8 May 2005 17:00:29 +0200
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <m2fyx343j0.fsf@soma.local>
References: <m2fyx343j0.fsf@soma.local>
Message-ID: <20050508170029.0be18d81@localhost>

On Wed, 04 May 2005 13:46:43 +0200
"Marco Baringer" <mb at bese.it> wrote:

> 6) see if there are any other stupid mistakes (missing files, backup
> files).

The version info in systems/ucw.asd needs to be updated.

Regards,
-- 
Julian Stecklina

Greenspun's Tenth Rule of Programming: "Any sufficiently complicated C
or Fortran program contains an ad-hoc, informally-specified bug-ridden
slow implementation of half of Common Lisp."


From rm at fabula.de  Sun May  8 17:52:54 2005
From: rm at fabula.de (rm at fabula.de)
Date: Sun, 8 May 2005 19:52:54 +0200
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <20050508052630.13f86558@localhost>
References: <m2fyx343j0.fsf@soma.local> <20050508052630.13f86558@localhost>
Message-ID: <20050508175254.GA15304@seid-online.de>

On Sun, May 08, 2005 at 05:26:30AM +0200, Julian Stecklina wrote:
> On Wed, 04 May 2005 13:46:43 +0200
> "Marco Baringer" <mb at bese.it> wrote:
> 
> > 7) tell me what platforms (hardware, os, lisp implementation, backend
> >    type) it worked (and didn't work) on.
> 
> Works perfectly on CMUCL 19a on FreeBSD 5.4 (x86) with the paserve
> backend. The httpd backend works as well, but the examples application
> looks somewhat different: The example index is at the top of the page,
> no border around the links. If I have time I am going to look into this
> later today.

At least the sample application (/ucw/examples...) seems to funtion with
sbcl 0.9 on x86 (Linux/Debian). Somehow the stylesheet isn't found so
the pages look kind of erm 80s style :-)

 Cheers Ralf Mattes

P.S: Will test later on sbcl 0.9/PPC and OpenMCL ...

> Regards,
> -- 
> Julian Stecklina
> 
> Greenspun's Tenth Rule of Programming: "Any sufficiently complicated C
> or Fortran program contains an ad-hoc, informally-specified bug-ridden
> slow implementation of half of Common Lisp."
> _______________________________________________
> bese-devel mailing list
> bese-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/bese-devel


From der_julian at web.de  Sun May  8 19:54:28 2005
From: der_julian at web.de (Julian Stecklina)
Date: Sun, 8 May 2005 21:54:28 +0200
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <20050508175254.GA15304@seid-online.de>
References: <m2fyx343j0.fsf@soma.local> <20050508052630.13f86558@localhost>
	<20050508175254.GA15304@seid-online.de>
Message-ID: <20050508215428.123336e0@localhost>

On Sun, 8 May 2005 19:52:54 +0200
rm at fabula.de wrote:

> On Sun, May 08, 2005 at 05:26:30AM +0200, Julian Stecklina wrote:
> > On Wed, 04 May 2005 13:46:43 +0200
> > "Marco Baringer" <mb at bese.it> wrote:
> > 
> > > 7) tell me what platforms (hardware, os, lisp implementation,
> > > backend
> > >    type) it worked (and didn't work) on.
> > 
> > Works perfectly on CMUCL 19a on FreeBSD 5.4 (x86) with the paserve
> > backend. The httpd backend works as well, but the examples
> > application looks somewhat different: The example index is at the
> > top of the page, no border around the links. If I have time I am
> > going to look into this later today.
> 
> At least the sample application (/ucw/examples...) seems to funtion
> with sbcl 0.9 on x86 (Linux/Debian). Somehow the stylesheet isn't
> found so the pages look kind of erm 80s style :-)

Yes, I had the same problem with my own application. Somehow ucw is
picky about the www-roots. I cannot pinpoint the problem, though.

Regards,
-- 
Julian Stecklina

Greenspun's Tenth Rule of Programming: "Any sufficiently complicated C
or Fortran program contains an ad-hoc, informally-specified bug-ridden
slow implementation of half of Common Lisp."


From mb at bese.it  Sun May  8 20:39:34 2005
From: mb at bese.it (Marco Baringer)
Date: Sun, 08 May 2005 22:39:34 +0200
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <20050508215428.123336e0@localhost> (Julian Stecklina's message
	of "Sun, 8 May 2005 21:54:28 +0200")
References: <m2fyx343j0.fsf@soma.local> <20050508052630.13f86558@localhost>
	<20050508175254.GA15304@seid-online.de>
	<20050508215428.123336e0@localhost>
Message-ID: <m2is1to3jt.fsf@soma.local>

Julian Stecklina <der_julian at web.de> writes:

> Yes, I had the same problem with my own application. Somehow ucw is
> picky about the www-roots. I cannot pinpoint the problem, though.

would it be worth to teach the httpd backend about static files (which
amounts to implemneting publish-directory) before calling it 0.3.9? At
the some time i could sit down and attempt to document how ucw uses
www-roots and publish-directory.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From ats at acm.org  Sun May  8 20:46:53 2005
From: ats at acm.org (Alan Shutko)
Date: Sun, 08 May 2005 15:46:53 -0500
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <20050508215428.123336e0@localhost> (Julian Stecklina's message
	of "Sun, 8 May 2005 21:54:28 +0200")
References: <m2fyx343j0.fsf@soma.local> <20050508052630.13f86558@localhost>
	<20050508175254.GA15304@seid-online.de>
	<20050508215428.123336e0@localhost>
Message-ID: <87mzr5qwci.fsf@vera.springies.com>

Julian Stecklina <der_julian at web.de> writes:

> Yes, I had the same problem with my own application. Somehow ucw is
> picky about the www-roots. I cannot pinpoint the problem, though.

I think it's just the httpd backend... it works fine under araneida.

ISTR that the httpd backend doesn't support publish-directory yet?

-- 
Alan Shutko <ats at acm.org> - I am the rocks.
Indianapolis 500 pit crews DO IT under 21 seconds.<--= Unhappy women!


From pupeno at pupeno.com  Sun May  8 21:34:42 2005
From: pupeno at pupeno.com (Pupeno)
Date: Sun, 8 May 2005 18:34:42 -0300
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <m2is1to3jt.fsf@soma.local>
References: <m2fyx343j0.fsf@soma.local> <20050508215428.123336e0@localhost>
	<m2is1to3jt.fsf@soma.local>
Message-ID: <200505081834.44858.pupeno@pupeno.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Je Diman?o Majo 8 2005 17:39, Marco Baringer skribis:
> would it be worth to teach the httpd backend about static files (which
> amounts to implemneting publish-directory) before calling it 0.3.9? At
> the some time i could sit down and attempt to document how ucw uses
> www-roots and publish-directory.
I think that you'd be repeating what's done in araneida and aserve, that is, 
wasting time in codding something that was already codded.
Maybe an option would be to choose either araneida or aserve, whatever is best 
from your perspective, as the default backend and claim it as a dependency of 
UCW (that's not bad, it's easy to install araneida or aserve, and asdf makes 
it easier).
That's my point of view.
- -- 
Pupeno: pupeno at pupeno.com - http://pupeno.com
Reading Science Fiction ? http://sfreaders.com.ar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCfoX0fW48a9PWGkURAhrsAJ9UKQADMzPmgNK5SzIXg+pDlZUaMwCcCdfp
v8Noww36TseWE+8me61WNDY=
=mUhs
-----END PGP SIGNATURE-----


From rm at fabula.de  Sun May  8 21:34:49 2005
From: rm at fabula.de (rm at fabula.de)
Date: Sun, 8 May 2005 23:34:49 +0200
Subject: [Bese-devel] ucw 0.3.9
In-Reply-To: <200505081834.44858.pupeno@pupeno.com>
References: <m2fyx343j0.fsf@soma.local> <20050508215428.123336e0@localhost>
	<m2is1to3jt.fsf@soma.local> <200505081834.44858.pupeno@pupeno.com>
Message-ID: <20050508213449.GC15304@seid-online.de>

On Sun, May 08, 2005 at 06:34:42PM -0300, Pupeno wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Je Diman??o Majo 8 2005 17:39, Marco Baringer skribis:
> > would it be worth to teach the httpd backend about static files (which
> > amounts to implemneting publish-directory) before calling it 0.3.9? At
> > the some time i could sit down and attempt to document how ucw uses
> > www-roots and publish-directory.
> I think that you'd be repeating what's done in araneida and aserve, that is, 
> wasting time in codding something that was already codded.
> Maybe an option would be to choose either araneida or aserve, whatever is best 
> from your perspective, as the default backend and claim it as a dependency of 
> UCW (that's not bad, it's easy to install araneida or aserve, and asdf makes 
> it easier).
> That's my point of view.

Yes, but araneida has _major_ problems with unicode enabled sbcl ....
Don't know much about (portable) aserve. Anyway, i think UCW should try as
much as possible to stay server agnostic.

 Cheers Ralf Mattes

> - -- 
> Pupeno: pupeno at pupeno.com - http://pupeno.com
> Reading Science Fiction ? http://sfreaders.com.ar
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> 
> iD8DBQFCfoX0fW48a9PWGkURAhrsAJ9UKQADMzPmgNK5SzIXg+pDlZUaMwCcCdfp
> v8Noww36TseWE+8me61WNDY=
> =mUhs
> -----END PGP SIGNATURE-----
> _______________________________________________
> bese-devel mailing list
> bese-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/bese-devel


From mb at bese.it  Mon May  9 18:00:53 2005
From: mb at bese.it (Marco Baringer)
Date: Mon, 09 May 2005 20:00:53 +0200
Subject: [Bese-devel] UCW 0.3.9 - learning to spel
Message-ID: <m2vf5si8iy.fsf@soma.local>


-*- outline -*-

UnCommon Web version 0.3.9 - "learning to spel"
Released 2005-05-09

This release: improves the documentation; adds a completely new
back-end; adds multi-threading support to the mod_lisp back-end; provides
a large number of bug fixes and minor improvements.

* Home page

http://common-lisp.net/project/ucw/

* Download

ftp://ftp.common-lisp.net/pub/project/ucw/ucw_0.3.9.tar.gz
ftp://ftp.common-lisp.net/pub/project/ucw/ucw_0.3.9.tar.bz2

* Changes (since 0.3.7)

- rfc2388 and iterate are no longer included in distribution tarballs
  but must be downloaded separately. UCW, unless the araneida backend
  is used, now depends on PURI (puri.b9.com).

** System

- All the scripts and lisp files required for starting and stopping
  UCW are now in the bin directory. The unused file src/bin.lisp has
  been removed.

- The default log level has been turned down to avoid uninformative
  messages being constantly written to the console.

** RERL

- The Content-Type header is explicitly set in the standard-server's
  handle-request method.

- HTTP headers are now always passed as strings. Automatic
  keyword->string conversion has been eliminated.

- The DEFAPPLICATION macro has been removed. In its place we now must
  explicitly create the application object and register is with the
  server at the appropiate times.

** Components

- New REDIRECT component.

- New convenience macro initialize-container.

- *debug-on-error* and *inspect-components* are now exported from the
   UCW package.

** Back-ends

- All back-ends now use the ucw.backend logger, this is much simpler
  than having each backend have its own logger.

- The mod_lisp backend now supports parsing mime encoded POST
  data. The current API is not definitive and will change in the near
  future.

- mod_lisp backend now support multiple worker threads.

- Added httpd backend.

** YACLML/TAL

- <ucw:select :multiple t now works as expected.

- New convenience tags <ucw:text, <ucw:password and <ucw:submit.

- :action attribute now allowed on regular A and INPUT tags in TAL
  files.

- Fix spelling error in yaclml, enviroment is now consistently spelt
  correctly.

** Documentation

- Added the wiki example.

- Improved user's manual.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From djwatson at docwatson.org  Tue May 10 21:28:12 2005
From: djwatson at docwatson.org (Dave Watson)
Date: Tue, 10 May 2005 14:28:12 -0700
Subject: [Bese-devel] form backtracking
Message-ID: <20050510212812.GA27975@exife.cs.washington.edu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Is there an easy way to backtrack form elements?

For example, in form.lisp there are implementations of backtracked
text-fields, completing-text-fields, and a few others, but no
checkboxes.
- -- 
- -Dave Watson
djwatson at docwatson.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCgSds2CNsIQeZjsMRAvqXAJ45Lyc+QylrQkvedjs5q3MGBihMhgCfXQto
H0MhmH07XbWbukCQfQ/FMEU=
=jCot
-----END PGP SIGNATURE-----


From mb at bese.it  Wed May 11 06:03:43 2005
From: mb at bese.it (Marco Baringer)
Date: Wed, 11 May 2005 08:03:43 +0200
Subject: [Bese-devel] form backtracking
In-Reply-To: <20050510212812.GA27975@exife.cs.washington.edu> (Dave Watson's
	message of "Tue, 10 May 2005 14:28:12 -0700")
References: <20050510212812.GA27975@exife.cs.washington.edu>
Message-ID: <m2ekcel2o0.fsf@soma.local>

Dave Watson <djwatson at docwatson.org> writes:

> Is there an easy way to backtrack form elements?

if the form element is the slot of a component then just use the slot
option :backtrack t (or #'copy-seq or whatever). If the form element's
value is somewhere else you will need to call BACKTRACK yourself:

(ucw::backtrack (ucw::context.current-frame ucw:*context*)
                (ucw:make-place (ACCESSOR-FORM)))

You can do this at any point during the action.

> For example, in form.lisp there are implementations of backtracked
> text-fields, completing-text-fields, and a few others, but no
> checkboxes.

checkboxs have beena real pain in the ass for me, if you figure
something out i'd love to hear about it.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From a_bakic at yahoo.com  Fri May 13 00:38:58 2005
From: a_bakic at yahoo.com (Aleksandar Bakic)
Date: Thu, 12 May 2005 17:38:58 -0700 (PDT)
Subject: [Bese-devel] build problems
Message-ID: <20050513003858.35313.qmail@web40621.mail.yahoo.com>

Hi,

Even though I've been on this list for quite some time, I am only now getting
to try UCW seriously. Could someone please give me a hint on how to get around
errors of this form, when building using recent CMUCL (2005-03 and 2005-05)?

The slot PCL:CLASS-PRECEDENCE-LIST is unbound in the object
#<STANDARD-COMPONENT-CLASS ERROR-MESSAGE {5861C14D}>.
   [Condition of type UNBOUND-SLOT]

I tried patching ucw.asd, but that only delayed the errors a bit. I also tried
building with SBCL but got some other error... I checked out from the arch
repository using the slow-start procedure from the UCW web site (I had to add a
symlink to iterate.asd; I am new to arch).

Thanks,
Alex


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Find what you need with new enhanced search. 
http://info.mail.yahoo.com/mail_250


From mb at bese.it  Fri May 13 19:38:57 2005
From: mb at bese.it (Marco Baringer)
Date: Fri, 13 May 2005 21:38:57 +0200
Subject: [Bese-devel] build problems
In-Reply-To: <20050513003858.35313.qmail@web40621.mail.yahoo.com> (Aleksandar
	Bakic's message of "Thu, 12 May 2005 17:38:58 -0700 (PDT)")
References: <20050513003858.35313.qmail@web40621.mail.yahoo.com>
Message-ID: <m2hdh6c3vy.fsf@soma.local>

Aleksandar Bakic <a_bakic at yahoo.com> writes:

> Hi,
>
> Even though I've been on this list for quite some time, I am only now getting
> to try UCW seriously. Could someone please give me a hint on how to get around
> errors of this form, when building using recent CMUCL (2005-03 and 2005-05)?
>
> The slot PCL:CLASS-PRECEDENCE-LIST is unbound in the object
> #<STANDARD-COMPONENT-CLASS ERROR-MESSAGE {5861C14D}>.
>    [Condition of type UNBOUND-SLOT]
>
> I tried patching ucw.asd, but that only delayed the errors a bit. I also tried
> building with SBCL but got some other error... I checked out from the arch
> repository using the slow-start procedure from the UCW web site (I had to add a
> symlink to iterate.asd; I am new to arch).

error-message is a sub class of simple-window-component, which is
defined in src/component/window.lisp, try adding "window" to the
dependencies of error in the .asd file and see if the error persists:

--- orig/ucw.asd
+++ mod/ucw.asd
@@ -67,7 +67,7 @@
                   :depends-on (:backend "packages" "loggers" "helpers" "vars"))
                  (:module :components
                   :components ((:file "container")
-                               (:file "error" :depends-on ("ucw-inspector"))
+                               (:file "error" :depends-on ("ucw-inspector" "window"))
                                (:file "form" :depends-on ("widget"))
                                (:file "login")
                                (:file "message")

odd that nobody has been caught by this before...

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From a_bakic at yahoo.com  Fri May 13 22:03:30 2005
From: a_bakic at yahoo.com (Aleksandar Bakic)
Date: Fri, 13 May 2005 15:03:30 -0700 (PDT)
Subject: [Bese-devel] build problems
In-Reply-To: <m2hdh6c3vy.fsf@soma.local>
Message-ID: <20050513220330.95680.qmail@web40626.mail.yahoo.com>

> error-message is a sub class of simple-window-component, which is
> defined in src/component/window.lisp, try adding "window" to the
> dependencies of error in the .asd file and see if the error persists:

Thanks! In the meantime, I updated my asdf and added a dependency of
"ucw-inspector" on "window", and it worked. Actually, I also had to prepend
"common-lisp-user::" to "ensure-system-for-ucw :rfc2388" in bin/utils.lisp
(function use-httpd-backend).

Regards,
Alex


		
__________________________________ 
Do you Yahoo!? 
Make Yahoo! your home page 
http://www.yahoo.com/r/hs


From mb at bese.it  Sat May 14 12:31:10 2005
From: mb at bese.it (Marco Baringer)
Date: Sat, 14 May 2005 14:31:10 +0200
Subject: [Bese-devel] build problems
In-Reply-To: <20050513220330.95680.qmail@web40626.mail.yahoo.com> (Aleksandar
	Bakic's message of "Fri, 13 May 2005 15:03:30 -0700 (PDT)")
References: <20050513220330.95680.qmail@web40626.mail.yahoo.com>
Message-ID: <m2fywq9egh.fsf@soma.local>

Aleksandar Bakic <a_bakic at yahoo.com> writes:

>> error-message is a sub class of simple-window-component, which is
>> defined in src/component/window.lisp, try adding "window" to the
>> dependencies of error in the .asd file and see if the error persists:
>
> Thanks! In the meantime, I updated my asdf and added a dependency of
> "ucw-inspector" on "window", and it worked. Actually, I also had to prepend
> "common-lisp-user::" to "ensure-system-for-ucw :rfc2388" in bin/utils.lisp
> (function use-httpd-backend).

afaict window does not actually depend on ucw-inspector, i wonder why
this fixed your problem...

i commited ucw--dev--0.3--patch-417 which fixs the problem with
common-lisp-user:: and the calls to ensure-system-for-ucw (it was
missing in a couple of places). i also commited
ucw--dev--0.3--patch-418 which (hopefully) fixes ucw.asd.

(you will have some conflicts when you merge with the dev branch)

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From a_bakic at yahoo.com  Sat May 14 13:38:19 2005
From: a_bakic at yahoo.com (Aleksandar Bakic)
Date: Sat, 14 May 2005 06:38:19 -0700 (PDT)
Subject: [Bese-devel] build problems
In-Reply-To: <m2fywq9egh.fsf@soma.local>
Message-ID: <20050514133819.71631.qmail@web40603.mail.yahoo.com>

> > Thanks! In the meantime, I updated my asdf and added a dependency of
> > "ucw-inspector" on "window", and it worked. Actually, I also had to prepend
> > "common-lisp-user::" to "ensure-system-for-ucw :rfc2388" in bin/utils.lisp
> > (function use-httpd-backend).
> 
> afaict window does not actually depend on ucw-inspector, i wonder why
> this fixed your problem...

It was the other way around: ucw-inspector depends on window. At least, it
appeared so to me after I took a quick look at those files.

Alex


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail


From mb at bese.it  Sat May 14 13:53:16 2005
From: mb at bese.it (Marco Baringer)
Date: Sat, 14 May 2005 15:53:16 +0200
Subject: [Bese-devel] build problems
In-Reply-To: <20050514133819.71631.qmail@web40603.mail.yahoo.com> (Aleksandar
	Bakic's message of "Sat, 14 May 2005 06:38:19 -0700 (PDT)")
References: <20050514133819.71631.qmail@web40603.mail.yahoo.com>
Message-ID: <m2d5rt9ann.fsf@soma.local>

Aleksandar Bakic <a_bakic at yahoo.com> writes:

>> > Thanks! In the meantime, I updated my asdf and added a dependency of
>> > "ucw-inspector" on "window", and it worked. Actually, I also had to prepend
>> > "common-lisp-user::" to "ensure-system-for-ucw :rfc2388" in bin/utils.lisp
>> > (function use-httpd-backend).
>> 
>> afaict window does not actually depend on ucw-inspector, i wonder why
>> this fixed your problem...
>
> It was the other way around: ucw-inspector depends on window. At least, it
> appeared so to me after I took a quick look at those files.

ok, that explains why it would fix your problem (error depends on
ucw-inspector so by adding window as a dependency to ucw-inspector you
managed to give error the dependency on window). however i've take a
close look at window, ucw-inspector and error and i'm pretty sure the
current setup (window and ucw-inspector and independent, error depends
on both of them) is correct (yell at me if your problems presist).

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From randomtalk at gmail.com  Sat May 14 17:32:07 2005
From: randomtalk at gmail.com (Jason Wang)
Date: Sat, 14 May 2005 13:32:07 -0400
Subject: [Bese-devel] new start.lisp problems
In-Reply-To: <m2d5rt9ann.fsf@soma.local>
References: <20050514133819.71631.qmail@web40603.mail.yahoo.com>
	<m2d5rt9ann.fsf@soma.local>
Message-ID: <939cf2005051410325a6364a4@mail.gmail.com>

hi, i have tried to start up ucw yesterday evening, after two days of
pause.. However, it doesn't work anymore for some reason (i didn't
touch it since last time running).. today morning, i upgraded
everything to latest from tla.. and the problem persists.

When i run ./bin/ucwctl start && ./bin/ucwctl attach, it loads
start.lisp, and returns the following error:
debugger invoked on a SIMPLE-ERROR in thread 4493:
  Error during processing of --eval option "(|LOAD|
\"/var/www/ucw/bin/start.lisp\")":

  Argument X is not a REAL: NIL

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
  0: [RETRY   ] Retry performing #<ASDF:LOAD-OP NIL {95959B9}> on
                #<ASDF:CL-SOURCE-FILE "swank-loader" {95802B9}>.
  1: [ACCEPT  ] Continue, treating #<ASDF:LOAD-OP NIL {95959B9}> on
                #<ASDF:CL-SOURCE-FILE "swank-loader" {95802B9}> as having been
                successful.
  2: [CONTINUE] Ignore and continue with next --eval option.
  3: [ABORT   ] Skip rest of --eval options.
  4:            Skip to toplevel READ/EVAL/PRINT loop.
  5: [QUIT    ] Quit SBCL (calling #'QUIT, killing the process).

anyone know what's wrong?
-- 
www.programer.name - my own personal blog : )


From mb at bese.it  Sat May 14 18:22:58 2005
From: mb at bese.it (Marco Baringer)
Date: Sat, 14 May 2005 20:22:58 +0200
Subject: [Bese-devel] new start.lisp problems
In-Reply-To: <939cf2005051410325a6364a4@mail.gmail.com> (Jason Wang's message
	of "Sat, 14 May 2005 13:32:07 -0400")
References: <20050514133819.71631.qmail@web40603.mail.yahoo.com>
	<m2d5rt9ann.fsf@soma.local> <939cf2005051410325a6364a4@mail.gmail.com>
Message-ID: <m2hdh57jlp.fsf@soma.local>

Jason Wang <randomtalk at gmail.com> writes:

> hi, i have tried to start up ucw yesterday evening, after two days of
> pause.. However, it doesn't work anymore for some reason (i didn't
> touch it since last time running).. today morning, i upgraded
> everything to latest from tla.. and the problem persists.
>
> When i run ./bin/ucwctl start && ./bin/ucwctl attach, it loads
> start.lisp, and returns the following error:
> debugger invoked on a SIMPLE-ERROR in thread 4493:
>   Error during processing of --eval option "(|LOAD|
> \"/var/www/ucw/bin/start.lisp\")":
>
>   Argument X is not a REAL: NIL
>
> Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
>
> restarts (invokable by number or by possibly-abbreviated name):
>   0: [RETRY   ] Retry performing #<ASDF:LOAD-OP NIL {95959B9}> on
>                 #<ASDF:CL-SOURCE-FILE "swank-loader" {95802B9}>.
>   1: [ACCEPT  ] Continue, treating #<ASDF:LOAD-OP NIL {95959B9}> on
>                 #<ASDF:CL-SOURCE-FILE "swank-loader" {95802B9}> as having been
>                 successful.
>   2: [CONTINUE] Ignore and continue with next --eval option.
>   3: [ABORT   ] Skip rest of --eval options.
>   4:            Skip to toplevel READ/EVAL/PRINT loop.
>   5: [QUIT    ] Quit SBCL (calling #'QUIT, killing the process).
>
> anyone know what's wrong?

this has been happening to a LOT of people lately :(

this gist is that asdf is comparing the file-write-dates of two files,
one of which doesn't exist, and this is causing #'< (or maybe its
#'MAX) to return an error. since you get this error on swank-loader
i'd suggest killing your ~/.slime/fasl directory and seeing if the
problem pressits.

ucw is (afaik) the only external app which uses slime so maybe
something has changed in slime and i haven't upgraded ucw yet, if the
problme persists we'll look closer.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From matasar at gmail.com  Mon May 16 04:39:32 2005
From: matasar at gmail.com (Ben Matasar)
Date: Sun, 15 May 2005 21:39:32 -0700
Subject: [Bese-devel] Counter doesn't work in ucw 0.39: Can't find function
	"make-standard-environment"
Message-ID: <3347ff74050515213919b7d7b3@mail.gmail.com>

I've been playing a bit with UCW under OpenMCL 14.3 on a mac running
Tiger (aka 10.4), and all of the example applications run fine except
for the counter, which fails citing:

"Undefined function IT.BESE.UCW::MAKE-STANDARD-ENVIRONMENT called with
arguments (((IT.BESE.UCW:COMPONENT . #<IT.BESE.UCW-USER::COUNTER
#x687D34E>)) #<IT.BESE.UCW-USER::COUNTER #x687D34E>)"

In emacs I get the choice to do several things, including send a
backtrace page to the user (which is extremely cool, btw).

I also tried to build a simple hello component and got a similar
error.  I've tried both the araneida and httpd backends, and it
doesn't work with either one.  I can send the full backtrace to the
list if necessary.

My question is: Am I configuring things improperly? 

Thanks,
Ben


From mb at bese.it  Mon May 16 09:23:49 2005
From: mb at bese.it (Marco Baringer)
Date: Mon, 16 May 2005 11:23:49 +0200
Subject: [Bese-devel] Counter doesn't work in ucw 0.39: Can't find
	function "make-standard-environment"
In-Reply-To: <3347ff74050515213919b7d7b3@mail.gmail.com> (Ben Matasar's
	message of "Sun, 15 May 2005 21:39:32 -0700")
References: <3347ff74050515213919b7d7b3@mail.gmail.com>
Message-ID: <m2sm0nbk2i.fsf@soma.local>

Ben Matasar <matasar at gmail.com> writes:

> I've been playing a bit with UCW under OpenMCL 14.3 on a mac running
> Tiger (aka 10.4), and all of the example applications run fine except
> for the counter, which fails citing:

(ot: you suggest buying 10.4.0 or waiting for 10.4.1?)

> "Undefined function IT.BESE.UCW::MAKE-STANDARD-ENVIRONMENT called with
> arguments (((IT.BESE.UCW:COMPONENT . #<IT.BESE.UCW-USER::COUNTER
> #x687D34E>)) #<IT.BESE.UCW-USER::COUNTER #x687D34E>)"
>
> In emacs I get the choice to do several things, including send a
> backtrace page to the user (which is extremely cool, btw).

it'll be even cooler when (if) that backtrace page gives you a list of
restarts...

> I also tried to build a simple hello component and got a similar
> error.  I've tried both the araneida and httpd backends, and it
> doesn't work with either one.  I can send the full backtrace to the
> list if necessary.
>
> My question is: Am I configuring things improperly? 

Just before releasing 0.3.9 i renamed enviroment to enviroNment in the
ucw and yaclml source code, since you get an error about
make-standard-environment (notice the correct spelling of environment)
my guess is that you have an up-to-date ucw but an out-of-date yaclml.

1) make sure you have exactly one copy of yaclml installed 

2) make sure the copy of yaclml asdf is using is the one shipped with
   ucw. you can check this by looking at the path returned by:

   (asdf:component-pathname (asdf:find-system :yaclml))

   and making user that it's under the ucw 0.3.9 tree.

3) open up ucw_0.3.9/libs/yaclml/src/tal/tal-environment.lisp and make
   sure the environment is correctly spelled.

4) if you successfully get here then i f__ked up something along tha
   way and you're entitled to: 1) mail a complete backtrace (show the
   local variables) 2) drink to forget :)

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From mb at bese.it  Mon May 16 14:21:58 2005
From: mb at bese.it (Marco Baringer)
Date: Mon, 16 May 2005 16:21:58 +0200
Subject: [Bese-devel] Counter doesn't work in ucw 0.39: Can't find
	function "make-standard-environment"
In-Reply-To: <3347ff7405051607155c30fb07@mail.gmail.com> (Ben Matasar's
	message of "Mon, 16 May 2005 07:15:58 -0700")
References: <3347ff74050515213919b7d7b3@mail.gmail.com>
	<m2sm0nbk2i.fsf@soma.local>
	<3347ff7405051607155c30fb07@mail.gmail.com>
Message-ID: <m2wtpz8d4p.fsf@soma.local>

Ben Matasar <matasar at gmail.com> writes:

> Marco, 
>
> Yeah, the problem was that I installed yaclml from asdf-install rather
> than using the one that came packaged with ucw.  I am now using the
> arnesi and yaclml from the ucw tarball, and most other packages from
> Cliki via asdf-install (including rfc2388, iterate, and others).
> Thanks for your help.
>
> Next question: the httpd backend doesn't appear to load the (whole?)
> wwwroot but does load the examples.  This manifests itself by giving
> me working examples with no stylesheet (aka plain old page).  The
> araneida backend (which I would prefer to use) doesn't give me
> examples or the stylesheet, but does start a webserver.

the httpd backend doesn't currently know how to server static pages,
it sends entry-ponit requests to ucw and returns a 404 for everything
else :(

the araneida backend _should_ work (the only thing you should see are
the 404s related to favico.icn). the first thing that comes to my mind
is: are you using the same host ("127.0.0.1") in both the cuw setup
and the browser? [there should be a warning in ucw's startup messages
to this effect].

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From matasar at gmail.com  Mon May 16 14:26:59 2005
From: matasar at gmail.com (Ben Matasar)
Date: Mon, 16 May 2005 07:26:59 -0700
Subject: [Bese-devel] Counter doesn't work in ucw 0.39: Can't find
	function "make-standard-environment"
In-Reply-To: <m2wtpz8d4p.fsf@soma.local>
References: <3347ff74050515213919b7d7b3@mail.gmail.com>
	<m2sm0nbk2i.fsf@soma.local>
	<3347ff7405051607155c30fb07@mail.gmail.com>
	<m2wtpz8d4p.fsf@soma.local>
Message-ID: <3347ff7405051607267a877bc3@mail.gmail.com>

Yeah, apparently "localhost" is no good but "127.0.0.1" does work.  Fascinating.

Thanks, I look forward to continuing to play with UCW. 

Ben

On 5/16/05, Marco Baringer <mb at bese.it> wrote:
> Ben Matasar <matasar at gmail.com> writes:
> 
> > Marco,
> >
> > Yeah, the problem was that I installed yaclml from asdf-install rather
> > than using the one that came packaged with ucw.  I am now using the
> > arnesi and yaclml from the ucw tarball, and most other packages from
> > Cliki via asdf-install (including rfc2388, iterate, and others).
> > Thanks for your help.
> >
> > Next question: the httpd backend doesn't appear to load the (whole?)
> > wwwroot but does load the examples.  This manifests itself by giving
> > me working examples with no stylesheet (aka plain old page).  The
> > araneida backend (which I would prefer to use) doesn't give me
> > examples or the stylesheet, but does start a webserver.
> 
> the httpd backend doesn't currently know how to server static pages,
> it sends entry-ponit requests to ucw and returns a 404 for everything
> else :(
> 
> the araneida backend _should_ work (the only thing you should see are
> the 404s related to favico.icn). the first thing that comes to my mind
> is: are you using the same host ("127.0.0.1") in both the cuw setup
> and the browser? [there should be a warning in ucw's startup messages
> to this effect].
> 
> --
> -Marco
> Ring the bells that still can ring.
> Forget the perfect offering.
> There is a crack in everything.
> That's how the light gets in.
>         -Leonard Cohen
>


From matasar at gmail.com  Mon May 16 14:15:58 2005
From: matasar at gmail.com (Ben Matasar)
Date: Mon, 16 May 2005 07:15:58 -0700
Subject: [Bese-devel] Counter doesn't work in ucw 0.39: Can't find
	function "make-standard-environment"
In-Reply-To: <m2sm0nbk2i.fsf@soma.local>
References: <3347ff74050515213919b7d7b3@mail.gmail.com>
	<m2sm0nbk2i.fsf@soma.local>
Message-ID: <3347ff7405051607155c30fb07@mail.gmail.com>

Marco, 

Yeah, the problem was that I installed yaclml from asdf-install rather
than using the one that came packaged with ucw.  I am now using the
arnesi and yaclml from the ucw tarball, and most other packages from
Cliki via asdf-install (including rfc2388, iterate, and others).
Thanks for your help.

Next question: the httpd backend doesn't appear to load the (whole?)
wwwroot but does load the examples.  This manifests itself by giving
me working examples with no stylesheet (aka plain old page).  The
araneida backend (which I would prefer to use) doesn't give me
examples or the stylesheet, but does start a webserver.

I also got my hello world template-component to work, so that's progress.

> (ot: you suggest buying 10.4.0 or waiting for 10.4.1?)

10.4.1 is supposedly due any day now.  10.4.0 is a bit buggy but no
dangerous bugs so far.  I think you're safe with 10.4.0, now that the
aqua emacs builds :).

Thanks,
Ben


From pjb at informatimago.com  Tue May 17 03:42:16 2005
From: pjb at informatimago.com (Pascal J.Bourguignon)
Date: Tue, 17 May 2005 05:42:16 +0200 (CEST)
Subject: [Bese-devel] EVAL: variable SELF has no value
Message-ID: <20050517034216.0193B10FBF3@thalassa.informatimago.com>


I've got a simple render-on method that just calls another component:

(defmethod render-on ((res response) (compo user-admin))
  (call 'not-implemented-yet
        :message (_ "Administration des utilisateurs")))


(defcomponent not-implemented-yet (widget-component)
  ((message  :accessor not-implemented-yet.message
             :initform nil
             :initarg :message
             :documentation "A message which will be presented to the user"))
  (:default-initargs
   :title (_ "Pas encore impl?ment?" "Window Title")
   :stylesheet "stylesheet.css")
  (:metaclass standard-component-class)
  (:documentation "Not implemented yet."))


(defmethod render-on ((res response) (compo not-implemented-yet))
  (<:div
    :id "not-implemented-yet"
    (when (not-implemented-yet.message compo)
      (<:h2 (<:as-html (not-implemented-yet.message compo))))
    (<:p (<:as-html
          (_ "D?sol?, cette fonction n'est pas encore impl?ment?e.")))
    (<ucw:form
     (button (_ "Retour" "Button") (answer-component compo nil)))))


Then, when the first component is to be rendered, I obtain instead a
backtrace with the top of stack being:

EVAL frame for form ((LAMBDA (RES COMPO) 
                     (DECLARE (SYSTEM::SOURCE
                               ((RES COMPO)
                                 (DECLARE (IGNORABLE RES COMPO)) 
                                 (BLOCK RENDER-ON
                                   (CALL 'NOT-IMPLEMENTED-YET
                                      :MESSAGE
                                      (_ "Administration des utilisateurs"))))))
                     (DECLARE (IGNORABLE RES COMPO))
                     (CALL-COMPONENT SELF (MAKE-INSTANCE 'NOT-IMPLEMENTED-YET
                         :MESSAGE "Administration des utilisateurs")))
                     #:G13176 #:G13177)


By the same token, I cannot write (ANSWER result) because this macro
expands to an expression refering SELF, so I have to write:

  (ANSWER-COMPONENT compo result)


Do I do something wrong or should I just avoid these macros?

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
Until real software engineering is developed, the next best practice
is to develop with a dynamic system that has extreme late binding in
all aspects. The first system to really do this in an important way
is Lisp. -- Alan Kay


From mb at bese.it  Tue May 17 08:44:52 2005
From: mb at bese.it (Marco Baringer)
Date: Tue, 17 May 2005 10:44:52 +0200
Subject: [Bese-devel] EVAL: variable SELF has no value
In-Reply-To: <20050517034216.0193B10FBF3@thalassa.informatimago.com> (Pascal
	J. Bourguignon's message of "Tue,
	17 May 2005 05:42:16 +0200 (CEST)")
References: <20050517034216.0193B10FBF3@thalassa.informatimago.com>
Message-ID: <m2oebaqm0r.fsf@soma.local>

Pascal J.Bourguignon <pjb at informatimago.com> writes:

> Do I do something wrong or should I just avoid these macros?

i think you're misunderstanding the purpose of CALL and ANSWER.

ANSWER and CALL are component "control flow" operators (if that
terminologoy makes any sense), they allow you to control how we get
from one component to the next. as such they only make sense in the
context of code which controls the passage between components, aka
actions and entry-points.

> (defmethod render-on ((res response) (compo user-admin))
>   (call 'not-implemented-yet
>         :message (_ "Administration des utilisateurs")))

what this is saying is: when _rendering_ the user-admin object compo
you should first pass control to a not-implemented-yet, when that
_answers_ then the render-on call should return.

This doesn't make any sense (not to me atleast). maybe what you want
to say is: "use not-implemented-yet's render-on method when attempting
to render a user-admin component." this isn't hard to do, but it's
written differently:

(defmethod render-on ((res response) (compo user-admin))
  (render-on res (make-instance 'not-implemented-yet ...)))

The other option is to add a rule which says "everytime someone tries
to call a user-admin component we sholud actually jump to a
not-implemented-yet component":

(defmethod/cc call-component ((from standard-component)
                              (to user-admin))
  (let/cc k
    (setf (place (component.place from))
          (make-instance 'not-implemented-yet
                         :continuation k
                         :place (component.place from)
                         :parent (component.parent from)))))

of course, this doesn't stop anyone from doing (make-instance
'user-admin).

hope this helps.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From pupeno at pupeno.com  Wed May 18 03:56:13 2005
From: pupeno at pupeno.com (Pupeno)
Date: Wed, 18 May 2005 00:56:13 -0300
Subject: [Bese-devel] Why (let ((part part)) ...) on wiki.lisp ?
Message-ID: <200505180056.16404.pupeno@pupeno.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The section where each wiki-word is turned into a link (an action-link) on the 
wiki example, it says:
(dolist (part (cl-ppcre:split scanner
                                  (contents (find-wiki-page (page-name page)))
                                  :with-registers-p t))
      (if (cl-ppcre:scan scanner part)
          (let ((part part)) ; At this point, part contains the page linking 
to.
            (<ucw:a :action (view-page page part)
              (<:as-html part)))
          (<:as-is part))))

Why is the (let ((part part))...) there ? What is the effect of asigning part 
to part ? Why is it needed (if returned, when the action view-page is run, 
part contains NIL). It seems something like a scope problem, but if someone 
can enlighten me about it, I'd be thankful.
Thank you.
- -- 
Pupeno: pupeno at pupeno.com - http://pupeno.com
Reading Science Fiction ? http://sfreaders.com.ar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCirzgfW48a9PWGkURApuIAJ9OsaKG05iCMchzCsdwJ5mBeu4U5wCfZHQ2
rX+Y07esyni+KLIVjoC1zBE=
=Nsdd
-----END PGP SIGNATURE-----


From bdowning at lavos.net  Wed May 18 05:09:26 2005
From: bdowning at lavos.net (Brian Downing)
Date: Wed, 18 May 2005 00:09:26 -0500
Subject: [Bese-devel] Why (let ((part part)) ...) on wiki.lisp ?
In-Reply-To: <200505180056.16404.pupeno@pupeno.com>;
	from pupeno@pupeno.com on Wed, May 18, 2005 at 12:56:13AM -0300
References: <200505180056.16404.pupeno@pupeno.com>
Message-ID: <20050518000925.B25486@lavos.net>

On Wed, May 18, 2005 at 12:56:13AM -0300, Pupeno wrote:
> Why is the (let ((part part))...) there ? What is the effect of asigning part 
> to part ? Why is it needed (if returned, when the action view-page is run, 
> part contains NIL). It seems something like a scope problem, but if someone 
> can enlighten me about it, I'd be thankful.

It's so that you have a fresh lexical binding to wrap up in the :action.
Otherwise DOLIST can choose to SETF part instead of rebinding it, so all
the links could wind up pointing to the same place (as they would all be
closed over the same binding)!

-bcd


From mb at bese.it  Wed May 18 10:27:48 2005
From: mb at bese.it (Marco Baringer)
Date: Wed, 18 May 2005 12:27:48 +0200
Subject: [Bese-devel] version dependencies
Message-ID: <m2hdh0de1n.fsf@soma.local>


http://common-lisp.net/cgi-bin/archzoom.cgi/ucw-2004 at common-lisp.net/ucw--dev--0.3--patch-420?log

ucw will now refuse to load unless you have the proper (aka very very
recent) versions of arnesi and yaclml.

------------------------------

i'd like to go off on a slight tangent:

instead of assigning a single version number to each version it
appears (at first sight) to be a great idea to give each version a
list of version tags (which are just free form strings).

compared to the 'single-version-number' this scheme has the advantage
that:

1) you no longer need to give version numbers structures. if you want
   at least 0.5.2 then just check thaht the 0.5.2 string is in there
   someplace. this will hald true for 0.5.2 and all successive
   versions.

2) if you want to break backwards compatability then remove the
   version number. example, let's say release 0.6.0 breaks
   compatablitiy with 0.5.2 then we just drop the 0.5.2 tag string
   from the 0.6.0 release and now any code which requires at least
   0.5.2 will stop working. (abviously if we've broken compatability
   with all previous versions then we drop all version tags).

3) you can stop using version number and give each release a set of
   features it implements, instead of asking for version 0.5.2 we ask
   for the version which supports the feature "mega-man-7"

4) you are no longer shoe horned into someone else's idea of what a
   version spec is and what it looks like. versions are just strings
   and they're either there or they aren't.

5) maintainers can be as specific or as generic as they want without
   breaking the system.

6) users can decide whether or not they trust the maintainers.

the only disadvantages i can see at the moment:

1) after a while (fsvo 'a while') you'll have many tags, this many
   become unmanageable (we'll see).

2) it looks really strange to see version 0.6 which includes tags for
   versions 0.2.37 and 0.4.1.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From smoof-ra at elder-gods.org  Thu May 19 09:18:22 2005
From: smoof-ra at elder-gods.org (Larry D'Anna)
Date: Thu, 19 May 2005 05:18:22 -0400
Subject: [Bese-devel] ucw on cmucl/linux
Message-ID: <ef9825d6d128c3778e64e0269445a53d@elder-gods.org>

I'm trying to get ucw working on cmucl and i'm encountering the  
following error.
What's really strange is that the defmethod that it's complaining about  
has the same
argument list as is specified in AMOP.  Has anyone else run into this,  
or know how to fix it?


;;; Loading  
#p"/home/larry/lisp/ucw/src/rerl/standard-component/standard-component- 
class.x86f".

Attempt to add the method #<Standard-Method  
PCL:DIRECT-SLOT-DEFINITION-CLASS (STANDARD-COMPONENT-CLASS)
                             {48792DD5}> to the generic function  
#<Standard-Generic-Function PCL:DIRECT-SLOT-DEFINITION-CLASS (3)
                                                                    
{281A40F9}>.
But the method has fewer required arguments than the generic function.

Restarts:
   0: [CONTINUE] Return NIL from load of  
#p"/home/larry/lisp/ucw/src/rerl/standard-component/standard-component- 
class.x86f".
   1: [RETRY   ] Retry performing #<ASDF:LOAD-OP NIL {48E809ED}> on
                 #<ASDF:CL-SOURCE-FILE "standard-component-class"  
{48E809FD}>.
   2: [ACCEPT  ] Continue, treating #<ASDF:LOAD-OP NIL {48E809ED}> on
                 #<ASDF:CL-SOURCE-FILE "standard-component-class"  
{48E809FD}> as
                 having been successful.
   3:            Return NIL from load of  
#p"/home/larry/lisp/ucw/bin/utils.lisp".
   4:            Return NIL from load of "start.lisp".
   5: [ABORT   ] Skip remaining initializations.

Debug  (type H for help)

(PCL::CHECK-METHOD-ARG-INFO
  #<Standard-Generic-Function PCL:DIRECT-SLOT-DEFINITION-CLASS (3)  
{281A40F9}>
  #S(PCL::ARG-INFO
       :ARG-INFO-LAMBDA-LIST (PCL::CLASS PCL::INITARGS)
       :ARG-INFO-PRECEDENCE (0 1)
       :ARG-INFO-METATYPES (PCL:STANDARD-INSTANCE T)
       :ARG-INFO-NUMBER-OPTIONAL 0
       :ARG-INFO-KEY/REST-P NIL
       ...)
  #<Standard-Method PCL:DIRECT-SLOT-DEFINITION-CLASS  
(STANDARD-COMPONENT-CLASS)
    {48792DD5}>)



From mb at bese.it  Thu May 19 10:26:22 2005
From: mb at bese.it (Marco Baringer)
Date: Thu, 19 May 2005 12:26:22 +0200
Subject: [Bese-devel] ucw on cmucl/linux
In-Reply-To: <ef9825d6d128c3778e64e0269445a53d@elder-gods.org> (Larry D'Anna's
	message of "Thu, 19 May 2005 05:18:22 -0400")
References: <ef9825d6d128c3778e64e0269445a53d@elder-gods.org>
Message-ID: <m2y8abldf5.fsf@soma.local>

Larry D'Anna <smoof-ra at elder-gods.org> writes:

> I'm trying to get ucw working on cmucl and i'm encountering the
> following error.
> What's really strange is that the defmethod that it's complaining
> about  has the same
> argument list as is specified in AMOP.  Has anyone else run into this,
> or know how to fix it?

odd.

> (PCL::CHECK-METHOD-ARG-INFO
>   #<Standard-Generic-Function PCL:DIRECT-SLOT-DEFINITION-CLASS (3)
>    {281A40F9}>
>   #S(PCL::ARG-INFO
>        :ARG-INFO-LAMBDA-LIST (PCL::CLASS PCL::INITARGS)
>        :ARG-INFO-PRECEDENCE (0 1)
>        :ARG-INFO-METATYPES (PCL:STANDARD-INSTANCE T)
>        :ARG-INFO-NUMBER-OPTIONAL 0
>        :ARG-INFO-KEY/REST-P NIL

this looks odd, i _should_ be:

:ARG-INFO-LAMBDA-LIST (PCL::CLASS &REST PCL::INITARGS)
:ARG-INFO-PRECEDENCE (0)
:ARG-INFO-METATYPES (PCL:STANDARD-INSTANCE)
:ARG-INFO-NUMBER-OPTIONAL 1
:ARG-INFO-KEY/REST-P T

(or something like that)

what version of cmucl are you running on?

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From smoof-ra at elder-gods.org  Thu May 19 21:18:50 2005
From: smoof-ra at elder-gods.org (Larry D'Anna)
Date: Thu, 19 May 2005 17:18:50 -0400
Subject: [Bese-devel] ucw on cmucl/linux
In-Reply-To: <m2y8abldf5.fsf@soma.local>
References: <ef9825d6d128c3778e64e0269445a53d@elder-gods.org>
	<m2y8abldf5.fsf@soma.local>
Message-ID: <f9542ff610654e19a8b71bd5fd21f388@elder-gods.org>


On May 19, 2005, at 6:26 AM, Marco Baringer wrote:
> what version of cmucl are you running on?

18e

	--larry



From smoof-ra at elder-gods.org  Fri May 20 03:39:38 2005
From: smoof-ra at elder-gods.org (Larry D'Anna)
Date: Thu, 19 May 2005 23:39:38 -0400
Subject: [Bese-devel] ucw on cmucl/linux
In-Reply-To: <f9542ff610654e19a8b71bd5fd21f388@elder-gods.org>
References: <ef9825d6d128c3778e64e0269445a53d@elder-gods.org>
	<m2y8abldf5.fsf@soma.local>
	<f9542ff610654e19a8b71bd5fd21f388@elder-gods.org>
Message-ID: <bd695160307fb4e33fb4f6a1a2a53989@elder-gods.org>


On May 19, 2005, at 5:18 PM, Larry D'Anna wrote:

>
> On May 19, 2005, at 6:26 AM, Marco Baringer wrote:
>> what version of cmucl are you running on?
>
> 18e

upgrading to 19a fixes it :-)  Sorry for all the emails.

	--larry





From mb at bese.it  Mon May 23 04:32:33 2005
From: mb at bese.it (Marco Baringer)
Date: Mon, 23 May 2005 06:32:33 +0200
Subject: [Bese-devel] darcs archive
Message-ID: <m2psviblzy.fsf@soma.local>


the darcs archive is currently busted. i'm looking into the issue but
i haven't had much free time lately. does this mean anything to anyone:

Pushing to mbaringer at common-lisp.net:/project/ucw/public_html/_darcs/ucw/...

Fail: failed to read patch in get_extra:
Fri Apr 29 13:23:20 CEST 2005  Marco Baringer <mb at bese.it>
  * back out the recent byte vs character changes to the httpd backend
Perhaps this is a 'partial' repository?


-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From pupeno at pupeno.com  Wed May 25 04:17:20 2005
From: pupeno at pupeno.com (Pupeno)
Date: Wed, 25 May 2005 01:17:20 -0300
Subject: [Bese-devel] Error compiling
Message-ID: <200505250117.25064.pupeno@pupeno.com>

When loading start.lisp I get the following error, might it be because I'm not 
running an enough recent version of slime ?

erred while invoking #<COMPILE-OP NIL {A67FBE9}> on
#<CL-SOURCE-FILE "swank-loader" {A67FBF9}>
   [Condition of type ASDF:COMPILE-FAILED]

Restarts:
  0: [RETRY] Retry performing #<ASDF:COMPILE-OP NIL {A67FBE9}> on 
#<ASDF:CL-SOURCE-FILE "swank-loader" {A67FBF9}>.
  1: [ACCEPT] Continue, treating #<ASDF:COMPILE-OP NIL {A67FBE9}> on 
#<ASDF:CL-SOURCE-FILE "swank-loader" {A67FBF9}> as having been successful.
  2: [ABORT] Abort handling SLIME request.
  3: [DESTROY-THREAD] Destroy this thread (23228)

Backtrace:
  0: ((SB-PCL::FAST-METHOD ASDF:PERFORM (ASDF:COMPILE-OP ASDF:CL-SOURCE-FILE)) 
#<unavailable argument> #<unavailable argument> #<ASDF:COMPILE-OP NIL 
{A67FBE9}> #<ASDF:CL-SOURCE-FILE "swank-loader" {A67FBF9}>)
  1: ((LAMBDA (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0. 
SB-PCL::.ARG1.)) #<unavailable argument> #<unavailable argument> 
#<ASDF:COMPILE-OP NIL {A67FBE9}> #<ASDF:CL-SOURCE-FILE 
"swank-loader" {A67FBF9}>)
  2: ((LAMBDA NIL))
  3: (SB-C::%WITH-COMPILATION-UNIT #<CLOSURE (LAMBDA NIL) {A518225}>)
  4: (ASDF:OPERATE ASDF:LOAD-OP :UCW)
  5: (SB-INT:EVAL-IN-LEXENV (ASDF:OOS (QUOTE ASDF:LOAD-OP) :UCW) 
#<NULL-LEXENV>)
  6: (SB-FASL::LOAD-AS-SOURCE #<SB-SYS:FD-STREAM for "file 
\"/home/pupeno/src/ucw/bin/utils.lisp\"" {9A410A1}> NIL NIL)
  7: (SB-FASL::INTERNAL-LOAD #P"/home/pupeno/src/ucw/bin/utils.lisp" 
#P"/home/pupeno/src/ucw/bin/utils.lisp" :ERROR NIL NIL :SOURCE :DEFAULT)
  8: (SB-FASL::INTERNAL-LOAD #P"/home/pupeno/src/ucw/bin/utils.lisp" 
#P"/home/pupeno/src/ucw/bin/utils.lisp" :ERROR NIL NIL NIL :DEFAULT)
  9: (LOAD #P"/home/pupeno/src/ucw/bin/utils.lisp")
 10: (SB-INT:EVAL-IN-LEXENV (LOAD (MERGE-PATHNAMES "utils.lisp" 
*LOAD-TRUENAME*)) #<NULL-LEXENV>)
 11: (SB-FASL::LOAD-AS-SOURCE #<SB-SYS:FD-STREAM for "file 
\"/home/pupeno/src/ucw/bin/start.lisp\"" {9A1B501}> NIL NIL)
 12: (SB-FASL::INTERNAL-LOAD #P"/home/pupeno/src/ucw/bin/start.lisp" 
#P"/home/pupeno/src/ucw/bin/start.lisp" :ERROR NIL NIL :SOURCE :DEFAULT)
 13: (SB-FASL::INTERNAL-LOAD #P"/home/pupeno/src/ucw/bin/start.lisp" 
#P"/home/pupeno/src/ucw/bin/start.lisp" :ERROR NIL NIL NIL :DEFAULT)
 14: (LOAD "/home/pupeno/src/ucw/bin/start.lisp")
 15: (SWANK:LOAD-FILE "/home/pupeno/src/ucw/bin/start.lisp")
 16: (SB-INT:EVAL-IN-LEXENV (SWANK:LOAD-FILE 
"/home/pupeno/src/ucw/bin/start.lisp") #<NULL-LEXENV>)
 17: ((LAMBDA NIL))
 18: ((SB-PCL::FAST-METHOD SWANK-BACKEND:CALL-WITH-DEBUGGER-HOOK (T T)) 
#<unused argument> #<unused argument> #<FUNCTION SWANK:SWANK-DEBUGGER-HOOK> 
#<CLOSURE (LAMBDA NIL) {9A180ED}>)
 19: ((LAMBDA NIL))
 20: ((LAMBDA NIL))
 21: (SWANK::CALL-WITH-REDIRECTED-IO #<SWANK::CONNECTION {98D5251}> #<CLOSURE 
(LAMBDA NIL) {9A13FC5}>)
 22: (SWANK::CALL-WITH-CONNECTION #<SWANK::CONNECTION {98D5251}> #<FUNCTION 
(LAMBDA NIL) {94EDADD}>)
 23: (SWANK::HANDLE-REQUEST #<SWANK::CONNECTION {98D5251}>)
 24: (SWANK::CALL-WITH-BINDINGS NIL #<CLOSURE (LAMBDA NIL) {9A13FA5}>)
 25: ((LAMBDA NIL))
 26: ("foreign function: call_into_lisp")
 27: ("foreign function: funcall0")

Thanks
-- 
Pupeno <pupeno at pupeno.com> (http://pupeno.com)
Reading ? Science Fiction ? http://sfreaders.com.ar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/bese-devel/attachments/20050525/61c6bea3/attachment.sig>

From mb at bese.it  Thu May 26 10:27:11 2005
From: mb at bese.it (Marco Baringer)
Date: Thu, 26 May 2005 12:27:11 +0200
Subject: [Bese-devel] Error compiling
In-Reply-To: <200505250117.25064.pupeno@pupeno.com> (pupeno@pupeno.com's
	message of "Wed, 25 May 2005 01:17:20 -0300")
References: <200505250117.25064.pupeno@pupeno.com>
Message-ID: <m2fywa2sg0.fsf@soma.local>

Pupeno <pupeno at pupeno.com> writes:

> When loading start.lisp I get the following error, might it be because I'm not 
> running an enough recent version of slime ?
>
> erred while invoking #<COMPILE-OP NIL {A67FBE9}> on
> #<CL-SOURCE-FILE "swank-loader" {A67FBF9}>
>    [Condition of type ASDF:COMPILE-FAILED]

all this says is that there was an erro while compiling swank-loader,
but it doesn't way what. try running (compile-file
"/path/to/slime/swank-loader.lisp") for more details.

-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen


From pupeno at pupeno.com  Sat May 28 01:13:06 2005
From: pupeno at pupeno.com (Pupeno)
Date: Fri, 27 May 2005 22:13:06 -0300
Subject: [Bese-devel] Strange method combination
Message-ID: <200505272213.08780.pupeno@pupeno.com>

Hello,
I was working on a web site refactoring the presentations example when I 
noticed a very weird behaviour. When edit-from-listing was called, the 
database (using cl-sql) got updated but the listing showed the old record, so 
I started researching and I've found a very strange problem: 
edit-from-listing :after gets called before edit-from-listing finishes. I've 
added some very verbose debuging output and this is what I get:

@@@ Starting: edit-from-listing ((person-listing person-listing) (person 
person) index.
@@@@ Running: (present-object person :using person-editor).
@@@ Starting: edit-from-listing :after ((l list-presentation) item index.
@@@@ Running: (setf (instances l) (get-all-instances l).
@@@ Ending: edit-from-listing :after (...).
@@@ Ending: edit-from-listing (...).

instead of what I should really get:

@@@ Starting: edit-from-listing ((person-listing person-listing) (person 
person) index.
@@@@ Running: (present-object person :using person-editor).
@@@ Ending: edit-from-listing (...).
@@@ Starting: edit-from-listing :after ((l list-presentation) item index.
@@@@ Running: (setf (instances l) (get-all-instances l).
@@@ Ending: edit-from-listing :after (...).

Isn't this strange ? I thought that maybe it had something to do with the way 
UCW manages continuations (if not, I would be doing tests to see if it's a 
sbcl bug, because that is not what's on the common lisp specification[1]). 
Attached is a compressed tar with src/components/presentation.lisp and 
examples/presentation.lisp to show the error (it makes the debuging output 
previusly shown).
Any help is appretiated.
-- 
Pupeno <pupeno at pupeno.com> (http://pupeno.com)
Reading ? Science Fiction ? http://sfreaders.com.ar

[1] http://www.lispworks.com/documentation/HyperSpec/Body/07_ffb.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: presents.tar.bz2
Type: application/x-tbz
Size: 8578 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/bese-devel/attachments/20050527/b529c799/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/bese-devel/attachments/20050527/b529c799/attachment.sig>

From mb at bese.it  Mon May 30 15:55:00 2005
From: mb at bese.it (Marco Baringer)
Date: Mon, 30 May 2005 17:55:00 +0200
Subject: [Bese-devel] Strange method combination
In-Reply-To: <200505272213.08780.pupeno@pupeno.com> (pupeno@pupeno.com's
	message of "Fri, 27 May 2005 22:13:06 -0300")
References: <200505272213.08780.pupeno@pupeno.com>
Message-ID: <m2k6lgbtez.fsf@soma.local>

Pupeno <pupeno at pupeno.com> writes:

> Hello,
> I was working on a web site refactoring the presentations example when I 
> noticed a very weird behaviour. When edit-from-listing was called, the 
> database (using cl-sql) got updated but the listing showed the old record, so 
> I started researching and I've found a very strange problem: 
> edit-from-listing :after gets called before edit-from-listing finishes. I've 
> added some very verbose debuging output and this is what I get:

the problem si that edit-from-listing isn't a regular method but an
"action." here's the gory details:

(defaction foo ((c component))
  (pre-call)
  (call 'some-component)
  (post-call))

(defmethod foo :after ((c component))
  (do-stuff))

now if we call (foo c) the first thing that happens is the PRE-CALL is
called and this makes sense. then however we have (call
'some-component), at this point the execution of foo stops, the
contiuation (which amounts to just a call to POST-CALL) is stored in
the new some-component object and the method foo _returns_. Method
combination being what it is this causes foo :after to run and
do-stuff to get called. sholud the SOME-COMPONENT return at a later
date the form (post-call) will get executed but, since foo isn't being
called directly, do-stuff will not.

this behaviour can be fixed with a custom method-combination, until
then you're screwed.

hth.
-- 
-Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen