🚀 go-pugleaf

Andreas Osswald wrote:
> I want to know how many files are opened by my application without closing
> it. You are right if you say the programm should know this. But if you
> forgot once to use close() or you returned out of a function before you call
> close() a stream keeps open. Under DOS-OS there was the possibility to use
> flushall() it returned all open streams an it was helpful to find errors
> like described.
> 
> Andreas
> 
> 
> "Andrue Cope [TeamB]" <no.spam@not.a.valid.address> schrieb im Newsbeitrag
> news:42f095b9$1@newsgroups.borland.com...
> 
>>Andreas Osswald wrote:
>>
>>
>>>Hallo, is there any way to get the total amount of open files, opened
>>>by the own application ?
>>
>>What do you mean exactly?
>>
>>If you want to know how many open files your application has at any one
>>time then I'd have to question your overall design and implementation.
>>IMO there should be no reason for you not to know that. A program that
>>doesn't know what state it's in sounds very dubious to me.
>>
>>If you want to know how many files your application has opened in total
>>(ie;how many times has open() been called) then I can think of no
>>standard way to do that. The easiest way would be to have all file I/O
>>open requests go through your own routine that can keep a count. This
>>can only be enforced through programming convention but it's not a bad
>>idea.
>>
>>We always use our own home grown functions (classes in more recent
>>code) because for us having that kind of centralised control over file
>>I/O offers many advantages. Logging all I/O is not something we bother
>>with at the moment but it would certainly be one application.
>>
>>--
>>Andrue Cope [TeamB]
>>[Bicester, Uk]
>>http://info.borland.com/newsgroups/guide.html
> 
> 
> 
Andreas,

	Did you compile your code with CodeGuard? CodeGuard must detect and 
report this kind of errors.

Sabetay