| If porting is important then it demands attention from the start.
If you don't, then when you need it, you will be stuck in habits and a way of thinking that makes "programming for portability" problematic.
Programming for portability is not as much a matter of "good books".
It is more a matter of knowing your programming language very well.
When you make some code, think like this:
"Did I use stuff that is typical for MS Windows?".
"If so, what can I do to achieve the same, but without the help of typical MS Windows features.".
"If so, how can I minimize problems when I need to re-code later?"
Test:
Is DirectX a typical MS Windows thing?
And Direct3D? And DirectSound? And DirectInput?
How about OpenGL?
How about system(PAUSE) (C++)?
How about <conio.h> ?
And <Windows.h> ?
__________________  |