From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: 'linux-c-programming' <linux-c-programming@vger.kernel.org>
Subject: Re: const char * vs char[]
Date: Tue, 23 Mar 2004 18:04:46 +0100 [thread overview]
Message-ID: <20040323170446.GB11933@lug-owl.de> (raw)
In-Reply-To: <000f01c410e6$6d7197e0$0c81640a@aca.org.ar>
[-- Attachment #1: Type: text/plain, Size: 1035 bytes --]
On Tue, 2004-03-23 11:52:12 -0300, Mariano Moreyra <moremari@aca.org.ar>
wrote in message <000f01c410e6$6d7197e0$0c81640a@aca.org.ar>:
> No... "char*" and "char []" are synonyms.
There's a subtle difference:
char *hello_ptr = "A really loooong hello world";
char write_string[] = "this is some long garbage";
void main(void) {
/* legal */
sprintf (write_string, "%s", "stuff");
/* illegal - may be in a read-only segment */
sprintf (hello_ptr, "%s", "Don't do that");
}
So if you're preparing some space for say building up some packet (to be
sent out to hardware), use "char xx[]", but if you only want to have a
read-only string (to printf() it to the user), you can use "char *xx".
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
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-03-23 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 12:01 const char * vs char[] Massimiliano Cialdi
2004-03-23 12:19 ` Glynn Clements
2004-03-23 13:44 ` Mariano Moreyra
2004-03-23 14:19 ` Massimiliano Cialdi
2004-03-23 14:52 ` Mariano Moreyra
2004-03-23 17:04 ` Jan-Benedict Glaw [this message]
2004-03-23 20:26 ` Glynn Clements
2004-03-23 20:37 ` Glynn Clements
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=20040323170446.GB11933@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).