Message208885
| Author |
larry |
| Recipients |
Yury.Selivanov, brett.cannon, georg.brandl, jkloth, larry, pitrou, serhiy.storchaka, taleinat, vajrasky, zach.ware |
| Date |
2014年01月23日.08:29:44 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1390465785.83.0.938930089859.issue20341@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> > 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? |
|