public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Damien MATTEI <Damien.Mattei@unice.fr>
To: Kawa mailing list <kawa@sourceware.org>
Subject: xml literals
Date: Mon, 15 May 2017 14:11:00 -0000	[thread overview]
Message-ID: <201705151611.09622.Damien.Mattei@unice.fr> (raw)

hello Per,
i try to use XML literals in code and i have errors i do not have in REPL:
compiling this:
(set! html-literal-table-data-code
			      (html:td result))

where result is a string ,or even a simple code:

(html:td "foo")
i got this error in my code:
java -cp /usr/local/share/java/kawa-2.1.jar:/home/mattei/NetBeansProjects/Sidonie/build/web/WEB-INF/classes kawa.repl -C DBtoWebObserversKawa.scm
(compiling DBtoWebObserversKawa.scm to eu.oca.kawafunct.DBtoWebObserversKawa)
Exception in thread "main" java.lang.Error: gnu.kawa.xml.MakeElement does not implement Externalizable
        at gnu.expr.LitTable.error(LitTable.java:103)
        at gnu.expr.LitTable.writeObject(LitTable.java:271)
        at gnu.expr.LitTable.emit(LitTable.java:66)
        at gnu.expr.Compilation.generateBytecode(Compilation.java:2433)
        at gnu.expr.Compilation.process(Compilation.java:2172)
        at gnu.expr.ModuleInfo.loadByStages(ModuleInfo.java:302)
        at gnu.expr.ModuleInfo.loadByStages(ModuleInfo.java:284)
        at kawa.repl.compileFiles(repl.java:753)
        at kawa.repl.processArgs(repl.java:434)
        at kawa.repl.main(repl.java:793)

at REPL all is ok:
 kawa --output-format html
#|kawa:1|# (html:em "hello!")
<em>hello!</em>
#|kawa:2|# (html:b "hello!")
<b>hello!</b>
#|kawa:3|# (html:td "toto")
<td>toto</td>
#|kawa:4|# (html:tr (html:td "foo") (html:td "bar"))
<tr><td>foo</td><td>bar</td></tr>
#|kawa:5|# (define toto "titi")
#|kawa:6|# (html:td toto)
<td>titi</td>

Damien

             reply	other threads:[~2017-05-15 14:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-15 14:11 Damien MATTEI [this message]
2017-05-15 16:06 ` Per Bothner
2017-05-15 16:50   ` Damien MATTEI
2017-05-15 16:57     ` Damien MATTEI
2017-05-15 18:51       ` Per Bothner
2017-05-22  9:26         ` Damien MATTEI
2017-05-22 10:14           ` Sudarshan S Chawathe
2017-05-22 13:44             ` Damien MATTEI
2017-05-22 13:55               ` Damien MATTEI
2017-05-22 15:44           ` Per Bothner
     [not found]             ` <CADEOadc_87ON2=Tsjd+Ca4d90GoeKABpR3vsrHiP=5SMTKPNZQ@mail.gmail.com>
2017-05-23 13:11               ` Fwd: " Damien Mattei
2017-05-23 19:36           ` Per Bothner
2017-06-06  9:26         ` Damien MATTEI
2017-06-07 14:17           ` Damien MATTEI
2017-06-07 14:36             ` Damien MATTEI
2017-06-07 16:24             ` Per Bothner
2017-06-07 18:16               ` Per Bothner
2017-06-09 15:13                 ` Damien MATTEI
2017-06-09 18:17                   ` Per Bothner
2017-06-10 17:22                     ` Per Bothner
2017-06-13  9:15                     ` Damien MATTEI
2017-06-13  9:37                       ` Damien MATTEI
2017-06-13 17:21                       ` Per Bothner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201705151611.09622.Damien.Mattei@unice.fr \
    --to=damien.mattei@unice.fr \
    --cc=kawa@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).