Message 230054 - 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	eryksun
Recipients	amaury.forgeotdarc, belopolsky, eryksun, meador.inge, pitrou, steve.dower
Date	2014-10-27.01:35:41
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1414373742.25.0.281779499665.issue22732@psf.upfronthosting.co.za>
In-reply-to

Content
> Why not use c_size_t? Or is that incorrect in some cases? Strictly speaking, size_t doesn't have to encompass the entire addressable range, such as for architectures that use segmented addressing (e.g. near and far pointers). Practically speaking, no platform supported by ctypes makes this distinction, so c_size_t and c_ssize_t use the platform pointer size. https://hg.python.org/cpython/file/ab2c023a9432/Lib/ctypes/__init__.py#l459 OTOH, it's best to avoid accumulating layers of assumptions.

> Why not use c_size_t? Or is that incorrect in some cases?

Strictly speaking, size_t doesn't have to encompass the entire addressable range, such as for architectures that use segmented addressing (e.g. near and far pointers). Practically speaking, no platform supported by ctypes makes this distinction, so c_size_t and c_ssize_t use the platform pointer size.

https://hg.python.org/cpython/file/ab2c023a9432/Lib/ctypes/__init__.py#l459

OTOH, it's best to avoid accumulating layers of assumptions.

History
Date	User	Action	Args
2014-10-27 01:35:42	eryksun	set	recipients: + eryksun, amaury.forgeotdarc, belopolsky, pitrou, meador.inge, steve.dower
2014-10-27 01:35:42	eryksun	set	messageid: <1414373742.25.0.281779499665.issue22732@psf.upfronthosting.co.za>
2014-10-27 01:35:42	eryksun	link	issue22732 messages
2014-10-27 01:35:41	eryksun	create