From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: complex variable
Date: Tue, 7 Sep 2004 18:05:35 +0200 [thread overview]
Message-ID: <20040907160535.GT6985@lug-owl.de> (raw)
In-Reply-To: <E3E30069B061524E90BCEE4417E30661138525@monm207.monmouth.army.mil>
[-- Attachment #1: Type: text/plain, Size: 1404 bytes --]
On Tue, 2004-09-07 11:37:06 -0400, Huber, George K RDECOM CERDEC STCD SRI <George.K.Huber@us.army.mil>
wrote in message <E3E30069B061524E90BCEE4417E30661138525@monm207.monmouth.army.mil>:
> In addition to the previously given suggestions, I would suggest checking
> the return
> value of fopen (it can fail), as well as printing out the error codes. For
> example,
> I would recode the above as (note - this is uncompiled/tested code but is
> should
> give an example of what I mean):
Error checking is always a good idea :-)
> #include<stdlib.h>
> #include<complex.h>
> #include<stdio.h>
> #include<errno.h>
>
> int main()
> {
> FILE* fp=NULL;
No need to initialize *fp to NULL because you assign a value before it's
read for the first time. That'll only bloat the program :)
> char szName[] = "test_data.dat";
>
> if(NULL != (fp = fopen(szName, "rb")))
> {
> int N=32, i=0;
> complex x, *in = NULL;
> if(NULL != (in=malloc(sizeof(complex)*N)))
Same here -- no need to initialize *in.
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-07 16: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 [this message]
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
[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=20040907160535.GT6985@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).