On 07/21/11 01:01 PM, Jian-Xin Lai wrote: > The major reason I prefer the first one is: > If we define Is_Target_XXX for all platforms, we'll lose some ability > to detect potential problems caused by target-specific changes. The > build-time problem is converted into compile-time, run-time or > run-time performance problem. The people who maintain the code and fix the problems and qa will still have to do that regardless.
If all target specific code is abstracted then it will be stable unless explicitly touched. (This is of course ideal and won't happen immediately) Further if the people who work on x86 don't break MIPS/IA64/foo then it reduces risk and makes maintaining everything easier, no? ------- You're essentially trying to argue that inline #if scattered all over the code are better design than abstracted interfaces which expose target specific behavior. (This is just absurd and ridiculous unless the interface is *that* badly designed.) ------------------------------------------------------------------------------ 5 Ways to Improve & Secure Unified Communications Unified Communications promises greater efficiencies for business. UC can improve internal communications as well as offer faster, more efficient ways to interact with customers and streamline customer service. Learn more! http://www.accelacomm.com/jaw/sfnl/114/51426253/ _______________________________________________ Open64-devel mailing list Open64-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open64-devel
