From: "Jon Beniston" <jbeniston@compxs.com>
To: "'Eitan'" <eitangur@bezeqint.net>, <gcc@gcc.gnu.org>,
<gcc-help@gcc.gnu.org>
Subject: RE: need help
Date: Fri, 26 Sep 2003 11:34:00 -0000 [thread overview]
Message-ID: <016301c38421$f07a4d00$06bda8c0@Kindrogan> (raw)
In-Reply-To: <005001c38429$65ac1d90$0956da51@gur>
>
> 2. I get an annoying warning message - "warning: too many
> arguments for format". What does it mean?
Probably that you're doing something like
printf("%s %d\n", name, age, address);
i.e. there are more arguments than there are %'s.
> 3. Good programing parctice - If I have a static global
> variable, that is defined in one file, but not used in it -
> why is it a bad thing (I get a warning)?
Static variables (and functions) are not visible to other files. So if
they're not referenced in the file in which they are defined, then they
may as well not exist.
Cheers,
Jon
next prev parent reply other threads:[~2003-09-26 11:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 11:28 Eitan
2003-09-26 11:34 ` Jon Beniston [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-07 12:23 ASHA GOWDA
2007-06-07 14:53 ` Ian Lance Taylor
2005-03-21 8:54 arul kumaran
2005-02-08 12:19 Vijayalakshmic
2004-10-11 17:50 Need Help Sriharsha Vedurmudi
2004-10-13 7:16 ` Muthukumar Ratty
2003-10-01 5:23 need help cro
2003-10-01 6:10 ` Jeffrey Holle
2003-07-08 16:16 V Robert
2003-07-09 18:42 ` LLeweLLyn Reese
2002-08-19 10:07 Kitti Kittirutsunetorn
2002-08-19 12:02 ` bjorn rohde jensen
2002-08-19 14:56 ` Oscar Fuentes
2002-08-19 15:29 ` bjorn rohde jensen
2001-07-01 22:30 Need help Martin Kalen
2001-07-01 14:42 Jules FOSSO
2001-07-01 22:02 ` Parameshwari B.
2000-05-02 9:31 need help Claudiu BRASOVEAN
2000-05-02 10:00 ` llewelly
1999-11-05 13:05 Need Help Powell, Sandy
1999-11-30 23:28 ` Powell, Sandy
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='016301c38421$f07a4d00$06bda8c0@Kindrogan' \
--to=jbeniston@compxs.com \
--cc=eitangur@bezeqint.net \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).