summaryrefslogtreecommitdiffstats
path: root/Python/getargs.c
Commit message (Collapse)AuthorAgeFilesLines
* Changes for BeOS, QNX and long long, by Chris Herborth.Guido van Rossum1998-08-041-0/+22
|
* Another veeeeeery old patch...Guido van Rossum1998-05-151-9/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Date: Thu, 14 Sep 1995 12:18:20 -0400 From: Alan Morse <alan@dvcorp.com> To: python-list@cwi.nl Subject: getargs bug in 1.2 and 1.3 BETA We have found a bug in the part of the getargs code that we added and submitted, and which was incorporated into 1.1. The parsing of "O?" format specifiers is not handled correctly; there is no "else" for the "if" and therefore it can never fail. What's worse, the advancing of the varargs pointer is not handled properly, so from then on it is out of sync, wreaking all sorts of havoc. (If it had failed properly, then the out-of-sync varargs would not have been an issue.) Below is the context diff for the change. Note that I have made a few stylistic changes beyond adding the else case, namely: 1) Making the "O" case follow the convention established by the other format specifiers of getting all their vararg arguments before performing the test, rather than getting some before and some after the test passes. 2) Making the logic of the tests parallel, so the "if" part indicates that the format is accepted and the "else" part indicates that the format has failed. They were inconsistent with each other and with the the other format specifiers. -Alan Morse (amorse@dvcorp.com)
* Make new gcc -Wall happyGuido van Rossum1998-04-101-1/+1
|
* Protect PyErr_Format format string argument from overflow (ironically,Guido van Rossum1998-01-191-1/+1
| | | | the error was about a bad format string :-).
* Oops -- '(' is also a legal start character of a new format...Guido van Rossum1997-12-191-0/+1
|
* Add explicit check for correct next character in format at end ofGuido van Rossum1997-12-091-0/+7
| | | | | format. This will complain about illegal formats like "O#" instead of ignoring the '#'.
* Checkin of Jack's buffer mods.Guido van Rossum1997-05-051-25/+89
| | | | Not really checked, but didn't fail any tests either...
* Fix old typo PyArgs_VaParse -> PyArg_VaParse.Guido van Rossum1997-05-051-2/+2
| | | | (Redoing the checking without merging in Jack's buffer mods.)
* Quickly renamed the remaining files -- this directory is done.Guido van Rossum1997-04-291-95/+96
|
* Keep gcc -Wall and Microsoft VC happy.Guido van Rossum1997-04-111-5/+5
|
* Keep gcc -Wall happy.Guido van Rossum1996-12-051-24/+23
|
* New permission notice, includes CNRI.Guido van Rossum1996-10-251-10/+17
|
* Add needed #include <ctype.h>Guido van Rossum1996-08-211-0/+2
|
* Support for keyword arguments (PyArg_ParseTupleAndKeywords) donated byGuido van Rossum1996-08-191-3/+383
| | | | | | | Geoff Philbrick <philbric@delphi.hks.com> (slightly changed by me). Also a little change to make the file acceptable to K&R C compilers (HPUX, SunOS 4.x).
* Py_complex; and WITHOUT_COMPLEX added to getargs.cGuido van Rossum1996-07-211-2/+4
|
* changes for complex numbersGuido van Rossum1996-01-121-0/+11
|
* don't overwrite error already set (e.g. from O&)Guido van Rossum1995-01-211-1/+3
|
* Added 1995 to copyright message.Guido van Rossum1995-01-041-2/+2
| | | | | | bltinmodule.c: fixed coerce() nightmare in ternary pow(). modsupport.c (initmodule2): pass METH_FREENAME flag to newmethodobject(). pythonrun.c: move flushline() into and around print_error().
* Lots of changes, most minor (fatal() instead of abort(), use ofGuido van Rossum1995-01-021-8/+16
| | | | | | err_fetch/err_restore and so on). But... NOTE: import.c has been rewritten and all the DL stuff is now in the new file importdl.c.
* prevent core dump for old getargs() with NULL argGuido van Rossum1994-11-101-0/+7
|
* * Python/{modsupport.c,getargs.c,Makefile.in},Guido van Rossum1994-09-291-0/+587
Include/modsupport.h: moved getargs() to its own file and re-implemented it entirely to support optional arguments, multiple arguments without surrounding parentheses (when called as newgetargs()), and better error messages