rsnd

Ok this is one of those stupid questions but #include <memory> or #include <memory.h> in c++?

I try to compile with memory in dev c++ and it complains and then when I try in vc++ 2008 it complains about undefined functions with memory.h

__________________
Spread your wings and fly! Chicken!

grumpy

Neither. There is no standard header named <memory.h> specified in either the C or C++ standards. The C++ standard also specifies no standard header named <memory> or <cmemory>.

If you are trying to access functions like memset(), the relevant C header is <string.h> (which is deprecated in C++ and replaced by <cstring> which has the functions living in namespace std).

rsnd

i c
thanks
what about functions like malloc/free/realloc?

__________________
Spread your wings and fly! Chicken!

grumpy

malloc(), calloc(), realloc(), and free() are declared within <stdlib.h> (C, deprecated in C++) and <cstdlib> (C++, also in namespace std).

Surely, your compiler documentation would have had some mention of those functions.

Ancient Dragon

Maybe yes, and maybe no. For example, MSDN still documents use of the .h extension, such as studio.h. For malloc() and associated functions MSDN doesn't distinguish the difference between C and C++ header files.

__________________
True Terror is to wake up one morning and discover that your high school class is running the country - Kurt Vonnegut Jr.

Jabo

In C++, malloc has been replaced with new hasn't it?

Seif

No. Malloc and new are different, and both have their place in C++, there are a number of differnces between the two.

new is an operator, that constructs an object and is type safe.

malloc is a function, malloc just allocates memory, it doesn't call the objects constructer, and returns a void pointer to the memory which is required to be explicitly cast.

Jabo

Just goes to show don't believe everything you hear...

grumpy

Allocating raw memory (which is all malloc() does) is one of the steps in dynamically creating an object (or multiple objects) with operator new. That step occurs before constructor(s) are invoked when dynamically creating object(s) with operator new.

The return value from malloc() does not require explicit casting (or conversion) in C, although it does in C++.

__________________
Dear God
So far today I've done all right. I haven't been grumpy yet. But in a few minutes, God, I'm going to get out of bed, and from then on I'm going to need a lot more help.
AMEN

Narue

>The C++ standard also specifies no standard header named <memory> or <cmemory>.
You might want to double check that. A header called <memory> does indeed exist. It's where you find such useful creatures as auto_ptr and allocator.

__________________
Even if the voices aren't real, they have some pretty good ideas.