do I have to free() a const char * ?

Question

1.00/5 (1 vote)

See more:

Hi, I'm just wondering if I have to call free() on a const char * pointer or string (idk which one it is). The reason why I'm wondering this is because of the *, which would seem to imply that it's a pointer. This is how I do it:

const char * filenames[2] = {"file1.png", "file2.png"};

Thanks in advance for any and all replies! -B

Posted 26-Feb-11 5:36am

bala_48225

Add a Solution

3 solutions

Solution 2

Free the filenames[2]!

Please feel free to to ignore this posting. :-O

Posted 26-Feb-11 5:41am

Henry Minute

Comments

CPallini 26-Feb-11 12:52pm

free(Henry); :-D

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Espen Harlinn · Accepted Answer · 2011-02-26T05:41:00

Solution 1

No, not in this case as the memory was not dynamically allocated using malloc and friends :)

Freeing it would be an error ...

Regards
Espen Harlinn

Posted 26-Feb-11 5:41am

Espen Harlinn

Comments

Henry Minute 26-Feb-11 11:51am

I'm glad someone gave correct information.
I can leave my, possibly, ill advised attempt at humour now.

My 5

Espen Harlinn 26-Feb-11 12:17pm

Thanks Henry!

Sergey Alexandrovich Kryukov 26-Feb-11 11:55am

Correct, my 5. The answer should be more simple I thing; see mine.
--SA

Espen Harlinn 26-Feb-11 12:18pm

Thanks SAKryukov!

fjdiewornncalwe 26-Feb-11 11:58am

Absolutely correct. +5. I've encountered many a developer who has caused themselves issues with this.

Espen Harlinn 26-Feb-11 12:18pm

Thanks Marcus!

bala_48225 26-Feb-11 12:24pm

Well thanks everyone; I think Henry Minute should delete his funny post on the off-chance that someone who is a cross between a tard and a noob doesn't read the second line, that could cause your ratings to go down, lol! As for SAKryukov, I don't do new pointers yet, but thanx anyway!

Sergey Alexandrovich Kryukov · Accepted Answer · 2011-02-26T05:54:00

Solution 3

No new — no delete. In the same way, no malloc (or calloc or realloc) — no free. Isn't that simple?

—SA

P.S.: Thanks again, CPallini

Posted 26-Feb-11 5:54am

Sergey Alexandrovich Kryukov

Updated 26-Feb-11 6:44am

v3

Comments

CPallini 26-Feb-11 12:11pm

Good, my 5. However it should be "no malloc (or calloc or realloc) -> no free".

Sergey Alexandrovich Kryukov 26-Feb-11 12:41pm

Oh, my bad; I messed up -- will fix it.
Thanks a lot.
--SA

Espen Harlinn 26-Feb-11 12:51pm

Well, yes - my 5

Sergey Alexandrovich Kryukov 26-Feb-11 14:36pm

Thank you, credit to CPallini.
--SA