From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: complex variable
Date: Mon, 6 Sep 2004 18:37:01 +0200 [thread overview]
Message-ID: <20040906163701.GD6985@lug-owl.de> (raw)
In-Reply-To: <20040906162532.22345.qmail@web52904.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]
On Mon, 2004-09-06 17:25:32 +0100, Ankit Jain <ankitjain1580@yahoo.com>
wrote in message <20040906162532.22345.qmail@web52904.mail.yahoo.com>:
> > 1 #include<stdlib.h>
> > 2 #include<complex.h>
> > 3 #include<stdio.h>
> > 4
> > 5 int main()
> > 6 {
> > 7 FILE *fp;
> > 8 fp=fopen("test_data.dat","rb");
> > 9 int N=32,i=0;
> > 10 complex x,*in;
> > 11 in=malloc(sizeof(complex)*N);
You need to check the "in" pointer -- malloc() may fail!
> > 12 if (fread(in,16,32,fp) != 32)
"16" should read "sizeof (complex)". If you don't do that, you loose any
portability (for no added value). Additionally, both "32" should be "N",
since that's what you really want to read, what you really malloc()ed.
Also (from personal experience), I can only strongly advise you not to
read in (or write out) numbers like that. All the data types may look
different on different CPUs or operating systems, so better stick to an
encoding that's common to all of them.
Define an own encoding for those values (eg. printf() out their real and
imaginary part as decimal floating-point values and translate these back
to "complex" values). It's a real *nightmare*.
> > 13 printf("error in reading from file
> > failed\n");
> > 14 else{
> > 15 for(i=0;i<N;i++)
> > 16 printf("%lf\t",*(in+i+0));
Others would have used that as in[i] ... Easier to read:-)
> > 17 }
> > 18 return 0;
> > 19 }
> >
> > i am sorry but this code also gives the same error
> >
> > error in reading from file failed
Even while your programs "features" a good number of typical no-no's,
it should probably work. Are you sure the file is long enough? Could you
provide a strace from this program being run?
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 --]
next prev parent reply other threads:[~2004-09-06 16:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040906134525.33692.qmail@web52908.mail.yahoo.com>
2004-09-06 16:25 ` complex variable Ankit Jain
2004-09-06 16:37 ` Jan-Benedict Glaw [this message]
2004-09-07 15:37 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
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
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=20040906163701.GD6985@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).