Re: dirname return value
- From: gordonb.7b9b4@xxxxxxxxxxx (Gordon Burditt)
- Date: Tue, 04 Jul 2006 05:43:51 -0000
Or to put it another way, since it says it MAY use static storage, and
there's no way to find out whether it did or didn't, for safety you have
to assume it's static and not freeable.
Tell me something new :-(
If I call it in a loop, how do I know it's not a memory leak? This
There is no system-supplied function that you can call that is guaranteed
not to leak memory. I'm not really sure that the integer + operator
is prohibited from leaking memory:
while(1) 2+2;
seems to be one of the "untouchable" APIs of POSIX. :-(
Gordon L. Burditt
.
- References:
- dirname return value
- From: Ian Zimmerman
- Re: dirname return value
- From: spibou@xxxxxxxxx
- Re: dirname return value
- From: Barry Margolin
- Re: dirname return value
- From: nobrowser
- dirname return value
- Prev by Date: Re: pls help in solving two problems
- Next by Date: Re: Finding common lines between text files
- Previous by thread: Re: dirname return value
- Next by thread: Re: dirname return value
- Index(es):
Relevant Pages
|
