unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Remco Bras" <vrsoft@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Can scm_shell be interrupted?
Date: Sun, 1 Jun 2008 22:58:03 +0100	[thread overview]
Message-ID: <49dd78620806011458y3a400af9hf7e5b7b63e1dd33@mail.gmail.com> (raw)
In-Reply-To: <200805161829.02777.vrsoft@gmail.com>

2008/5/16 Remco Bras <vrsoft@gmail.com>:
> Hello,
>
> after the last exchange in this thread, I wrote and tested a prototype of a
> repl for my app. The code for this is as follows:
>
> int
> exec_guile_shell (void *unused_arg)
> {
>  scm_init_guile();
[...]
> This is run when the app starts, after using scm_c_define_gsubr to define the
> primitive interface my app exports and after scm_c_primitive_load is used to
> read in user-defined scheme files.
[...]
> For the most part, this works fine, but if I use this REPL to evaluate a call
> to one of the functions I have defined using scm_c_define_gsubr, for example
> (stop-repl), the function is unbound in the environment the REPL uses. I've
> tried using scm_interaction_environment() as a second argument to scm_eval
> rather than using scm_primitive_eval, but that did not solve this problem.

What environment (or module) are your gsubrs defined in, and how
exactly does your C code achieve this?

Does exec_guile_shell() run in a separate thread from the thread where
the gsubrs were defined?

       Neil




  reply	other threads:[~2008-06-01 21:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 16:29 Can scm_shell be interrupted? Remco Bras
2008-06-01 21:58 ` Neil Jerram [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-10 20:54 Remco Bras
2008-05-12 20:43 ` Neil Jerram
2008-05-16 15:29   ` Remco Bras

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=49dd78620806011458y3a400af9hf7e5b7b63e1dd33@mail.gmail.com \
    --to=neiljerram@googlemail.com \
    --cc=guile-user@gnu.org \
    --cc=vrsoft@gmail.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).