Larry Hastings added the comment: > > Yes, that is a different name that seems to mean much the same > > thing. > and which is much more understandable by a Python developer.
Thanks for your opinion. > > Changing error to an char and moving it to the end would > > save exactly zero bytes, because the compiler *will* align > > stack variables to 4 byte boundaries. > > Except if other stack variables happen to be shorter than an int, > perhaps. Do we use a lot of those? > But regardless, it doesn't cost anything to do so, so why not do it? I thought I just got through explaining how it is slightly slower. There is no benefit in changing them to "char", so why do it? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue20341> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
