@@ -228,30 +228,30 @@ Implementing functions and methods
228228 Structure used to describe a method of an extension type. This structure has
229229 four fields:
230230
231- .. c :member :: const char * PyMethodDef. ml_name
231+ .. c :member :: const char * ml_name
232232
233233 name of the method
234234
235- .. c :member :: PyCFunction PyMethodDef. ml_meth
235+ .. c :member :: PyCFunction ml_meth
236236
237237 pointer to the C implementation
238238
239- .. c :member :: int PyMethodDef. ml_flags
239+ .. c :member :: int ml_flags
240240
241241 flags bits indicating how the call should be constructed
242242
243- .. c :member :: const char * PyMethodDef. ml_doc
243+ .. c :member :: const char * ml_doc
244244
245245 points to the contents of the docstring
246246
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
248248types, but they always return :c:expr: `PyObject* `. If the function is not of
249249the :c:type: `PyCFunction `, the compiler will require a cast in the method table.
250250Even though :c:type: `PyCFunction ` defines the first parameter as
251251:c:expr: `PyObject* `, it is common that the method implementation uses the
252252specific C type of the *self * object.
253253
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.
255255The individual flags indicate either a calling convention or a binding
256256convention.
257257
0 commit comments