From: Tom Lord <lord@regexps.com>
Cc: lord@regexps.com
Subject: Re: Threads and asyncs
Date: Mon, 2 Sep 2002 16:36:48 -0700 (PDT) [thread overview]
Message-ID: <13330.2750801251$1031009020@news.gmane.org> (raw)
In-Reply-To: <200209022324.QAA08246@morrowfield.regexps.com> (message from Tom Lord on Mon, 2 Sep 2002 16:24:35 -0700 (PDT))
> If Guile never budges on the stack issue, I would still be
> inclined to see it as an implementation optimized for cases
> when the C stack is used heavily.
And, not to reopen old wounds or restart old fights ---
RnRS is plainly wrong on (eq? #f '()) .... that's the biggest
obstacle.
Indeed, after resuming hacking emacs lisp in recent history, I'm
starting to think that the old CL bit of:
(car nil) => nil
(cdr nil) => nil
is also not a bad idea. "Protective errors" are often wrong.
-t
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-09-02 23:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87it1oglmq.fsf@zagadka.ping.de>
2002-09-02 21:24 ` Threads and asyncs Tom Lord
[not found] ` <200209022124.OAA07625@morrowfield.regexps.com>
2002-09-02 21:53 ` Marius Vollmer
2002-09-02 22:24 ` Tom Lord
[not found] ` <200209022224.PAA07962@morrowfield.regexps.com>
2002-09-02 23:51 ` Marius Vollmer
2002-09-02 23:02 ` Rob Browning
[not found] ` <87k7m43si7.fsf@raven.i.defaultvalue.org>
2002-09-02 23:24 ` Tom Lord
[not found] ` <200209022324.QAA08246@morrowfield.regexps.com>
2002-09-02 23:36 ` Tom Lord [this message]
[not found] ` <200209022336.QAA08304@morrowfield.regexps.com>
2002-09-02 23:52 ` Lynn Winebarger
[not found] ` <0209021852361X.19624@locke.free-expression.org>
2002-09-03 0:57 ` Tom Lord
[not found] ` <200209030057.RAA08617@morrowfield.regexps.com>
2002-09-03 1:13 ` Thomas Bushnell, BSG
[not found] ` <87admzub73.fsf@becket.becket.net>
2002-09-03 1:29 ` Tom Lord
2002-09-03 1:31 ` Tom Lord
2002-09-03 1:00 ` Thomas Bushnell, BSG
[not found] ` <87ptvvubst.fsf@becket.becket.net>
[not found] ` <200209030128.SAA08719@morrowfield.regexps.com>
2002-09-03 1:23 ` RnRS process/history/documentation (was Re: Threads and asyncs) Lynn Winebarger
2002-09-03 1:27 ` Threads and asyncs Rob Browning
2002-09-03 1:34 ` Thomas Bushnell, BSG
[not found] ` <87u1l73ls1.fsf@raven.i.defaultvalue.org>
2002-09-03 1:45 ` Tom Lord
2002-09-03 1:48 ` Lynn Winebarger
2002-09-03 1:28 ` Tom Lord
2002-09-03 18:06 ` Marius Vollmer
2002-09-04 0:28 ` NIIBE Yutaka
2002-09-04 18:02 ` Marius Vollmer
2002-09-04 22:30 ` NIIBE Yutaka
2002-09-02 20:52 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='13330.2750801251$1031009020@news.gmane.org' \
--to=lord@regexps.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).