From: Kevin Ryde <user42@zip.com.au>
To: guile-devel@gnu.org
Subject: Re: scm_cell vs threads build option
Date: Tue, 04 Sep 2007 10:46:27 +1000 [thread overview]
Message-ID: <873axv9s0s.fsf@zip.com.au> (raw)
In-Reply-To: <87lkbovccu.fsf@raven.defaultvalue.org> (Rob Browning's message of "Sun, 02 Sep 2007 17:09:21 -0700")
Rob Browning <rlb@defaultvalue.org> writes:
>
> Perhaps Guile should use a different name for the threaded libs if
> they're not compatible.
I suppose that'd help against mysterious crashes, but leaves the same
problem as in every incompatibility, ie. that add-ons do or don't
switch, making various combinations unusable, or forcing everyone to
recompile in lock-step, etc.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-09-04 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 0:33 scm_cell vs threads build option Kevin Ryde
2007-09-03 0:09 ` Rob Browning
2007-09-03 7:28 ` Ludovic Courtès
2007-09-04 5:22 ` Rob Browning
2007-09-04 0:46 ` Kevin Ryde [this message]
2007-09-03 7:34 ` 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=873axv9s0s.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@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).