unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Nigel Warner <nwarner84@gmail.com>
To: 16726@debbugs.gnu.org
Subject: bug#16726: Possible bug?
Date: Wed, 12 Feb 2014 00:51:29 +0000	[thread overview]
Message-ID: <52FAC591.2060607@gmail.com> (raw)

#|
   This file is an extract of a documentation and code assembly process
   which works from a list of elements and attributes. Perhaps I'm
   being particularly stupid but I can't see why the function
   emit-groff-bug? does not work as expected.

   Version is 2.09 GCC is 4.7.3 on 64 bit Ubuntu self compiled.

   BTW, thanks to all the developers for a wonderful program. I am
   greatly enjoying programming in Guile.

|#
(define-syntax say
   (syntax-rules ()
    ((say format-string ...)
     (format #t format-string ...))
    ((say format-string)
     (format #t format-string))))

(define-syntax emit
   (syntax-rules ()
     ((emit a-string)
      (say (string-append a-string "\n")))
     ((emit a-string ...)
      (say (string-append (format #f a-string ...) "\n")))))


(define canvas-description
"A canvas object specifies the two dimensional area on which graphics
objects are painted.

The function `canvas' requires at least one parameter, the name by
which the canvas will be known. If there is already a canvas by that
name in the canvas-table then it will be used as the current
canvas. If not then a new canvas will be created using the default
values unless overridden by keyword value pairs passed to the
function.")

(define thoth-canvas
   `((#:object-name . canvas)
     (#:description . ,canvas-description)
     (#:attributes
       (viewbox none "Creates user coordinate space")
       (background none "Creates a background rectangle")
       (transform none "Transformation object"))))

(define (process-attributes-for-groff lst)
   (for-each
     (lambda (element)
      (emit ".attribute ~a ~a" (list-ref element 0)
                               (list-ref element 1))
      (emit ".start-hint")
      (emit "~a" (list-ref element 2))
      (emit ".end-hint"))
    lst))

(define (emit-groff lst)
   (for-each
    (lambda (element)
      (cond ((and (pair? element)
                  (eq? #:object-name (car element)))
             (emit ".object-name ~a" (cdr element)))
            ((and (pair? element)
                  (eq? #:description (car element)))
             (emit ".start-description")
             (emit "~a" (cdr element))
             (emit ".end-description"))
            ((and (list? element)
                  (eq? #:attributes (car element)))
             (process-attributes-for-groff (cdr element)))
            (else
             (emit "emit-groff | unknown list type")
             (throw 'snafu))))
    lst))

(define (emit-groff-bug? lst)
   (for-each
    (lambda (element)
      (cond ((pair? element)
             (cond ((eq? #:object-name (car element))
                    (emit ".object-name ~a" (cdr element)))
                   ((eq? #:description (car element))
                    (emit ".start-description")
                    (emit "~a" (cdr element))
                    (emit ".end-description"))))
            ((list? element)
             (cond ((eq? #:attributes (car element)))
                   (process-attributes-for-groff (cdr element)))
             (else
              (emit "emit-groff | unknown list type")
              (throw 'snafu)))))
    lst))

  (emit "------------- working")
  (emit-groff thoth-canvas)
  (emit "------------- not working")
  (emit-groff-bug? thoth-canvas)






             reply	other threads:[~2014-02-12  0:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  0:51 Nigel Warner [this message]
2014-02-12  3:40 ` bug#16726: Possible bug? Mark H Weaver

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=52FAC591.2060607@gmail.com \
    --to=nwarner84@gmail.com \
    --cc=16726@debbugs.gnu.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).