Re: [algogeeks] Re: EXPLAIN THE OUTPUTS

2011-07-19 Thread rajeev bharshetty
Output on gcc 4.3.x being bfed75a8 3 -1218278705 The First output is the address of the a[0] . Here the function is returning a local address , so the output is compiler dependent . On Tue, Jul 19, 2011 at 8:42 PM, geek forgeek wrote: > @schrodinger y a[] value is not lost in first call.it sh

Re: [algogeeks] Re: EXPLAIN THE OUTPUTS

2011-07-19 Thread geek forgeek
@schrodinger y a[] value is not lost in first call.it should be lost in first call only? On Tue, Jul 19, 2011 at 8:24 PM, schrodinger <6fae1ce6347...@gmail.com>wrote: > First output of memory location is fine. > Second output is also expected one. > Third output will vary compiler to compiler an

[algogeeks] Re: EXPLAIN THE OUTPUTS

2011-07-19 Thread schrodinger
First output of memory location is fine. Second output is also expected one. Third output will vary compiler to compiler and from time to time. This is because a[] is a local to fun(). First time when you call printf("%d\n",r[0]) its fine. but after executing printf() location of r is lost and

[algogeeks] Re: EXPLAIN THE OUTPUTS

2011-07-19 Thread SAMMM
check the O/P :- https://ideone.com/p7pcv Output:- bfc9aae0 (this is always give correct address) 3 // may vary from compiler to compiler (garbage may also come) 3 // may vary from compiler to compiler I think the o/p will depend from compiler to compiler . -- You received this message