➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients amaury.forgeotdarc, eric.smith, mark.dickinson, pitrou, rhettinger, stutzbach
Date 2010-10-07.21:12:24
SpamBayes Score 0.08140293
Marked as misclassified No
Message-id <1286485942.3143.3.camel@localhost.localdomain>
In-reply-to <1286485442.93.0.345929097918.issue10044@psf.upfronthosting.co.za>
Content 
> Nope.  It's only well-defined for pointers pointing into the same
> array (or to one past the end of an array).  Otherwise it's undefined
> behaviour.

How can the compiler tell whether two pointers are "into the same
array"? That sounds like an undecidable criterion.
History
Date User Action Args
2010-10-07 21:12:25pitrousetrecipients: + pitrou, rhettinger, amaury.forgeotdarc, mark.dickinson, eric.smith, stutzbach
2010-10-07 21:12:24pitroulinkissue10044 messages
2010-10-07 21:12:24pitroucreate