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

/* An arena-like memory interface for the compiler.
 */

#ifndef Py_PYARENA_H
#define Py_PYARENA_H

#ifdef __cplusplus
extern "C" {
#endif

typedef struct _arena PyArena;

/* PyArena_New() and PyArena_Free() create a new arena and free it,
     respectively.  Once an arena has been created, it can be used
     to allocate memory via PyArena_Malloc().  Pointers to PyObject can
     also be registered with the arena via PyArena_AddPyObject(), and the
     arena will ensure that the PyObjects stay alive at least until
     PyArena_Free() is called.  When an arena is freed, all the memory it
     allocated is freed, the arena releases internal references to registered
     PyObject*, and none of its pointers are valid.
     XXX (tim) What does "none of its pointers are valid" mean?  Does it
     XXX mean that pointers previously obtained via PyArena_Malloc() are
     XXX no longer valid?  (That's clearly true, but not sure that's what
     XXX the text is trying to say.)

PyArena_New() returns an arena pointer.  On error, it
     returns a negative number and sets an exception.
     XXX (tim):  Not true.  On error, PyArena_New() actually returns NULL,
     XXX and looks like it may or may not set an exception (e.g., if the
     XXX internal PyList_New(0) returns NULL, PyArena_New() passes that on
     XXX and an exception is set; OTOH, if the internal
     XXX block_new(DEFAULT_BLOCK_SIZE) returns NULL, that's passed on but
     XXX an exception is not set in that case).
  */
  PyAPI_FUNC(PyArena *) PyArena_New(void);
  PyAPI_FUNC(void) PyArena_Free(PyArena *);

/* Mostly like malloc(), return the address of a block of memory spanning
   * `size` bytes, or return NULL (without setting an exception) if enough
   * new memory can't be obtained.  Unlike malloc(0), PyArena_Malloc() with
   * size=0 does not guarantee to return a unique pointer (the pointer
   * returned may equal one or more other pointers obtained from
   * PyArena_Malloc()).
   * Note that pointers obtained via PyArena_Malloc() must never be passed to
   * the system free() or realloc(), or to any of Python's similar memory-
   * management functions.  PyArena_Malloc()-obtained pointers remain valid
   * until PyArena_Free(ar) is called, at which point all pointers obtained
   * from the arena `ar` become invalid simultaneously.
   */
  PyAPI_FUNC(void *) PyArena_Malloc(PyArena *, size_t size);

/* This routine isn't a proper arena allocation routine.  It takes
   * a PyObject* and records it so that it can be DECREFed when the
   * arena is freed.
   */
  PyAPI_FUNC(int) PyArena_AddPyObject(PyArena *, PyObject *);

#ifdef __cplusplus
}
#endif

#endif /* !Py_PYARENA_H */