marcov wrote:The point is that you can't do things like you normally do, and what internet recommends. This complicates things for people mostly working on newer windows. Just like any Windows code after 2000-2005 will probably call -W functions a lot.
Things like that are basically behind the advise to not add to the win32 target, but rather split it in (multiple?) old and new.
good... because you shouldnt simple do what internet recommends without reasoning first... the last thing you want is to code like a genius for no good reason...
Exactly my sentiment. Why do a lot of navigating to keep win32s .. win10 in one target? Just separate them into separate targets, and retro and more forward developers are not constantly at loggerheads and /or calling each other names like "capitalist slave" (or "caveman" :-)
And no, doing manual hacks simply are not an option. Retro options should NOT dictate mainstream Windows devels how to code.
This is also absolutely not anti-retro, it is simply about managing retro within a not-retro-only project, giving it a proper place. FPC nowadays supports 16-bit dos, 32-bit dos, win16, win32, win64, nativent and wince (IOW every MS target but win32s :-)
And even retro non-dos targets like various Amiga targets as well as embedded 8-bitters like Arduino.