简短的回答是:如果没有真正好的理由，不要在c++中使用malloc。malloc在与c++一起使用时有许多缺陷，而new定义是为了克服这些缺陷。

c++代码中新修正的缺陷

malloc is not typesafe in any meaningful way. In C++ you are required to cast the return from void*. This potentially introduces a lot of problems: #include <stdlib.h> struct foo { double d[5]; }; int main() { foo *f1 = malloc(1); // error, no cast foo *f2 = static_cast<foo*>(malloc(sizeof(foo))); foo *f3 = static_cast<foo*>(malloc(1)); // No error, bad } It's worse than that though. If the type in question is POD (plain old data) then you can semi-sensibly use malloc to allocate memory for it, as f2 does in the first example. It's not so obvious though if a type is POD. The fact that it's possible for a given type to change from POD to non-POD with no resulting compiler error and potentially very hard to debug problems is a significant factor. For example if someone (possibly another programmer, during maintenance, much later on were to make a change that caused foo to no longer be POD then no obvious error would appear at compile time as you'd hope, e.g.: struct foo { double d[5]; virtual ~foo() { } }; would make the malloc of f2 also become bad, without any obvious diagnostics. The example here is trivial, but it's possible to accidentally introduce non-PODness much further away (e.g. in a base class, by adding a non-POD member). If you have C++11/boost you can use is_pod to check that this assumption is correct and produce an error if it's not: #include <type_traits> #include <stdlib.h> foo *safe_foo_malloc() { static_assert(std::is_pod<foo>::value, "foo must be POD"); return static_cast<foo*>(malloc(sizeof(foo))); } Although boost is unable to determine if a type is POD without C++11 or some other compiler extensions. malloc returns NULL if allocation fails. new will throw std::bad_alloc. The behaviour of later using a NULL pointer is undefined. An exception has clean semantics when it is thrown and it is thrown from the source of the error. Wrapping malloc with an appropriate test at every call seems tedious and error prone. (You only have to forget once to undo all that good work). An exception can be allowed to propagate to a level where a caller is able to sensibly process it, where as NULL is much harder to pass back meaningfully. We could extend our safe_foo_malloc function to throw an exception or exit the program or call some handler: #include <type_traits> #include <stdlib.h> void my_malloc_failed_handler(); foo *safe_foo_malloc() { static_assert(std::is_pod<foo>::value, "foo must be POD"); foo *mem = static_cast<foo*>(malloc(sizeof(foo))); if (!mem) { my_malloc_failed_handler(); // or throw ... } return mem; } Fundamentally malloc is a C feature and new is a C++ feature. As a result malloc does not play nicely with constructors, it only looks at allocating a chunk of bytes. We could extend our safe_foo_malloc further to use placement new: #include <stdlib.h> #include <new> void my_malloc_failed_handler(); foo *safe_foo_malloc() { void *mem = malloc(sizeof(foo)); if (!mem) { my_malloc_failed_handler(); // or throw ... } return new (mem)foo(); } Our safe_foo_malloc function isn't very generic - ideally we'd want something that can handle any type, not just foo. We can achieve this with templates and variadic templates for non-default constructors: #include <functional> #include <new> #include <stdlib.h> void my_malloc_failed_handler(); template <typename T> struct alloc { template <typename ...Args> static T *safe_malloc(Args&&... args) { void *mem = malloc(sizeof(T)); if (!mem) { my_malloc_failed_handler(); // or throw ... } return new (mem)T(std::forward(args)...); } }; Now though in fixing all the issues we identified so far we've practically reinvented the default new operator. If you're going to use malloc and placement new then you might as well just use new to begin with!

malloc和new有一个很大的区别。Malloc分配内存。这对于C语言来说很好，因为在C语言中，一块内存就是一个对象。

在c++中，如果你不处理POD类型(类似于C类型)，你必须在内存位置上调用构造函数来实际拥有一个对象。非pod类型在c++中非常常见，因为许多c++特性使对象自动变为非pod类型。

New分配内存并在该内存位置上创建一个对象。对于非pod类型，这意味着调用构造函数。

