summaryrefslogtreecommitdiffstats
path: root/Objects/bufferobject.c
Commit message (Collapse)AuthorAgeFilesLines
* Fix for Bug #216405:Thomas Heller2001-10-191-4/+6
| | | | use the correct base for a buffer object in _PyBuffer_FromObject.
* repr's converted to using PyString_FromFormat() instead of sprintf'ingBarry Warsaw2001-08-241-13/+7
| | | | | | into a hardcoded char* buffer. Closes patch #454743.
* Merge of descr-branch back into trunk.Tim Peters2001-08-021-17/+17
|
* REMOVED all CWI, CNRI and BeOpen copyright markings.Guido van Rossum2000-09-011-9/+0
| | | | This should match the situation in the 1.6b1 tree.
* Removing warnings found by gcc -WallMoshe Zadka2000-08-041-4/+5
|
* ANSI-fication of the sources.Fred Drake2000-07-091-78/+24
|
* Change copyright notice - 2nd try.Guido van Rossum2000-06-301-6/+0
|
* Change copyright notice.Guido van Rossum2000-06-301-22/+7
|
* Trent Mick <trentm@activestate.com>:Fred Drake2000-06-301-7/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | The common technique for printing out a pointer has been to cast to a long and use the "%lx" printf modifier. This is incorrect on Win64 where casting to a long truncates the pointer. The "%p" formatter should be used instead. The problem as stated by Tim: > Unfortunately, the C committee refused to define what %p conversion "looks > like" -- they explicitly allowed it to be implementation-defined. Older > versions of Microsoft C even stuck a colon in the middle of the address (in > the days of segment+offset addressing)! The result is that the hex value of a pointer will maybe/maybe not have a 0x prepended to it. Notes on the patch: There are two main classes of changes: - in the various repr() functions that print out pointers - debugging printf's in the various thread_*.h files (these are why the patch is large) Closes SourceForge patch #100505.
* Vladimir Marangozov's long-awaited malloc restructuring.Guido van Rossum2000-05-031-4/+4
| | | | | | | | | | For more comments, read the patches@python.org archives. For documentation read the comments in mymalloc.h and objimpl.h. (This is not exactly what Vladimir posted to the patches list; I've made a few changes, and Vladimir sent me a fix in private email for a problem that only occurs in debug mode. I'm also holding back on his change to main.c, which seems unnecessary to me.)
* PyBuffer_New(): Raise ValueError if size is negative (the otherFred Drake1999-08-041-1/+6
| | | | | | | constructors didn't miss this). Raise MemoryError if malloc() fails, instead of just returning NULL.
* Folded long lines.Guido van Rossum1999-03-241-9/+18
|
* Added check for negative offset for PyBuffer_FromObject and check forGuido van Rossum1999-03-191-1/+13
| | | | negative size for PyBuffer_FromMemory. Greg Stein.
* Greg Stein: Implement the new bf_getcharbuffer function, indicatingGuido van Rossum1998-10-081-2/+18
| | | | that (as far as the data type is concerned!) this is character data.
* Make gcc -Wall happy.Guido van Rossum1998-10-071-5/+4
|
* Add Greg Stein's buffer object API.Guido van Rossum1998-10-071-0/+599