Message93662
| Author |
amaury.forgeotdarc |
| Recipients |
Rhamphoryncus, amaury.forgeotdarc, bupjae, ezio.melotti, lemburg, vstinner |
| Date |
2009年10月06日.21:27:44 |
| SpamBayes Score |
1.0698612e-09 |
| Marked as misclassified |
No |
| Message-id |
<1254864468.25.0.484365983959.issue5127@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> that would cause lots of compiler
> warnings and implicit truncation on UCS2 builds
Unfortunately, there is no such warning, or the initial problem we are trying
to solve would have been spotted by such a warning (unicode_repr() calls
Py_UNICODE_ISPRINTABLE() with a Py_UCS4 argument).
gcc has a -Wconversion flag, (which I tried today on python) but it is far too
verbose before version 4.3, and this newer version still has some false
positives. http://gcc.gnu.org/wiki/NewWconversion
But the most important thing is that implicit truncation on UCS2 builds is what
happens already! The patch does not solve it, but at least it yields sensible
results to wary code.
Or can you imagine some (somewhat working) code which behavior will be worse
after the change? |
|