unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Peter TB Brett <peter@peter-b.co.uk>
Cc: guile-user@gnu.org
Subject: Re: Help needed debugging segfault with Guile 1.8.7
Date: Wed, 01 Dec 2010 20:48:13 +0100	[thread overview]
Message-ID: <m339qhxojm.fsf@unquote.localdomain> (raw)
In-Reply-To: <m38w0ah9g1.fsf@harrington.peter-b.co.uk> (Peter TB Brett's message of "Tue, 30 Nov 2010 19:56:30 +0000")

On Tue 30 Nov 2010 20:56, Peter TB Brett <peter@peter-b.co.uk> writes:

>  - An easily re-usable/embeddable and well-documented REPL, to aid
>    developers in implementing a "Scheme Interaction Window" or similar
>    in their apps.

This is surprisingly difficult to do. A traditional REPL is the bottom
of the main loop of an application (though "application" might be
stretching it); integrating it with other main loops is tricky.

Essentially you need threads. Either pthreads, which bring their own
issues ("what thread is calling my app??? I thought i didn't use
threads?"), coroutines (but since `read' is implemented in C, delimited
continuations that involve the readers are not resumable), or simulated
threads (for example, the gtk repl in guile-gnome that runs recursive
main loops inside soft port readers).

Dunno. Perhaps there are other interfaces that are less repl-like, but
still useful. Suggestions and patches are welcome :-)

>  - An high-level API for passing strings for evaluation, that reports
>    back the results or error information in a way that's easy to deal
>    with from C.

What would this API look like?

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2010-12-01 19:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 12:43 Help needed debugging segfault with Guile 1.8.7 Peter TB Brett
2010-11-10 21:35 ` Peter TB Brett
2010-11-11 10:52   ` Peter Brett
2010-11-11 12:37     ` Thien-Thi Nguyen
2010-11-11 14:22       ` Peter Brett
2010-11-28 11:38         ` Neil Jerram
2010-11-28 17:21           ` Linas Vepstas
2010-11-30 19:56             ` Peter TB Brett
2010-12-01 19:48               ` Andy Wingo [this message]
2010-11-30 19:43           ` Peter TB Brett
2010-12-01 13:46             ` Ludovic Courtès
2010-12-03  7:52               ` Peter TB Brett
2010-11-11  8:22 ` rixed
2010-11-11  8:33 ` Neil Jerram
2010-11-11 13:30 ` Ludovic Courtès

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=m339qhxojm.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-user@gnu.org \
    --cc=peter@peter-b.co.uk \
    /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).