Staging
v0.5.0
https://github.com/python/cpython
Raw File
Tip revision: 3540ef16c19f2260e347a679cb27d44ba734bec6 authored by Guido van Rossum on 31 August 2007, 15:07:53 UTC
Tagging for release of Python 3.0a1.
Tip revision: 3540ef1
memoryobject.h

/* Memory object interface */

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

typedef struct {
        PyObject_HEAD
        PyObject *base;
        PyBuffer view;
} PyMemoryViewObject;


PyAPI_DATA(PyTypeObject) PyMemoryView_Type;

#define PyMemory_Check(op) (Py_Type(op) == &PyMemoryView_Type)
#define PyMemoryView(op) (((PyMemoryViewObject *)(op))->view)

#define Py_END_OF_MEMORY	(-1)

PyAPI_FUNC(PyObject *) PyMemoryView_GetContiguous(PyObject *base, int buffertype, 
                                                  char fort);

	/* Return a contiguous chunk of memory representing the buffer
	   from an object in a memory view object.  If a copy is made then the
           base object for the memory view will be a *new* bytes object. 
           
           Otherwise, the base-object will be the object itself and no 
           data-copying will be done. 

           The buffertype argument can be PyBUF_READ, PyBUF_WRITE,
           PyBUF_UPDATEIFCOPY to determine whether the returned buffer
           should be READONLY, WRITEABLE, or set to update the
           original buffer if a copy must be made.  If buffertype is
           PyBUF_WRITE and the buffer is not contiguous an error will
           be raised.  In this circumstance, the user can use
           PyBUF_UPDATEIFCOPY to ensure that a a writeable temporary
           contiguous buffer is returned.  The contents of this
           contiguous buffer will be copied back into the original
           object after the memoryview object is deleted as long as
           the original object is writeable and allows setting its
           memory to "readonly".  If this is not allowed by the
           original object, then a BufferError is raised.
	   
           If the object is multi-dimensional and if fortran is 'F',
           the first dimension of the underlying array will vary the
           fastest in the buffer.  If fortran is 'C', then the last
           dimension will vary the fastest (C-style contiguous).  If
           fortran is 'A', then it does not matter and you will get
           whatever the object decides is more efficient.  

           A new reference is returned that must be DECREF'd when finished.
        */

PyAPI_FUNC(PyObject *) PyMemoryView_FromObject(PyObject *base);

PyAPI_FUNC(PyObject *) PyMemoryView_FromMemory(PyBuffer *info);
	/* create new if bufptr is NULL 
	    will be a new bytesobject in base */

#ifdef __cplusplus
}
#endif
#endif /* !Py_MEMORYOBJECT_H */
back to top