From: Tom Lord <lord@regexps.com>
Cc: rlb@defaultvalue.org, guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: Threads and asyncs
Date: Mon, 2 Sep 2002 18:28:34 -0700 (PDT) [thread overview]
Message-ID: <200209030128.SAA08719@morrowfield.regexps.com> (raw)
In-Reply-To: <87ptvvubst.fsf@becket.becket.net> (tb@becket.net)
> You keep saying "plainly wrong" which is the most infuriating part.
> Seems to me it's *plainly right*.
Yes, well...
[very long list of purely anecdotal reasons why you are full of crap
omitted]
None of which is a solid argument that you are wrong.
So there we are.
ObPolitics: If you think this is merely a friendly design space
disagreement, that will work itself out on the merits of which idea
works out better in practice, think again. Accidental economics of
the situation give significantly greater weight to one side than the
other -- which is an economic bug (at least comperable to standards
for railroad-track sizes; arguably much more serious).
ObPolitics 2: The, arguably politically problematic process by which
the RnRS arose (arises?) also adds lots of noise to any signal that
might be there.
ObPolitics 3: As nearly as I can tell, I'm having much more *fun*
programming in my #f == () implementation than y'all are in your #f !=
() implementation. Nyah nyah!
ObPolitics 4: a *process* to map out the design space for this an
other issues would be more valuable to me, at this juncture, than
continued contextless argument over this particular design issue.
-t
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-09-03 1:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 20:52 Threads and asyncs Marius Vollmer
2002-09-02 21:24 ` Tom Lord
2002-09-02 21:53 ` Marius Vollmer
[not found] ` <87bs7ggiss.fsf@zagadka.ping.de>
2002-09-02 22:24 ` Tom Lord
2002-09-02 23:51 ` Marius Vollmer
2002-09-02 23:02 ` Rob Browning
2002-09-02 23:24 ` Tom Lord
2002-09-02 23:36 ` Tom Lord
2002-09-02 23:52 ` Lynn Winebarger
2002-09-03 0:57 ` Tom Lord
2002-09-03 1:13 ` Thomas Bushnell, BSG
2002-09-03 1:29 ` Tom Lord
2002-09-03 1:31 ` Tom Lord
2002-09-03 1:00 ` Thomas Bushnell, BSG
2002-09-03 1:28 ` Tom Lord [this message]
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:45 ` Tom Lord
2002-09-03 1:48 ` Lynn Winebarger
2002-09-04 23:46 ` Lynn Winebarger
2002-09-05 0:20 ` Tom Lord
2002-09-05 1:45 ` Lynn Winebarger
2002-09-05 2:38 ` Tom Lord
2002-09-05 2:30 ` Thomas Bushnell, BSG
2002-09-05 2:43 ` Tom Lord
2002-09-05 2:40 ` Thomas Bushnell, BSG
2002-09-05 3:00 ` Tom Lord
2002-09-05 2:57 ` Thomas Bushnell, BSG
2002-09-05 3:23 ` Tom Lord
2002-09-05 3:14 ` Lynn Winebarger
2002-09-05 4:00 ` Tom Lord
2002-09-05 3:51 ` Thomas Bushnell, BSG
2002-09-05 4:01 ` Tom Lord
2002-09-05 22:03 ` Lynn Winebarger
2002-09-03 1:34 ` Thomas Bushnell, BSG
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
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=200209030128.SAA08719@morrowfield.regexps.com \
--to=lord@regexps.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=rlb@defaultvalue.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).