From: a@9srv.net
To: 9fans@cse.psu.edu
Subject: RE: [9fans] fp stack overflow -- hypot
Date: Fri, 5 Mar 2004 10:14:01 -0500 [thread overview]
Message-ID: <92c0a65f5d11f7e5fcf9b1bf72fa3d58@9srv.net> (raw)
In-Reply-To: <D691F041928C1049808A0670D2252BE006334122@nj9620exch001u.mh.lucent.com>
i'd rather see ape stick around. imperfect, sure, but certainly
still useful. there's a significant body of code that i either
run on plan 9 (ghostscript, troff) or would like to see running
on plan 9. given a finite set of plan 9 development resources
(read: people), i'd rather see our efforts spent on other things
than porting (and keeping current) the stuff we already have
under ape.
that aside, for the few programs i've written for unix, i've
found ape to be a wonderful testbed for conformance and
likely portability.
granted, today i'd probably use rsc's 9libs instead...
ア
next prev parent reply other threads:[~2004-03-05 15:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 12:13 Trickey, Howard W (Howard)
2004-03-05 12:19 ` boyd, rounin
2004-03-05 12:24 ` Gorka Guardiola Múzquiz
2004-03-05 12:30 ` boyd, rounin
2004-03-05 12:36 ` Gorka Guardiola Múzquiz
2004-03-05 12:38 ` Fco.J.Ballesteros
2004-03-05 12:49 ` boyd, rounin
2004-03-05 12:46 ` boyd, rounin
2004-03-05 12:24 ` David Tolpin
2004-03-05 12:37 ` boyd, rounin
2004-03-05 15:14 ` a [this message]
2004-03-05 15:25 ` boyd, rounin
2004-03-08 10:14 ` Douglas A. Gwyn
2004-03-08 10:59 ` Bruce Ellis
2004-03-09 9:47 ` Douglas A. Gwyn
2004-03-09 12:19 ` boyd, rounin
2004-03-09 22:58 ` Bruce Ellis
2004-03-11 9:38 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2004-03-04 22:18 David Tolpin
2004-03-04 23:08 ` Bruce Ellis
2004-03-04 23:10 ` boyd, rounin
2004-03-04 23:53 ` Bruce Ellis
2004-03-04 23:54 ` David Tolpin
2004-03-05 6:32 ` Charles Forsyth
2004-03-06 10:24 ` Bruce Ellis
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92c0a65f5d11f7e5fcf9b1bf72fa3d58@9srv.net \
--to=a@9srv.net \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).