All of lore.kernel.org
 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: Fri, 10 Sep 2004 22:05:19 +0200	[thread overview]
Message-ID: <20040910200519.GJ19967@lug-owl.de> (raw)
In-Reply-To: <chnv2v$j6n$1@sea.gmane.org>

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

On Wed, 2004-09-08 23:54:45 +0200, Charlie Gordon <gmane@chqrlie.org>
wrote in message <chnv2v$j6n$1@sea.gmane.org>:
> "Jan-Benedict Glaw" <jbglaw@lug-owl.de> wrote in message
> news:20040908120658.GZ6985@lug-owl.de...
> 
> > > >                 for(i=0; i< N; i++)
> > > >                     printf("%lf\t", in[i]);

> it's ugly because the whole complex number in whatever storage format it's
> in gets passed to printf.

Right.

> In my understanding, this may fail because there is no guaranty about which
> part of the structure will be printed and the format specifier may be
> incorrect for the actual type thus passed.

Right, too. Here's how it ought to work:

-----------------------------------------------------------
#include <complex.h>
#include <stdio.h>
#include <stdlib.h>

int
main (int argc, char *argv[])
{
	complex co;

	co = 1.3 + I * 2.9;
	printf ("%lf %lf\n", creal (co), cimag (co));

	return EXIT_SUCCESS;
}
-----------------------------------------------------------

So you basically use creal() and cimag() to access the two 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-10 20:05 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 [this message]
2004-09-13 19:32         ` Charlie Gordon
2004-09-13 21:57           ` Jan-Benedict Glaw
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=20040910200519.GJ19967@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.