Thread: What the... nested fpout doesnt work?

Shouldn't it be _fcloseall? and not fcloseall?

You can check the return value of fclose to see if the file was really closed.
I'd add the tracing to see in the log that the actual number of fopen calls is equal to fclose calls...

You can miss some place where fclose is called on some condition, and otherwise the file is left opened...

Originally Posted by vart

Shouldn't it be _fcloseall? and not fcloseall?

Oh my god..... that's it indeed and it works!! Thanks so much!!!

But... what does this mean? Was there still some fopen left unclosed? Or is there another function that occupies a "file-open-slot" ? How about opendir() for example?

Thanks a whole lot anyway Vart... what a relieve to see it working, finally!!

<3 Cboard.

Ren&#233;

Was there still some fopen left unclosed?

Check the return value of _fcloseall

I'm not familiar with opendir function - but looking at the man page I see a closedir function - I suppose they should be called in pairs

Originally Posted by vart

Check the return value of _fcloseall

I'm not familiar with opendir function - but looking at the man page I see a closedir function - I suppose they should be called in pairs

Yeah, I'm using closedir on every readdir already
And thanks for the return value tip, it says it's 1 or 2 everytime so I suppose I'm still overlooking something. I will have a closer look at this.

Thanks again for your time and help!