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 eckhardt
Recipients belopolsky, christian.heimes, eckhardt, jhylton, sebastinas
Date 2009-01-02.14:03:37
SpamBayes Score 1.7470987e-07
Marked as misclassified No
Message-id <1230905018.89.0.89434507226.issue1699259@psf.upfronthosting.co.za>
In-reply-to
Content
Concerning the SetArgv( int, char**), that one will have to be changed
to a SetArgv( int, char const* const*), i.e. applying the const on both
levels. Otherwise, there is no implicit conversion between the two.

The reason is a bit complicated: if the function stored a
pointer-to-const in the array, it would become a pointer-to-nonconst
outside. Only if modification of the array is forbidden, changing the
element type to pointer-to-const is allowed.

Otherwise, I'm +1 on this kind of changes, because it makes immediately
obvious which functions modify a passed buffer and which don't.
History
Date User Action Args
2009-01-02 14:03:39eckhardtsetrecipients: + eckhardt, jhylton, belopolsky, christian.heimes, sebastinas
2009-01-02 14:03:38eckhardtsetmessageid: <1230905018.89.0.89434507226.issue1699259@psf.upfronthosting.co.za>
2009-01-02 14:03:38eckhardtlinkissue1699259 messages
2009-01-02 14:03:37eckhardtcreate