0UT1S's

usr/include/python2.7/

By Order of Mr.0UT1S

N/A

20.62 KB

4.27 KB

44.17 KB

1.07 KB

230 bytes

792 bytes

912 bytes

922 bytes

bytearrayobject.h

1.90 KB

bytes_methods.h

2.74 KB

1.13 KB

1.96 KB

651 bytes

4.94 KB

2.93 KB

2.86 KB

4.30 KB

6.03 KB

1.04 KB

complexobject.h

1.81 KB

8.12 KB

2.42 KB

6.73 KB

338 bytes

253 bytes

1.37 KB

557 bytes

3.58 KB

5.49 KB

3.18 KB

2.92 KB

891 bytes

1.87 KB

2.00 KB

2.17 KB

2.91 KB

274 bytes

522 bytes

2.51 KB

3.82 KB

5.67 KB

713 bytes

2.76 KB

253 bytes

3.28 KB

4.91 KB

609 bytes

938 bytes

39.12 KB

14.00 KB

4.70 KB

1.03 KB

1.74 KB

1.42 KB

253 bytes

1.15 KB

4.17 KB

2.63 KB

1.64 KB

37.02 KB

162 bytes

1.24 KB

1.29 KB

11.47 KB

2.07 KB

8.27 KB

348 bytes

2.92 KB

8.43 KB

7.16 KB

4.60 KB

31.79 KB

6.25 KB

463 bytes

1.54 KB

7.06 KB

1.13 KB

646 bytes

3.06 KB

1.64 KB

7.79 KB

2.83 KB

862 bytes

3.64 KB

865 bytes

541 bytes

1.76 KB

697 bytes

2.18 KB

924 bytes

unicodeobject.h

51.00 KB

635 bytes

weakrefobject.h

2.74 KB

/*
   CObjects are marked Pending Deprecation as of Python 2.7.
   The full schedule for 2.x is as follows:
     - CObjects are marked Pending Deprecation in Python 2.7.
     - CObjects will be marked Deprecated in Python 2.8
       (if there is one).
     - CObjects will be removed in Python 2.9 (if there is one).

Additionally, for the Python 3.x series:
     - CObjects were marked Deprecated in Python 3.1.
     - CObjects will be removed in Python 3.2.

You should switch all use of CObjects to capsules.  Capsules
   have a safer and more consistent API.  For more information,
   see Include/pycapsule.h, or read the "Capsules" topic in
   the "Python/C API Reference Manual".

Python 2.7 no longer uses CObjects itself; all objects which
   were formerly CObjects are now capsules.  Note that this change
   does not by itself break binary compatibility with extensions
   built for previous versions of Python--PyCObject_AsVoidPtr()
   has been changed to also understand capsules.

*/

/* original file header comment follows: */

/* C objects to be exported from one extension module to another.
 
   C objects are used for communication between extension modules.
   They provide a way for an extension module to export a C interface
   to other extension modules, so that extension modules can use the
   Python import mechanism to link to one another.

*/

#ifndef Py_COBJECT_H
#define Py_COBJECT_H
#ifdef __cplusplus
extern "C" {
#endif

PyAPI_DATA(PyTypeObject) PyCObject_Type;

#define PyCObject_Check(op) (Py_TYPE(op) == &PyCObject_Type)

/* Create a PyCObject from a pointer to a C object and an optional
   destructor function.  If the second argument is non-null, then it
   will be called with the first argument if and when the PyCObject is
   destroyed.

*/
PyAPI_FUNC(PyObject *) PyCObject_FromVoidPtr(
	void *cobj, void (*destruct)(void*));

/* Create a PyCObject from a pointer to a C object, a description object,
   and an optional destructor function.  If the third argument is non-null,
   then it will be called with the first and second arguments if and when 
   the PyCObject is destroyed.
*/
PyAPI_FUNC(PyObject *) PyCObject_FromVoidPtrAndDesc(
	void *cobj, void *desc, void (*destruct)(void*,void*));

/* Retrieve a pointer to a C object from a PyCObject. */
PyAPI_FUNC(void *) PyCObject_AsVoidPtr(PyObject *);

/* Retrieve a pointer to a description object from a PyCObject. */
PyAPI_FUNC(void *) PyCObject_GetDesc(PyObject *);

/* Import a pointer to a C object from a module using a PyCObject. */
PyAPI_FUNC(void *) PyCObject_Import(char *module_name, char *cobject_name);

/* Modify a C object. Fails (==0) if object has a destructor. */
PyAPI_FUNC(int) PyCObject_SetVoidPtr(PyObject *self, void *cobj);

typedef struct {
    PyObject_HEAD
    void *cobject;
    void *desc;
    void (*destructor)(void *);
} PyCObject;

#ifdef __cplusplus
}
#endif
#endif /* !Py_COBJECT_H */