Thread: Memory management - How/why/when

Originally Posted by sloppy

@Salem
I use gcc4 under linux (command line bash... does it depend on command line?)

@gibsosmat
it seems to me that the error doesn't come for built-in funcions even if I do not cast. but maybe it depends on my compiler...


PS:
Using "gcc -S" vs "g++ -S" to get assembly output of a custom malloc(int,int) functions it seems that gcc calls malloc, whereas g++ renames the custom malloc and calls the custom malloc.

am using the same.. so things dont change much..
but its like a habit that few ppl learn how not to before learning how to
I am one of them..

btw I dont like that .s file.. and I didnt do 2 of my assignments which wanted me to comment whats going on in sparc & PC architecture
I found it to be the worst thing to be done and calling it a programming assignment.
still I will learn it latter

Originally Posted by Salem

Doesn't gcc4 default to C99 behaviour, which makes implicit declarations of functions illegal?

I do not know the default. But If I add to the command line "-std=c99" I get one more warning:
prova.c:10: warning: implicit declaration of function 'malloc'

(always both with and without casting)

Originally Posted by Salem

Doesn't gcc4 default to C99 behaviour, which makes implicit declarations of functions illegal?

Not with GCC 4.1.2:

Code:

main(void) {
  return 0;
}

Running "gcc foo.c" gives no warnings. I have to use -Wall to get

foo.c:1: warning: return type defaults to ‘int’

It's not likely that C99 will be the default until the support for it is essentially complete.

http://gcc.gnu.org/c99status.html