From: Bruce Korb <bkorb@veritas.com>
Subject: Re: PLEASE: debugging embedded guile code
Date: Fri, 16 May 2003 19:33:45 -0700 [thread overview]
Message-ID: <3EC59F89.A9E9B958@veritas.com> (raw)
In-Reply-To: 3EC582D5.6FB4D63C@veritas.com
Bruce Korb wrote:
> The issue here is that gh_eval_str processes the *entire* string and
> returns the result of the last expression. This "eval-client-input"
> function does not behave in the same way:
> ... How do I make
> that ``(list (primitive-eval (read p)))'' thing into a loop that
> yields the last value?
Answer: (begin ... )
EXCEPT: the problem now is that instead of getting the final result,
the returned SCM is an SCM *PAIR*, not the value I need.
That was because the result of the primitive-eval should not
be listified:
> (list (primitive-eval (read p))) ) ) )
OK. Here's what I have now:
> (use-modules (ice-9 stack-catch))
> (use-modules (ice-9 debug))
>
> (read-enable 'positions)
>
> (define (eval-client-input str)
> (stack-catch #t
>
> (lambda ()
> (call-with-input-string
> (string-append "(begin " str ")") ;;; <<--== ICK!!
> (lambda (p)
> (set-port-filename! p (tpl-file))
> (set-port-line! p (string->number (tpl-file-line "%2$d")))
> (primitive-eval (read p)) ) ) )
>
> (lambda (key . args)
> (apply display-error
> (fluid-ref the-last-stack)
> (current-error-port)
> args)
> (set! stack-saved? #f)
> (error "exiting") )
> ) )
It's really close, but for two problems:
1. "primitive-eval" doesn't seem to like comments:
> ERROR: In procedure list:
> ERROR: end of file in ./auto_gen.tpl
> Error in template ./auto_gen.tpl, line 675
> DEFINITIONS ERROR in ./auto_gen.tpl line 675 for autogen.texi:
> exiting
> Failing Guile command: = = = = =
>
> (shell "[ -f autogen.texi.ori ] && rm -f autogen.texi.ori
> rm -rf ${tempdir}")
> (set-writable #t)
>
> ;; Local Variables:
> ;; indent-tabs-mode: nil
> ;; mode: texinfo
> ;; End:
>
> =================================
2. if you notice, the lines beginning with "ERROR:" still don't
have the line number, but I see the file name there!!
(Please note: by this point, I've run through many templates.
Likely this is the only one with scheme comments at the end.)
3. It seems (current-error-port) is set to something that got
squirreled away when gh_enter got called. I've scoured the
manual now. How do I simply set error port to the current stderr?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-17 2:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.3.96.1030209200016.26546A-100000@anh>
2003-02-25 14:19 ` PLEASE: debugging embedded guile code Joris van der Hoeven
2003-02-25 14:36 ` Dale P. Smith
2003-04-26 14:51 ` Neil Jerram
2003-04-26 16:40 ` Bruce Korb
2003-04-26 19:12 ` Neil Jerram
2003-04-26 20:13 ` Bruce Korb
2003-04-27 20:49 ` Neil Jerram
2003-04-27 21:57 ` Bruce Korb
2003-04-28 15:54 ` Paul Jarc
2003-04-28 16:07 ` Bruce Korb
2003-04-28 19:21 ` Neil Jerram
2003-04-28 20:06 ` Bruce Korb
2003-04-28 20:58 ` Neil Jerram
2003-05-16 17:19 ` Bruce Korb
2003-05-16 19:23 ` Neil Jerram
2003-05-16 20:27 ` Bruce Korb
2003-05-16 21:21 ` Rob Browning
2003-05-16 21:56 ` Bruce Korb
2003-05-17 0:31 ` Bruce Korb
2003-05-17 2:33 ` Bruce Korb [this message]
2003-05-19 15:00 ` Paul Jarc
2003-04-28 13:52 ` Mikael Djurfeldt
2003-04-28 19:26 ` Neil Jerram
2003-04-30 0:13 ` SRFI 34 Neil Jerram
2003-05-17 0:45 ` Marius Vollmer
2003-05-17 9:39 ` Neil Jerram
2003-05-17 20:36 ` Marius Vollmer
2004-03-07 18:34 ` Neil Jerram
2003-04-26 14:45 ` PLEASE: debugging embedded guile code Neil Jerram
[not found] <Pine.GSO.4.33.0304261706460.1619-100000@sunanh>
2003-04-26 15:34 ` Neil Jerram
2003-04-26 15:40 ` Joris van der Hoeven
2003-04-26 19:30 ` Neil Jerram
2003-04-27 8:40 ` Joris van der Hoeven
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=3EC59F89.A9E9B958@veritas.com \
--to=bkorb@veritas.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).