Hi, I am not 100% sure that it is a bug in tbnl not in my setup though when using SBCL (cvs version 2005-10-07) it seems that tbnl refuses to serve jpg/png files ... I have tried launching the test application and it works fine except for the
"Binary data, delivered from file (a picture)" "Binary data, delivered from RAM (same picture)"
sections :/ I thought that the problem might be in the dispatcher, but i could not upload jpg/png files through "File Uploads" too (post script files uploaded/downloaded fine) i was just geting back to the upload page after clicking on the submit button.
At the same time - the same set up worked fine on CMUCL, i mean i could see example image and could download/upload any files i want.
I got no errors on the lisp side, so i can't send you any tracebacks.
Ignas Mikalajūnas
On Fri, 7 Oct 2005 03:21:44 +0300, Ignas Mikalajunas ignas.mikalajunas@gmail.com wrote:
Hi, I am not 100% sure that it is a bug in tbnl not in my setup though when using SBCL (cvs version 2005-10-07) it seems that tbnl refuses to serve jpg/png files ...
This might be a problem with SBCL's Unicode implementation.[*] We had similar issues already:
http://common-lisp.net/pipermail/tbnl-devel/2005-June/000341.html
I'm sorry but TBNL is kind of unsupported for SBCL. I don't use it and nobody else has sent patches yet to fix the known problems.
Cheers, Edi.
[*] To make this clear: The problem is TBNL, not SBCL.
I'm sorry but TBNL is kind of unsupported for SBCL. I don't use it and nobody else has sent patches yet to fix the known problems.
Cheers, Edi.
[*] To make this clear: The problem is TBNL, not SBCL.
Well CVS SBCL supports bivalent streams and the only thing i had to do was - add tbnl-bivalent-streams to features ... now examples work just fine. Ignas Mikalajunas
On Sun, 9 Oct 2005 01:12:48 +0300, Ignas Mikalajunas ignas.mikalajunas@gmail.com wrote:
Well CVS SBCL supports bivalent streams and the only thing i had to do was - add tbnl-bivalent-streams to features ... now examples work just fine.
Thanks for the info. Does that mean one has to add this to *FEATURES* before building SBCL or just before using TBNL? Do you know since when SBCL has bivalent streams?
Thanks, Edi.
Thanks for the info. Does that mean one has to add this to *FEATURES* before building SBCL or just before using TBNL?
Just before using tbnl.
Do you know since when SBCL has bivalent streams?
According to http://constantly.at/ since the end of June, 2005 (not 100% sure though)
Ignas
Ignas Mikalajunas wrote:
Thanks for the info. Does that mean one has to add this to *FEATURES* before building SBCL or just before using TBNL?
Just before using tbnl.
My experience is that :tbnl-bivalent-streams must be added to *FEATURES* before TBNL is _built_.
The source code seems to support this notion as the #:+/- checks will occur at compile time.
It seems that :tbnl-bivalent-streams could be added to features automatically for SBCL by adding :sbcl to the code block on line 309 of specials.lisp:
--- specials.lisp.orig 2005-11-03 11:57:39.000000000 -0500 +++ specials.lisp 2005-11-03 11:58:05.000000000 -0500 @@ -309,7 +309,8 @@ (eval-when (:compile-toplevel :load-toplevel :execute) #+(or (and :allegro :allegro-version>= (version>= 6 0)) :lispworks4.3 - :lispworks4.4) + :lispworks4.4 + :sbcl) (pushnew :tbnl-bivalent-streams *features*))
#+:sbcl
I would not worry tremendously about breaking older versions of SBCL because 1) TBNL is already broken on older versions of SBCL and 2) most SBCL users track pretty close to the latest release.
Cheers,
-- Travis
On Thu, 03 Nov 2005 12:01:57 -0500, Travis Cross travis@crosswirecorp.com wrote:
My experience is that :tbnl-bivalent-streams must be added to *FEATURES* before TBNL is _built_.
The source code seems to support this notion as the #:+/- checks will occur at compile time.
It seems that :tbnl-bivalent-streams could be added to features automatically for SBCL by adding :sbcl to the code block on line 309 of specials.lisp:
--- specials.lisp.orig 2005-11-03 11:57:39.000000000 -0500 +++ specials.lisp 2005-11-03 11:58:05.000000000 -0500 @@ -309,7 +309,8 @@ (eval-when (:compile-toplevel :load-toplevel :execute) #+(or (and :allegro :allegro-version>= (version>= 6 0)) :lispworks4.3
:lispworks4.4)
:lispworks4.4:sbcl)#+:sbcl
I would not worry tremendously about breaking older versions of SBCL because 1) TBNL is already broken on older versions of SBCL and 2) most SBCL users track pretty close to the latest release.
OK, thanks. I'll add that for the next release. I think there are still problems, though - see other message.
Cheers, Edi.
-
Edi Weitz -
Ignas Mikalajunas -
Travis Cross