cl-who-devel August 2008

cl-who-devel@common-lisp.net

4 participants
4 discussions

[cl-who-devel] strange behaviour: package and/or macro relevant?
by olivier buechel 26 Aug '08

26 Aug '08

This works: (in-package :cl-user) (let* ((txt1 "hallo") (txt2 "yellow")) (cl-who:show-html-expansion (str nil :indent t) ((:a) txt1 txt2))) This does not work and hell breaks out when compiling: (defpackage :dummy-package (:use :cl :cl-user :cl-who)) (in-package :dummy-package) (let* ((txt1 "hallo") (txt2 "yellow")) (cl-who:show-html-expansion (str nil :indent t) ((:a) txt1 txt2))) ==> (LET ((STR STR)) (PROGN (WRITE-STRING " <a> " LET ((#:G1 NIL)) (WHEN #:G1 (PRINC #:G1 STR))) TXT1 (WRITE-STRING " " LET ((#:G2 NIL)) (WHEN #:G2 (PRINC #:G2 STR))) TXT2 (WRITE-STRING " </a>" LET ((#:G3 NIL)) (WHEN #:G3 (PRINC #:G3 STR))))) Well, I really don't get it with packages, so I just tried around and found that this code here works: (defpackage :dummy-package (:use :cl :cl-user :cl-who)) (in-package :dummy-package) (let* ((txt1 "hallo") (txt2 "yellow")) (cl-who:show-html-expansion (s nil :indent t) ((:a) txt1 txt2))) So kind-of it's not the package alone the problem, somehow it's the combination of package and using str in macro Ha, just tried with fmt instead of str: same problem Hint: Maybe no protection with gensym? And why does it work in cl-user?!? Using cl-who-0.11.1 And yes, I was in hell... And now (after changing str to s) I want just to understand what happend to me. thanks olli

2 1

[cl-who-devel] Changing *attribute-quote-char*
by Andrei Stebakov 16 Aug '08

16 Aug '08

By default the variable is initialized to #\' If I want to change it to #\" via local binding I still get the single quotes in the resulting string. (let ((*attribute-quote-char* #\")) (with-html-output-to-string (*standard-output* nil :prologue nil :indent nil) (:html (:head (:title "title") (:meta :name "DESCRIPTION" :content "description") (:meta :name "KEYWORDS" :content "keywords"))))) I get: "<html><head><title>title</title><meta name='DESCRIPTION' content='description' /><meta name='KEYWORDS' content='keywords' /></head></html>" Is it possible to make a local new binding or I should change it only globally? Thank you, Andrew

3 9

[cl-who-devel] Macro expansion...
by Andrei Stebakov 16 Aug '08

16 Aug '08

I am trying to incorporate parenscript into cl-who tree. I tried to insert a small macro but for some reasons I get various errors linke "cl-who:fmt not defined" or ":script not defined". I guess I need help to figure out the way macros work with cl-who... (defmacro js-body (&rest body) `(:script :type "text/javascript" (fmt (ps ,@body)))) (with-html-output-to-string (*standard-output* nil :prologue nil :indent nil) (:html (:head (:title "Some title")) (js-body (defun some-func () (alert "Hello!"))))) I think parenscript is not really relevant to the task, so I am looking for some help to figure out why I have these expansion errors. BTW, when I run (macroexpand '(with-html-output-to-string (*standard-output* nil :prologue nil :indent nil) (:html (:head (:title "Some title")) (js-body (defun some-func () (alert "Hello!")))))) I get: (LET ((*STANDARD-OUTPUT* (MAKE-STRING-OUTPUT-STREAM :ELEMENT-TYPE 'CHARACTER))) (UNWIND-PROTECT (PROGN (WITH-HTML-OUTPUT (*STANDARD-OUTPUT* NIL :PROLOGUE NIL :INDENT NIL) (:HTML (:HEAD (:TITLE "Some title")) (JS-BODY (DEFUN SOME-FUNC () (ALERT "Hello!")))))) (CLOSE *STANDARD-OUTPUT*)) (GET-OUTPUT-STREAM-STRING *STANDARD-OUTPUT*)) The HyperSpec says: "*macroexpand* <#macroexpand> repeatedly expands *form*until it is no longer a *macro form"* <26_glo_m.htm#macro_form> Why js-body or with-html-output doesn't get expanded in this case? I am using sbcl 1.0.18 on Ubuntu. Thank you! Andrew

2 1

[cl-who-devel] with-html-output-to-string (str)
by Victor Kryukov 09 Aug '08

09 Aug '08

The following code produces errors on two of my systems (Linux and Mac) for both CLISP and SBCL: (require 'asdf) (asdf:oos 'asdf:load-op :cl-who) (defpackage :test (:use :cl :cl-who)) (in-package :test) (with-html-output-to-string (str) (:html (:title "test"))) It looks like a bug, macro variable capture, to me, but it may well be my misunderstanding/misuse of CL-WHO. I'd appreciate your comments, as usual. -- Yours Sincerely, Victor Kryukov

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

cl-who-devel August 2008