From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: Assignment make pointers
Date: Mon, 13 Dec 2004 11:10:11 +0100 [thread overview]
Message-ID: <20041213101011.GO16958@lug-owl.de> (raw)
In-Reply-To: <20041213_100432_025782.r_zaca@ig.com.br>
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
On Mon, 2004-12-13 08:04:32 -0200, r_zaca <r_zaca@ig.com.br>
wrote in message <20041213_100432_025782.r_zaca@ig.com.br>:
Content-Description: Mail message body
> If you take a look in "man 3 basename", you'll see that basename function
> just returns a pointer to a char. In the case above you need to "cast" the
> pointer returned to be of type int.
> Like: prog_ptr = (int *) basename (argv[0]);
Don't do that. Usually, you can write even quite large programs without
using casts at all. Most of the time, a cast points to spots in your
programs that are badly designed from the type of your variables point
of view. If your variables are of senseful types and obey a well-thought
structure (like using enums and unions instead of #defines and casts),
you usually don't need to cast.
Also, I usually suggest to compile code with "-Wall" -- that'll show you
probably lots of odd constructs that should be written differently (or
using proper types).
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-12-13 10:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 10:04 Assignment make pointers r_zaca
2004-12-13 10:10 ` Jan-Benedict Glaw [this message]
2004-12-13 14:51 ` Eric Bambach
2004-12-13 14:58 ` Eric Bambach
2004-12-13 15:01 ` C Newbie Darren Sessions
2004-12-13 15:50 ` Jan-Benedict Glaw
2004-12-13 16:03 ` Eric Bambach
2004-12-29 2:13 ` Defunct Processes Darren Sessions
2004-12-29 10:16 ` Jan-Benedict Glaw
2004-12-30 13:14 ` Daniel Souza
2004-12-13 15:47 ` Assignment make pointers 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=20041213101011.GO16958@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.