@@ -228,30 +228,30 @@ Implementing functions and methods
228
228
Structure used to describe a method of an extension type. This structure has
229
229
four fields:
230
230
231
- .. c :member :: const char * PyMethodDef. ml_name
231
+ .. c :member :: const char * ml_name
232
232
233
233
name of the method
234
234
235
- .. c :member :: PyCFunction PyMethodDef. ml_meth
235
+ .. c :member :: PyCFunction ml_meth
236
236
237
237
pointer to the C implementation
238
238
239
- .. c :member :: int PyMethodDef. ml_flags
239
+ .. c :member :: int ml_flags
240
240
241
241
flags bits indicating how the call should be constructed
242
242
243
- .. c :member :: const char * PyMethodDef. ml_doc
243
+ .. c :member :: const char * ml_doc
244
244
245
245
points to the contents of the docstring
246
246
247
- The :c:member: `PyMethodDef. ml_meth ` is a C function pointer. The functions may be of different
247
+ The :c:member: `ml_meth ` is a C function pointer. The functions may be of different
248
248
types, but they always return :c:expr: `PyObject* `. If the function is not of
249
249
the :c:type: `PyCFunction `, the compiler will require a cast in the method table.
250
250
Even though :c:type: `PyCFunction ` defines the first parameter as
251
251
:c:expr: `PyObject* `, it is common that the method implementation uses the
252
252
specific C type of the *self * object.
253
253
254
- The :c:member: `PyMethodDef. ml_flags ` field is a bitfield which can include the following flags.
254
+ The :c:member: `ml_flags ` field is a bitfield which can include the following flags.
255
255
The individual flags indicate either a calling convention or a binding
256
256
convention.
257
257
0 commit comments