The default libstdc++ operator new and delete use the libc malloc and free.
所在版块：求学狮城 发贴时间：2005-10-30 15:48

用户信息
复制本帖HTML代码
高亮: 今天贴 X 昨天贴 X 前天贴 X 
since it boils down to function call, i guess g++ is not supposed to do such checking.
.
欢迎来到华新中文网，踊跃发帖是支持我们的最好方法!

　相关帖子 我要回复↙ ↗回到正文
why does not "g++ -Wall" give warning message when compiling the following code? － icky 　2005-10-30 00:44 (660 bytes , 932reads )
delete array; not delete [] array; － simon 　2005-10-30 11:15 (470 bytes , 648reads )
do u mean － icky 　2005-10-30 15:44 (132 bytes , 387reads )
no la...as simon said, object vs primitive data type － sarah 　2005-10-30 20:03 (0 bytes , 390reads )
。。。。。。ok... － simon 　2005-10-31 01:04 (0 bytes , 289reads )
different btw 'object' and 'primitive data type' － simon 　2005-10-30 11:16 (0 bytes , 343reads )
using linux/glibc? Segfault because you damaged the link list － hash 　2005-10-30 06:28 (1304 bytes , 650reads )
a mistake － hash 　2005-10-30 15:21 (233 bytes , 411reads )
but after － icky 　2005-10-30 10:20 (103 bytes , 386reads )
The default libstdc++ operator new and delete use the libc malloc and free. － hash 　2005-10-30 15:48 (86 bytes , 464reads )