This isn't just for backwards compatibility, OutputDebugString is a crucial func... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		ptr on June 8, 2021 \| parent \| context \| favorite \| on: It is 2018 and this error message is a mistake fro... 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 on June 8, 2021 [–]

Indeed, that is the very definition of backward compatibility.

dmurray on June 8, 2021 | | [–]

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 on June 8, 2021 | | [–]

No. It’s not. If it was superseded, and still kept in, that’s backward compatible.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact