rbowman
Mon, 30 Jan 2017 02:10:23 GMT in alt.home.repair, wrote:

On 01/29/2017 02:19 PM, Diesel wrote:
Sadly, for the most part, that's the authors personal lazy
choice. Aside from a few API calls which are new/altered, there's
no real reason to deliberately force your binary not to run under
Windows XP.


If you use new API call, the app isn't going to run.

Possibly. It may not run at all, depending on when you call that api.
Or, it might run upto the point where you reach out to that api.


No reason to
force anything. It's no different than if I add a new call to one
of our dll's. Older software that doesn't depend on the new call
still works. New software linked against the new lib won't run
with the old dll.

Of course. It's been that way for decades. Prior to DLL.

It's not a lazy choice. The world moves on. We're not going to use
multiple source branches, builds, documents, and test protocols to
support those living in the past.

See my other post for more on this.


--
Sarcasm, because beating the living **** out of deserving people is
illegal.