linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: complex variable
Date: Mon, 13 Sep 2004 23:57:42 +0200	[thread overview]
Message-ID: <20040913215742.GZ19967@lug-owl.de> (raw)
In-Reply-To: <ci4sid$kgu$1@sea.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1669 bytes --]

On Mon, 2004-09-13 21:32:06 +0200, Charlie Gordon <gmane@chqrlie.org>
wrote in message <ci4sid$kgu$1@sea.gmane.org>:
> "Jan-Benedict Glaw" <jbglaw@lug-owl.de> wrote in message
> news:20040910200519.GJ19967@lug-owl.de...
[...]
> > So you basically use creal() and cimag() to access the two numbers.
> 
> Well it is still too vague :
> - what is the floating type of complex variable co ?

Not specified, I guess GCC "assumes" something there. But that doesn't
seem (from my reading) to match with C99 rules.

> - You did not specify float, double or long double, so what is the default ?

Hmmm. You're probably right. I've digget into C99, but to be honest, my
reading is that a simple "complex" (without a real floating type) is
just illegal...

> - Reading tens of pages from C99 leaves that question open (!)

Right. At least from my point of view :-)

> - The creal and cimag macros apply to all 3 complex types.

Well, there has been some type-conversion in between :-)
-----------
7.3.9.2 The cimag functions
Sysnopsis
	#include <complex.h>
	double cimag(double complex z);
	float cimagf(float complex z);
	long double cimagl(long double complex z);
-----------

> PS: I have always hated floating point stuff ;-)

/me too, but sometimes, it helps to achieve more correct numbers :-)

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-09-13 21:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07 15:37 complex variable Huber, George K RDECOM CERDEC STCD SRI
2004-09-07 16:05 ` Jan-Benedict Glaw
2004-09-08  9:59 ` Charlie Gordon
2004-09-08 12:06   ` Jan-Benedict Glaw
2004-09-08 16:25     ` Ankit Jain
2004-09-08 21:54     ` Charlie Gordon
2004-09-10 20:05       ` Jan-Benedict Glaw
2004-09-13 19:32         ` Charlie Gordon
2004-09-13 21:57           ` Jan-Benedict Glaw [this message]
2004-09-14  8:16             ` Charlie Gordon
  -- strict thread matches above, loose matches on Subject: below --
2004-09-08 18:40 Huber, George K RDECOM CERDEC STCD SRI
2004-09-10 20:09 ` Jan-Benedict Glaw
     [not found] <20040906134525.33692.qmail@web52908.mail.yahoo.com>
2004-09-06 16:25 ` Ankit Jain
2004-09-06 16:37   ` Jan-Benedict Glaw

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=20040913215742.GZ19967@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-c-programming@vger.kernel.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 NNTP newsgroup(s).