From: Kevin Ryde <user42@zip.com.au>
Subject: Re: doco scm_remember_upto_1
Date: Sat, 24 May 2003 11:19:37 +1000 [thread overview]
Message-ID: <87vfw1i1jq.fsf@zip.com.au> (raw)
In-Reply-To: <87r86rqa6m.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Thu, 22 May 2003 10:21:21 -0500")
Rob Browning <rlb@defaultvalue.org> writes:
>
> So what level of preemption are we planning to support, or
> rather for what kind of preemption should we be coding defensively?
Some guidance in the smob section of the manual will no doubt be
vital, one way or another, for authors of add-ons.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-24 1:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 23:15 doco scm_remember_upto_1 Kevin Ryde
2003-05-22 7:07 ` Rob Browning
2003-05-22 9:42 ` Marius Vollmer
2003-05-22 15:21 ` Rob Browning
2003-05-24 1:19 ` Kevin Ryde [this message]
2003-05-30 0:04 ` Kevin Ryde
2003-06-01 21:41 ` Marius Vollmer
2003-06-11 23:07 ` Kevin Ryde
2003-06-18 23:36 ` Marius Vollmer
2003-06-21 23:02 ` Kevin Ryde
2003-07-27 14:49 ` Marius Vollmer
2003-05-30 13:26 ` Marius Vollmer
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=87vfw1i1jq.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).