From: steve tell <tell@telltronics.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: ANN: Guile-Charting 0.1.0 released
Date: Sun, 10 Jun 2007 22:40:57 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0706102205390.4830@ariel.telltronics.org> (raw)
In-Reply-To: <1181319366.4168.6.camel@localhost.localdomain>
On Fri, 8 Jun 2007, Andy Wingo wrote:
> ... using Guile-Cairo, and a day and a half later here we are!
>
> (make-bar-chart "Average Height at Iihenda JSS"
> '(("Grade 9" (150 "Boys") (140 "Girls"))
> ("Grade 10" (153 "Boys") (147 "Girls")))
> :write-to-png "/tmp/graph.png")
I was looking for a guile-cairo example, so I gave gave this a try, by
adding a "(use-modules (charting))" to those four
lines, and running from the guile-charting-0.1.0
build directory with "env guile -s ../examples/height.scm".
It fails with
ERROR: Unbound variable: :write-to-png
Changing only ":write-to-png" to "#:write-to-png" changes the session to:
$ cat ../examples/height.scm
(use-modules (charting))
(make-bar-chart "Average Height at Iihenda JSS"
'(("Grade 9" (150 "Boys") (140 "Girls"))
("Grade 10" (153 "Boys") (147 "Girls")))
#:write-to-png "/tmp/graph.png")
$ env guile -s ../examples/height.scm
ERROR: Unbound variable: :y-axis-ticks
$
This looks like a problem of the #: vs. : style of keyword-arguments,
but adding "(read-set! keywords 'prefix)" to the
example doesn't fix things, but simply changes the error to
ERROR: Unbound variable: #{:y-axis-ticks}#
All this using guile-cairo-1.3.91, cario-1.2.6, and fedora core's
guile-1.8.0-8.20060831cvs
Steve
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2007-06-11 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 16:16 ANN: Guile-Charting 0.1.0 released Andy Wingo
2007-06-11 2:40 ` steve tell [this message]
2007-06-12 21:51 ` Andy Wingo
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0706102205390.4830@ariel.telltronics.org \
--to=tell@telltronics.org \
--cc=guile-user@gnu.org \
--cc=wingo@pobox.com \
/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).