Re: _wstat on Windows (actually stat stuff in general)

Switching _wstat to _stat will only make the problem worse.
How can returning an error (which the application can trap, and possibly take remedial action of its own - for example trying _wstat itself), *EVER* be worse than a function silently succeeding with a bogus return value?

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]