File Manager

X7ROOT File Manager

Current Path: /opt/alt/python312/include/python3.12/internal

opt / alt / python312 / include / python3.12 / internal /

ðŸ“ ..
ðŸ“„ pycore_abstract.h(611 B)
ðŸ“„ pycore_asdl.h(2.96 KB)
ðŸ“„ pycore_ast.h(30.55 KB)
ðŸ“„ pycore_ast_state.h(6.59 KB)
ðŸ“„ pycore_atexit.h(1.12 KB)
ðŸ“„ pycore_atomic.h(16.58 KB)
ðŸ“„ pycore_atomic_funcs.h(2.38 KB)
ðŸ“„ pycore_bitutils.h(5.92 KB)
ðŸ“„ pycore_blocks_output_buffer.h(8.48 KB)
ðŸ“„ pycore_bytes_methods.h(3.3 KB)
ðŸ“„ pycore_bytesobject.h(1.31 KB)
ðŸ“„ pycore_call.h(3.83 KB)
ðŸ“„ pycore_ceval.h(5.14 KB)
ðŸ“„ pycore_ceval_state.h(2.68 KB)
ðŸ“„ pycore_code.h(15.46 KB)
ðŸ“„ pycore_compile.h(3.37 KB)
ðŸ“„ pycore_condvar.h(2.84 KB)
ðŸ“„ pycore_context.h(1.27 KB)
ðŸ“„ pycore_descrobject.h(499 B)
ðŸ“„ pycore_dict.h(6.23 KB)
ðŸ“„ pycore_dict_state.h(1.07 KB)
ðŸ“„ pycore_dtoa.h(1.58 KB)
ðŸ“„ pycore_emscripten_signal.h(562 B)
ðŸ“„ pycore_exceptions.h(842 B)
ðŸ“„ pycore_faulthandler.h(2.17 KB)
ðŸ“„ pycore_fileutils.h(7.72 KB)
ðŸ“„ pycore_fileutils_windows.h(2.66 KB)
ðŸ“„ pycore_floatobject.h(1.54 KB)
ðŸ“„ pycore_flowgraph.h(4.52 KB)
ðŸ“„ pycore_format.h(480 B)
ðŸ“„ pycore_frame.h(9.04 KB)
ðŸ“„ pycore_function.h(611 B)
ðŸ“„ pycore_gc.h(7.48 KB)
ðŸ“„ pycore_genobject.h(1.16 KB)
ðŸ“„ pycore_getopt.h(490 B)
ðŸ“„ pycore_gil.h(1.53 KB)
ðŸ“„ pycore_global_objects.h(2.96 KB)
ðŸ“„ pycore_global_objects_fini_generated.h(112.66 KB)
ðŸ“„ pycore_global_strings.h(24.84 KB)
ðŸ“„ pycore_hamt.h(3.65 KB)
ðŸ“„ pycore_hashtable.h(4.19 KB)
ðŸ“„ pycore_import.h(6.21 KB)
ðŸ“„ pycore_initconfig.h(5.57 KB)
ðŸ“„ pycore_instruments.h(2.93 KB)
ðŸ“„ pycore_interp.h(8.87 KB)
ðŸ“„ pycore_intrinsics.h(1.36 KB)
ðŸ“„ pycore_list.h(1.93 KB)
ðŸ“„ pycore_long.h(7.62 KB)
ðŸ“„ pycore_memoryobject.h(383 B)
ðŸ“„ pycore_moduleobject.h(1.16 KB)
ðŸ“„ pycore_namespace.h(392 B)
ðŸ“„ pycore_object.h(14.57 KB)
ðŸ“„ pycore_object_state.h(1016 B)
ðŸ“„ pycore_obmalloc.h(26.64 KB)
ðŸ“„ pycore_obmalloc_init.h(2.04 KB)
ðŸ“„ pycore_opcode.h(19.61 KB)
ðŸ“„ pycore_opcode_utils.h(2.62 KB)
ðŸ“„ pycore_parser.h(1.33 KB)
ðŸ“„ pycore_pathconfig.h(606 B)
ðŸ“„ pycore_pyarena.h(2.67 KB)
ðŸ“„ pycore_pyerrors.h(3.04 KB)
ðŸ“„ pycore_pyhash.h(709 B)
ðŸ“„ pycore_pylifecycle.h(3.29 KB)
ðŸ“„ pycore_pymath.h(8.4 KB)
ðŸ“„ pycore_pymem.h(2.97 KB)
ðŸ“„ pycore_pymem_init.h(2.59 KB)
ðŸ“„ pycore_pystate.h(4.87 KB)
ðŸ“„ pycore_pythread.h(2.03 KB)
ðŸ“„ pycore_range.h(346 B)
ðŸ“„ pycore_runtime.h(8.23 KB)
ðŸ“„ pycore_runtime_init.h(5.77 KB)
ðŸ“„ pycore_runtime_init_generated.h(44.68 KB)
ðŸ“„ pycore_signal.h(2.55 KB)
ðŸ“„ pycore_sliceobject.h(414 B)
ðŸ“„ pycore_strhex.h(937 B)
ðŸ“„ pycore_structseq.h(923 B)
ðŸ“„ pycore_symtable.h(6.87 KB)
ðŸ“„ pycore_sysmodule.h(999 B)
ðŸ“„ pycore_time.h(388 B)
ðŸ“„ pycore_token.h(2.98 KB)
ðŸ“„ pycore_traceback.h(3.42 KB)
ðŸ“„ pycore_tracemalloc.h(3 KB)
ðŸ“„ pycore_tuple.h(2.15 KB)
ðŸ“„ pycore_typeobject.h(4.62 KB)
ðŸ“„ pycore_typevarobject.h(763 B)
ðŸ“„ pycore_ucnhash.h(898 B)
ðŸ“„ pycore_unicodeobject.h(2.59 KB)
ðŸ“„ pycore_unicodeobject_generated.h(122.57 KB)
ðŸ“„ pycore_unionobject.h(682 B)
ðŸ“„ pycore_warnings.h(740 B)

Editing: pycore_pyarena.h

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

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

#ifndef Py_BUILD_CORE
#  error "this header requires Py_BUILD_CORE define"
#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_INTERNAL_PYARENA_H */

X7ROOT File Manager

Editing: pycore_pyarena.h

Upload File

Create Folder