Will this code leaks memory

[LinuxGuy]

Can someone please tell if following code leaks memory

void someFunction()
{

char MyArray[512];

memset(MyArray, 0,512);

}

[Dervish]

No - it can't leak. However it is better to write
memset(MyArray, 0,sizeof(MyArra y));
to avoid duplicating of magic number (512).

[Alf P. Steinbach]

* Dervish:

[non-quoting]
Please read the FAQ and the monthly welcome message.

Please quote what you're replying to.

This isn't a web forum or instant messaging.

No - it can't leak. However it is better to write
memset(MyArray, 0,sizeof(MyArra y));
to avoid duplicating of magic number (512).

memset is not type safe and thus should be avoided where practically
possible.

In this case, if a raw array is really needed (it seldom is), write

void someFunction()
{
char MyArray[512] = {};
}
--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?

[LinuxGuy]

even if I don't use memset() and just declare the array then will it be
deallocated when function exits..

[mlimber]

LinuxGuy wrote:

even if I don't use memset() and just declare the array then will it be
deallocated when function exits..

First, to reiterate: please QUOTE what you are replying to. Not
everyone is using Google Groups, and it helps all to follow the
conversation. (To quote automatically from GG, click "show options" and
then "reply" in the revealed header.)

Second, you seem to have either asked a question but omitted to proper
punctuation or inappropriately phrased an indicative sentence as an
interrogative. In either case, the answer is that, yes, automatic
variables and arrays are freed when they leave scope.

Cheers! --M

[Christopher Benson-Manica]

LinuxGuy <ra**********@g mail.com> wrote:

even if I don't use memset() and just declare the array then will it be
deallocated when function exits..

Your failure to post properly has already been duly noted.

In answer to your actual question, yes, your array will be deallocated
when the function exits, no matter what you do to it. If your
implementation uses a stack (it probably does), it may help to know
that space allocated on the stack is *always* freed when the function
returns. Such is the beauty of "automatic" (whatever C++ calls it)
storage.

--
Christopher Benson-Manica | I *should* know what I'm talking about - if I
ataru(at)cybers pace.org | don't, I need to know. Flames welcome.