Dear all -
Working through the examples for CL-PDF (trying to put together a
quick substitute for R's Sweave literate programming tool) is giving
me some weird errors, for example, evaluation of the EXAMPLE1 function
(error from SLIME below). In general, PDF:WRITE-DOCUMENT function
seems to be unable to take a string or pathname, but throws the
following error (which I tried to resolve by OPENing the proper handle
and passing it):
#<SB-SYS:FD-STREAM for "file /tmp/ex1.pdf" {BEC30D1}> is not a binary
output stream.
[Condition of type SIMPLE-TYPE-ERROR]
Restarts:
0: [RETRY] Retry SLIME interactive evaluation request.
1: [ABORT] Return to SLIME's top level.
2: [TERMINATE-THREAD] Terminate this thread (#<THREAD "worker"
RUNNING {C0EA1A9}>)
Backtrace:
0: (SB-KERNEL:ILL-BOUT #<SB-SYS:FD-STREAM for "file /tmp/ex1.pdf"
{BEC30D1}>)[:EXTERNAL]
1: (SB-IMPL::ANSI-STREAM-WRITE-SEQUENCE #(8 153 115 10 225 210 ...)
#<SB-SYS:FD-STREAM for "file /tmp/ex1.pdf" {BEC30D1}> 0 NIL)
2: (WRITE-SEQUENCE #(8 153 115 10 225 210 ...) #<SB-SYS:FD-STREAM
for "file /tmp/ex1.pdf" {BEC30D1}>)[:EXTERNAL]
This is with SBCL from Debian Unstable: SBCL 1.0.29.11.debian
Now, looking through the code, I'm thinking this might be an SBCL
issue and should be reported there? Or is this a bug with recent
CL-PDF's? Or perhaps I'm mixing and matching packages which
shouldn't be mixed and matched? Insight appreciated, including a
clue-stick if I need one.
best,
-tony
blindgl...@gmail.com
Muttenz, Switzerland.
"Commit early,commit often, and commit in a repository from which we
can easily roll-back your mistakes" (AJR, 4Jan05).
Drink Coffee: Do stupid things faster with more energy!
_______________________________________________
cl-pdf-devel site list
cl-pdf-devel@common-lisp.net
http://common-lisp.net/mailman/listinfo/cl-pdf-devel
