[cl-typesetting-devel] Non-macro interface to building documents.
Peter Seibel
peter at javamonkey.com
Mon Feb 16 20:03:03 UTC 2004
"Marc Battyani" <marc.battyani at fractalconcept.com> writes:
> Marc Battyani <marc.battyani at fractalconcept.com> writes:
>
>
> > (loop for (name tel age) in '(("Erik Enge" "555-1234" "25")
> > ("Erik Enge" "555-1234" "25")
> > ("Erik Enge" "555-1234" "25")
> > ("Erik Enge" "555-1234" "25")
> > ("Erik Enge" "555-1234" "25"))
> > do
> > (typeset:row ()
> > (typeset:cell ()
> > (typeset:paragraph ()
> > "Name"))
> > (typeset:cell ()
> > (typeset:paragraph ()
> > name)))
> > (typeset:row ()
> > (typeset:cell ()
> > (typeset:paragraph ()
> > "Telephone"))
> > (typeset:cell ()
> > (typeset:paragraph ()
> > tel)))
> > (typeset:row ()
> > (typeset:cell ()
> > (typeset:paragraph ()
> > "Age"))
> > (typeset:cell ()
> > (typeset:paragraph ()
> > age))))))))
>
> Warning: the table are not multi-page so far. So you should use a
> table for each row if you don't want to have problems when the table
> height exceed the draw-block height.
So it seems that when a table is too big to fit in a page the
typesetting engine gets stuck in a loop, allocating more and more
memory. Unless someone's got a multi-page-table patch waiting in the
wings it might be nice to at least detect that condition and emit a
warning, giving up on the table?
-Peter
--
Peter Seibel peter at javamonkey.com
Lisp is the red pill. -- John Fraser, comp.lang.lisp
More information about the cl-typesetting-devel
mailing list