From: Scott Robert Ladd <coyote@coyotegulch.com>
To: Steven Bosscher <stevenb@suse.de>
Cc: Toon Moene <toon@moene.indiv.nluug.nl>,
Robert Dewar <dewar@gnat.com>,
Luchezar Belev <l_belev@yahoo.com>,
gcc@gcc.gnu.org
Subject: Re: why not consfold sin(const)
Date: Tue, 21 Sep 2004 05:55:00 -0000 [thread overview]
Message-ID: <414F6AC8.2040203@coyotegulch.com> (raw)
In-Reply-To: <200409210128.23686.stevenb@suse.de>
Steven Bosscher wrote:
>> That's not really a flippant remark. How far do we go to force numerical performance in C?
>
> Since all languages try to be general purpose nowadays (class inheritance in Fortran, whee!), probably pretty far!
Call me an old stick-in-the-mud, but I always preferred programming languages (and programs) that have specific applicability;
combine different tools to accomplish heterogeneous tasks.
Then again, I'm a bearded, balding Unix geek who doesn't seem compatible with a world driven by marketing... ;)
--
Scott Robert Ladd
site: http://www.coyotegulch.com
blog: http://chaoticcoyote.blogspot.com
next prev parent reply other threads:[~2004-09-20 23:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 16:02 Luchezar Belev
2004-09-19 18:00 ` Robert Dewar
2004-09-19 19:17 ` Luchezar Belev
2004-09-19 19:31 ` Robert Dewar
2004-09-19 19:55 ` Luchezar Belev
2004-09-19 20:25 ` Robert Dewar
2004-09-19 20:34 ` Luchezar Belev
2004-09-19 20:56 ` Zack Weinberg
2004-09-20 8:15 ` Kai Henningsen
2004-09-19 21:12 ` Robert Dewar
2004-09-19 20:53 ` Timothy J.Wood
2004-09-19 22:41 ` Robert Dewar
2004-09-20 0:31 ` Timothy J.Wood
2004-09-20 4:27 ` Robert Dewar
2004-09-20 5:44 ` Dale Johannesen
2004-09-20 19:43 ` Toon Moene
2004-09-20 20:34 ` Kaveh R. Ghazi
2004-09-20 23:31 ` Robert Dewar
2004-09-21 0:13 ` Scott Robert Ladd
2004-09-21 5:18 ` Steven Bosscher
2004-09-21 5:55 ` Scott Robert Ladd [this message]
2004-09-23 11:35 Bradley Lucier
2004-09-23 23:04 ` Toon Moene
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=414F6AC8.2040203@coyotegulch.com \
--to=coyote@coyotegulch.com \
--cc=dewar@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=l_belev@yahoo.com \
--cc=stevenb@suse.de \
--cc=toon@moene.indiv.nluug.nl \
/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).