public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gerard Jungman <jungman@lanl.gov>
To: gsl-discuss@sourceware.org
Subject: Re: [Help-gsl] GSL and C99 standard
Date: Thu, 10 Apr 2008 19:19:00 -0000	[thread overview]
Message-ID: <1207855079.6909.74.camel@manticore.lanl.gov> (raw)
In-Reply-To: <87wsn5irwq.wl%bjg@network-theory.co.uk>


The other problem with C99 complex types is that they
introduce yet another possibility for variation in
binary layout, alignment, etc.

The three "complex" types that need to play together are
Fortran COMPLEX, C++ std::complex, and now C99 complex.
And there are (as of yet, AFAIK) no compatibility guarantees
for these on any platform, even though they should
probably work "most of the time".

It's really a stupid situation. At the very least, the C++
and C99 committees should decide on something. But they
probably never will.

--
Gerard Jungman


On Thu, 2008-04-10 at 17:41 +0100, Brian Gough wrote:
> At Thu, 10 Apr 2008 00:47:06 +0800,
> Hongzheng Wang wrote:
> > Although C99 standard has not been fully implemented in GCC, several
> > new key features, e.g. complex type support, are indeed useful to
> > numerical computations.  So, I wonder if there is any plan for the
> > development of GSL to embrass C99 standard and adopt these useful
> > offers.
> 
> Do complex types acually work now? I haven't checked for a while but
> according to http://gcc.gnu.org/gcc-4.3/c99status.html they weren't
> completed.
> 
> I would like to keep C89 compatibility, which limits the extent to
> which any new features can be used.


  reply	other threads:[~2008-04-10 19:19 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 [this message]
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

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=1207855079.6909.74.camel@manticore.lanl.gov \
    --to=jungman@lanl.gov \
    --cc=gsl-discuss@sourceware.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).