3 ms·

This isn't just for backwards compatibility, OutputDebugString is a crucial function and hasn't been replaced with anything afaik. We use it all the time. Why f

by ptr 5y ago

This isn't just for backwards compatibility, OutputDebugString is a crucial function and hasn't been replaced with anything afaik. We use it all the time. Why fix something that isn't broken I guess?

Stratoscope 5y ago
Indeed, that is the very definition of backward compatibility.
- dmurray 5y ago
  This is closer to forward compatibility: your program written for Windows 10 will work as expected on Windows 1.0! Well, at least the OutputDebugString parts.
- megablast 5y ago
  No. It’s not. If it was superseded, and still kept in, that’s backward compatible.