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 ncoghlan
Recipients BreamoreBoy, doerwalter, gvanrossum, ncoghlan, philipdumont
Date 2010-09-20.11:16:40
SpamBayes Score 1.2428947e-12
Marked as misclassified No
Message-id <1284981402.94.0.283884189406.issue1866@psf.upfronthosting.co.za>
In-reply-to
Content
I'm rejecting this due to the effect it has on the output parameters.

The patch ends up have to stick (char *) casts in several places because a pointer into the string provided via the char * input parameter is returned by each affected API to the calling function via a char **output parameter.

We can't change the signature of the output parameters since that would break existing code. That then means we also can't change the signature of the input parameters, since we can't guarantee that the recipient of the output parameter won't later use it to change things.

The calling code knows whether or not it is going to modify the pointer it receives back, and hence whether or not it is safe to cast away the const-ness of the passed in pointer.
History
Date User Action Args
2010-09-20 11:16:43ncoghlansetrecipients: + ncoghlan, gvanrossum, doerwalter, philipdumont, BreamoreBoy
2010-09-20 11:16:42ncoghlansetmessageid: <1284981402.94.0.283884189406.issue1866@psf.upfronthosting.co.za>
2010-09-20 11:16:41ncoghlanlinkissue1866 messages
2010-09-20 11:16:40ncoghlancreate