mirabilos added the comment: Right, keeping it simple helps in preventing accidents, and the code block looks full of magic enough as-is.
Maybe add a comment block that says: /* * m68k is a bit different from most architectures in that objects * do not use "natural alignment" - for example, int and long are * only aligned at 2-byte boundaries. Tests have shown that skipping * the "optimised version" will even speed up m68k, so we #ifdef * for "the odd duck out" here. */ Then we have an in-situ documentation point for why that ifdef is there and why m68k is “the odd duck” and this whitelist method is used. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17237> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
