有人能给我解释一下为什么有些程序员在malloc前面使用(char*)。我知道它会返回void，但是为什么我要它只返回char内存呢？对不起，我只是个编程新手。谢谢你

不需要强制转换EDOCX1的返回值(0)，因为它的返回类型是void*。

Can someone explain why do some programmers use (*char) in front of the malloc?

他们做错事(最有可能)通过铸造它(在良好的程序员看来)。

正如维基所说：

malloc返回一个空指针(void *)，表示它是指向未知数据类型区域的指针。由于强大的类型系统，在C++中需要使用铸造，而在C＜1＞/Sub中则不是这样。缺少从malloc返回的特定指针类型是一些程序员所说的类型不安全行为：malloc是基于字节计数而不是基于类型分配的。这与C++返回了一个指针，它的类型依赖于操作数的C++ EDCOX1 6Ω操作符不同。可以将此指针"强制转换"到特定类型：

这样的演员表演有其优点和缺点。

• Including the cast allows a program or function to compile as C++.
• The cast allows for pre-1989 versions of malloc that originally returned a char *.
• Casting can help the developer identify inconsistencies in type sizing should the destination pointer type change, particularly if the pointer is declared far from the malloc() call.

铸造的缺点：

• Under the ANSI C standard, the cast is redundant.
• Adding the cast may mask failure to include the header stdlib.h, in which the prototype for malloc is found. In the absence of a prototype for malloc, the standard requires that the C compiler assume malloc returns an int. If there is no cast, a warning is issued when this integer is assigned to the pointer; however, with the cast, this warning is not produced, hiding a bug. On certain architectures and data models (such as LP64 on 64-bit systems, where long and pointers are 64-bit and int is 32-bit), this error can actually result in undefined behavior, as the implicitly declared malloc returns a 32-bit value whereas the actually defined function returns a 64-bit value. Depending on calling conventions and memory layout, this may result in stack smashing. This issue is less likely to go unnoticed in modern compilers, as they uniformly produce warnings that an undeclared function has been used, so a warning will still appear. For example, GCC's default behavior is to show a warning that reads"incompatible implicit declaration of built-in function" regardless of whether the cast is present or not.
• If the type of the pointer is changed, one must fix all code lines where malloc was called and cast (unless it was cast to a typedef).

＞1。重点是我的。