public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ankit Jain" <ankitjain1580@yahoo.com>
To: Sriharsha Vedurmudi <sriharsha.v@redpinesignals.com>
Cc: gcc <gcc-help@gcc.gnu.org>
Subject: Re: complex variable
Date: Mon, 06 Sep 2004 13:45:00 -0000	[thread overview]
Message-ID: <20040906134525.33692.qmail@web52908.mail.yahoo.com> (raw)
In-Reply-To: <413C5C4D.9070107@redpinesignals.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);
     12         if (fread(in,16,32,fp) != 32)
     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));
     17         }
     18         return 0;
     19 }

i am sorry but this code also gives the same error

error in reading from file failed

ankit
 --- Sriharsha Vedurmudi
<sriharsha.v@redpinesignals.com> wrote: 

---------------------------------
    Ankit Jain wrote:  
      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);     12         if
(fread(in,16,32*16,fp) != 32)     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));     17         }    
18         return 0;     19 }it gives error"error in
reading the file"  

Which in the above errors (in Bold) is displayed.
Because, both of themare different. And I dont see any
means by which it would print theerror you specified.

Coming to fread, the third arguement should be 32 in
case you aretrying to read 32 items each of size 16
bytes and then the return valuewill be 32 in case it
actually reads 32 such items. In the abovestatement,
you have asked fread like this:

Read 32 * 16 elements (total of 512 elements) each 16
bytes long from'fp' and store tehm at 'in'. If you
dont read 32 such elements, printerror message. 

Can you see the ambiguity here (ask it to read 512
elements and compareif it reads 32).....

-Harsha
 

________________________________________________________________________
Yahoo! Messenger - Communicate instantly..."Ping" 
your friends today! Download Messenger Now 
http://uk.messenger.yahoo.com/download/index.html

       reply	other threads:[~2004-09-06 13:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <413C5C4D.9070107@redpinesignals.com>
2004-09-06 13:45 ` Ankit Jain [this message]
2004-09-06 14:09   ` Patrick Percot
     [not found] <20040906.143802.63132483.ppercot@free.fr>
2004-09-06 12:48 ` Ankit Jain
2004-09-06 13:12   ` Claudio Bley
2004-09-06 12:22 Ankit Jain
2004-09-06 13:32 ` Ankit Jain

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=20040906134525.33692.qmail@web52908.mail.yahoo.com \
    --to=ankitjain1580@yahoo.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=sriharsha.v@redpinesignals.com \
    /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).