如果你这样做:

non_pod_type* p = (non_pod_type*) malloc(sizeof *p);

您获得的指针不能被解引用，因为它不指向对象。在使用它之前，您需要调用它的构造函数(这是使用placement new完成的)。

另一方面，如果你有:

non_pod_type* p = new non_pod_type();

你得到一个总是有效的指针，因为new创建了一个对象。

即使是POD类型，两者之间也有显著差异:

pod_type* p = (pod_type*) malloc(sizeof *p);
std::cout << p->foo;

这段代码将打印一个未指定的值，因为由malloc创建的POD对象没有初始化。

使用new，可以指定要调用的构造函数，从而获得定义良好的值。

pod_type* p = new pod_type();
std::cout << p->foo; // prints 0

如果你真的想要它，你可以使用use new来获得未初始化的POD对象。有关更多信息，请参阅另一个答案。

另一个区别是失败时的行为。当它分配内存失败时，malloc返回一个空指针，而new则抛出异常。

前者要求您在使用它之前测试返回的每个指针，而后者将始终产生有效的指针。

基于这些原因，在c++代码中应该使用new，而不是malloc。但即便如此，你也不应该“公开”使用新的内容，因为它会占用你以后需要发布的资源。当你使用new时，你应该立即将它的结果传递给一个资源管理类:

std::unique_ptr<T> p = std::unique_ptr<T>(new T()); // this won't leak

有几件事是new做的，malloc没有:

New通过调用该对象的构造函数来构造该对象 New不需要对已分配的内存进行类型转换。 它不需要分配大量的内存，而是需要大量的内存 要构造的对象。

因此，如果使用malloc，则需要显式地执行上述操作，这并不总是实际的。此外，new可以重载，但malloc不能。

如果你正在使用c++，尝试使用new/delete而不是malloc/calloc，因为它们是操作符。对于malloc/calloc，需要包含另一个头文件。不要在同一代码中混合使用两种不同的语言。它们的工作在各个方面都是相似的，都是从哈希表的堆段动态分配内存。

来自c++ FQA Lite:

[16.4] Why should I use new instead of trustworthy old malloc()? FAQ: new/delete call the constructor/destructor; new is type safe, malloc is not; new can be overridden by a class. FQA: The virtues of new mentioned by the FAQ are not virtues, because constructors, destructors, and operator overloading are garbage (see what happens when you have no garbage collection?), and the type safety issue is really tiny here (normally you have to cast the void* returned by malloc to the right pointer type to assign it to a typed pointer variable, which may be annoying, but far from "unsafe"). Oh, and using trustworthy old malloc makes it possible to use the equally trustworthy & old realloc. Too bad we don't have a shiny new operator renew or something. Still, new is not bad enough to justify a deviation from the common style used throughout a language, even when the language is C++. In particular, classes with non-trivial constructors will misbehave in fatal ways if you simply malloc the objects. So why not use new throughout the code? People rarely overload operator new, so it probably won't get in your way too much. And if they do overload new, you can always ask them to stop.

对不起，我就是忍不住。：）

除非被迫使用C，否则永远不要使用malloc。总是使用new。

如果你需要大量的数据，可以这样做:

char *pBuffer = new char[1024];

尽管这是不正确的，但要小心:

//This is incorrect - may delete only one element, may corrupt the heap, or worse...
delete pBuffer;

相反，你应该在删除数据数组时这样做:

//This deletes all items in the array
delete[] pBuffer;

new关键字是c++实现它的方式，它将确保你的类型的构造函数被调用。new关键字也更加类型安全，而malloc根本不是类型安全的。

我认为使用malloc有益的唯一方式是需要改变数据缓冲区的大小。new关键字没有类似realloc的方式。realloc函数可能能够更有效地扩展内存块的大小。

值得一提的是，你不能将new/free和malloc/delete混合使用。

注:本题部分答案无效。

int* p_scalar = new int(5);  // Does not create 5 elements, but initializes to 5
int* p_array  = new int[5];  // Creates 5 elements