Difference between explicitly using Unicode/ANSI Windows APIs and letting them be handled by aliases?
<p>What's the difference between me explicitly defining every Win32 API I use in my project as W (Wide) or A (ANSI) and letting it be decided by the solution/project configuration? Apart by being able to change it on the fly, that is.</p>

<p>Say I only need Unicode at the moment for some reason, would it be better of me to just let them expand to the correct one automatically or explicitly define them?
Would it break some systems on release if I only develop for ANSI or Unicode versus supporting both?</p>