Message208852
| Author |
pitrou |
| Recipients |
Yury.Selivanov, brett.cannon, georg.brandl, jkloth, larry, pitrou, serhiy.storchaka, taleinat, vajrasky, zach.ware |
| Date |
2014年01月22日.21:19:31 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1390425567.2306.7.camel@fsol> |
| In-reply-to |
<1390424715.11.0.790443777608.issue20341@psf.upfronthosting.co.za> |
| Content |
> > int(or_none=True) ?
>
> Yes, that is a different name that seems to mean much the same thing.
and which is much more understandable by a Python developer.
> 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. But regardless, it doesn't cost anything to do so, so why not
do it? |
|