| |||||||||||||
Choosing between portability and innovationChoosing between portability and innovationPosted Mar 9, 2011 17:50 UTC (Wed) by schabi (subscriber, #14079)In reply to: Choosing between portability and innovation by dlang Parent article: Choosing between portability and innovation
I agree here.
But note that there is a huge difference between writing "non-portable" code targeted for an idealized platform (with a PAL in place to emulate that platform in the real environment), and writing with portability in mind (hundreds of #ifdefs, missing functionality, etc.).
(Log in to post comments)
Choosing between portability and innovation Posted Mar 9, 2011 23:44 UTC (Wed) by nix (subscriber, #2304) [Link]
Writing with portability in mind does not imply 'missing functionality' (on platforms capable of it), and *certainly* does not imply 'hundreds of #ifdefs'. Indeed, the latter is generally a symptom of software that was not written with portability in mind, but which had limited portability jammed crudely into it at a later date.
|
|||||||||||||