Thomas Frieden wrote:
... But again, deprecated functions are deprecated for a reason, and ignoring the warning messages might result in
your program misbehaving in later versions of the OS.
I consider that using deprecated functions intensionally, simply defines your software as pre-broken in some way,
it therefore won' t be able to adapt to changes required to bring the operating system forward or extend functionality.
There is always a reason why a function is deprecated, whether it be simply because it couldn't host new features because
the old API design ruined any chance of extensibility, or whether the API used parameters or structures that were limited
to 32 bit quantities, or whether said structures had limited sized buffers that couldn't handle full sized string lengths,
or some other reasons.
In any way, the use of these functions PREVENTS software from being able to handle situations where someone may
pass a name that happens to be longer than will fit, or a file may be sized larger than can be returned in 32 bits.
Your software is already broken if these kind of limitations are enforced, it's just a matter of time before someone creates
a filename longer that 107 bytes or stores a 5gig movie file on the disk, before your software will break in unknown ways.