its /n/sources/patch/testolder, also leaks dir in the case:
if(rel)
n = time(0) - n;
if(n 0)
return 0; - HERE
r = dir-mtime n;
free(dir);
return r;
And the consequences of not freeing a few bytes of memory, in a command
which
On Jun 3, 2013 6:49 AM, Richard Miller 9f...@hamnavoe.com wrote:
And the consequences of not freeing a few bytes of memory, in a command
which will exit a few microseconds later, would be ... ?
bad taste.
bad taste.
I agree - better style is to free memory always, or never. But the
choice might not be as obvious as one first thinks.
Richard Miller 9f...@hamnavoe.com wrote:
And the consequences of not freeing a few bytes of memory, in a command
which will exit a few microseconds later, would be ... ?
The Code Correctness Police come and collect you and force you to
program on Windows... ducks
:-)
Arnold
On Mon Jun 3 08:00:20 EDT 2013, arn...@skeeve.com wrote:
Richard Miller 9f...@hamnavoe.com wrote:
And the consequences of not freeing a few bytes of memory, in a command
which will exit a few microseconds later, would be ... ?
The Code Correctness Police come and collect you and force
its /n/sources/patch/testolder, also leaks dir in the case:
if(rel)
n = time(0) - n;
if(n 0)
return 0; - HERE
r = dir-mtime n;
free(dir);
return r;
--
cinap
On Sun Jun 2 17:31:05 EDT 2013, cinap_len...@gmx.de wrote:
its /n/sources/patch/testolder, also leaks dir in the case:
if(rel)
n = time(0) - n;
if(n 0)
return 0; - HERE
r = dir-mtime n;
free(dir);
return r;
thanks. i
yup. i think it's a bug:
/n/sources/patch/older
/n/atom/patch/older
- erik
