Message 118138 - Python tracker

➜

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	eric.smith
Recipients	amaury.forgeotdarc, eric.smith, mark.dickinson, pitrou, rhettinger, stutzbach
Date	2010-10-07.21:18:55
SpamBayes Score	0.01671617
Marked as misclassified	No
Message-id	<1286486337.22.0.410841281198.issue10044@psf.upfronthosting.co.za>
In-reply-to

Content
In the bad old days of 386 segment:offset memory architectures this was a problem. You could have overlapping segments but pointers inside an object were always in the same segment, so the segment selectors never had to be inspected. Pointers to different objects could indeed have the same offset and would compare equal. We should follow the standard here: no comparisons between pointers to different arrays (basically).

In the bad old days of 386 segment:offset memory architectures this was a problem. You could have overlapping segments but pointers inside an object were always in the same segment, so the segment selectors never had to be inspected. Pointers to different objects could indeed have the same offset and would compare equal.

We should follow the standard here: no comparisons between pointers to different arrays (basically).

History
Date	User	Action	Args
2010-10-07 21:18:57	eric.smith	set	recipients: + eric.smith, rhettinger, amaury.forgeotdarc, mark.dickinson, pitrou, stutzbach
2010-10-07 21:18:57	eric.smith	set	messageid: <1286486337.22.0.410841281198.issue10044@psf.upfronthosting.co.za>
2010-10-07 21:18:56	eric.smith	link	issue10044 messages
2010-10-07 21:18:55	eric.smith	create