PySide Shiboken Sequence Protocol: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
AutoSpider (talk | contribs) (Add "cleanup" tag) |
||
Line 1: | Line 1: | ||
{{Cleanup | reason=Auto-imported from ExpressionEngine.}} | |||
[[Category:LanguageBindings::PySide]] | [[Category:LanguageBindings::PySide]] | ||
Revision as of 16:19, 3 March 2015
This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine. Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean. |
PySide Shiboken Sequence Protocol
Support for the sequence protocol is achieved adding functions with special names, this is done using the add-function tag.
The special function names are:
Function name | Parameters | Return type | CPython equivalent |
---|---|---|---|
__len__ | PyObject* self | Py_ssize_t | PySequence_Size |
__getitem__ | PyObject* self, Py_ssize_t _i | PyObject* | PySequence_GetItem |
__setitem__ | PyObject* self, Py_ssize_t _i, PyObject* _value | int | PySequence_SetItem |
__contains__ | PyObject* self, PyObject* _value | int | PySequence_Contains |
__concat__ | PyObject* self, PyObject* _other | PyObject* | PySequence_Concat |
You just need to inform the function name to the add-function tag, without any parameter or return type information, when you do it, Shiboken will create a C function with parameters and return type definied by the table above.
The function needs to follow the same semantics of the CPython equivalent function, the only way to do it is using the inject-code tag.