From: "Hongzheng Wang" <wanghz@gmail.com>
To: "Heikki Orsila" <shd@modeemi.fi>
Cc: "Brian Gough" <bjg@gnu.org>,
gsl-discuss@sourceware.org, help-gsl@gnu.org
Subject: Re: [Help-gsl] GSL and C99 standard
Date: Tue, 15 Apr 2008 15:12:00 -0000 [thread overview]
Message-ID: <b954b2060804150811y5ecab11dy9093ee54058c4aa1@mail.gmail.com> (raw)
In-Reply-To: <20080415105854.GF24451@jolt.modeemi.cs.tut.fi>
> The benefit of C99 is common conventions that are portable between
> projects. The new floating point stuff is probably useful for GSL, but I
> see C99 being much more than that. It makes general coding easier.
Agree.
Basically, I think the problem is not just what benefits we could get
when utilizing the new features of C99. More important thing, in my
opinion, is that GSL must be ready for these welcome elements
introduced by the new standard. Let's still take complex number
support as an example. When full C99 support is ready and gets
certain applications in the future (some people even argue if this
will be true, but I believe it), a user new to GSL may have already a
plenty of codes built on the standard complex type support and would
feel confused if GSL still uses current non-standard complex number
mechanism. Such incompatiblities between GSL and standard would harm
the development of GSL and even cause divergence among potential
users.
--
HZ
prev parent reply other threads:[~2008-04-15 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b954b2060804090947j2574cf96y4ce9262b2fd55e77@mail.gmail.com>
2008-04-10 16:42 ` Brian Gough
2008-04-10 19:19 ` Gerard Jungman
2008-04-11 8:00 ` Hongzheng Wang
2008-04-11 12:41 ` Heikki Orsila
2008-04-15 10:37 ` Brian Gough
2008-04-15 11:00 ` Heikki Orsila
2008-04-15 15:12 ` Hongzheng Wang [this message]
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=b954b2060804150811y5ecab11dy9093ee54058c4aa1@mail.gmail.com \
--to=wanghz@gmail.com \
--cc=bjg@gnu.org \
--cc=gsl-discuss@sourceware.org \
--cc=help-gsl@gnu.org \
--cc=shd@modeemi.fi \
/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).