unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org, guile-devel@gnu.org
Subject: Re: [PATCH][PR guile/17247] Block SIGCHLD while initializing Guile
Date: Mon, 01 Sep 2014 05:36:59 +0300	[thread overview]
Message-ID: <8338ccgj78.fsf@gnu.org> (raw)
In-Reply-To: <CAP9bCMTNsoi6AhQxJtzjc6=o9iHi8TXkX32OiKbArAuAnsjZUQ@mail.gmail.com>

> Date: Sun, 31 Aug 2014 13:20:48 -0700
> From: Doug Evans <xdje42@gmail.com>
> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>, guile-devel <guile-devel@gnu.org>
> 
> Users are going to want to start threads.

If users want threads in Guile, they can use Guile.

In GDB, Guile is just an extension language.  I see no catastrophe in
saying there are some restrictions to what a Guile extension in GDB
can and cannot do.


  reply	other threads:[~2014-09-01  2:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m31trwv5o1.fsf@sspiff.org>
     [not found] ` <834mwsh2nu.fsf@gnu.org>
2014-08-31 20:20   ` [PATCH][PR guile/17247] Block SIGCHLD while initializing Guile Doug Evans
2014-09-01  2:36     ` Eli Zaretskii [this message]
2014-09-01 10:11       ` Ludovic Courtès
2014-09-01 14:39         ` Eli Zaretskii
2014-09-01 16:18           ` Ludovic Courtès
2014-09-01 17:10             ` Eli Zaretskii
2014-09-01 22:04               ` Doug Evans
2014-09-02 15:25                 ` Eli Zaretskii
2014-09-05  8:26                   ` Doug Evans
2014-09-05  8:48                     ` Eli Zaretskii
2014-09-05 10:51                       ` Pedro Alves
2014-09-05 11:51                         ` Eli Zaretskii
2014-09-05 12:48                           ` Pedro Alves
2014-09-05 11:50                       ` Ludovic Courtès
2014-09-01 12:48     ` Gary Benson
2014-09-01 16:34       ` Doug Evans

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=8338ccgj78.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=guile-devel@gnu.org \
    --cc=xdje42@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).