summaryrefslogtreecommitdiffstats
path: root/Parser
Commit message (Collapse)AuthorAgeFilesLines
* Removed all instances of RETSIGTYPE from the source code: signalTim Peters2000-07-231-3/+2
| | | | | | | handlers "return void", according to ANSI C. Removed the new Py_RETURN_FROM_SIGNAL_HANDLER macro. Left RETSIGTYPE in the config stuff, because it's not clear to me that others aren't relying on it (e.g., extension modules).
* Recent ANSIfication introduced a couple instances ofTim Peters2000-07-231-3/+1
| | | | | | | | | | | #if RETSIGTYPE != void That isn't C, and MSVC properly refuses to compile it. Introduced new Py_RETURN_FROM_SIGNAL_HANDLER macro in pyport.h to expand to the correct thing based on RETSIGTYPE. However, only void is ANSI! Do we still have platforms that return int? The Unix config mess appears to #define RETSIGTYPE by magic without being asked to, so I assume it's "a problem" across Unices still.
* Remember to return something if RETSIGTYPE is not 'void'. Do we still needThomas Wouters2000-07-221-0/+3
| | | | | to worry about systems that have signal-handlers return 'int' ? Not all of the code does, though nothing will break because of it.
* Mass ANSIfication.Thomas Wouters2000-07-2216-330/+123
| | | | | | Work around intrcheck.c's desire to pass 'PyErr_CheckSignals' to 'Py_AddPendingCall' by providing a (static) wrapper function that has the right number of arguments.
* Spelling fixes supplied by Rob W. W. Hooft. All these are fixes in eitherThomas Wouters2000-07-161-1/+1
| | | | | | | | | | comments, docstrings or error messages. I fixed two minor things in test_winreg.py ("didn't" -> "Didn't" and "Didnt" -> "Didn't"). There is a minor style issue involved: Guido seems to have preferred English grammar (behaviour, honour) in a couple places. This patch changes that to American, which is the more prominent style in the source. I prefer English myself, so if English is preferred, I'd be happy to supply a patch myself ;)
* Create two new exceptions: IndentationError and TabError. These areFred Drake2000-07-114-13/+20
| | | | | | | used for indentation related errors. This patch includes Ping's improvements for indentation-related error messages. Closes SourceForge patches #100734 and #100856.
* Nuke all remaining occurrences of Py_PROTO and Py_FPROTO.Tim Peters2000-07-0916-54/+51
|
* Include limits.h if we have it.Jack Jansen2000-07-031-0/+3
|
* Change copyright notice - 2nd try.Guido van Rossum2000-06-3020-120/+0
|
* Change copyright notice.Guido van Rossum2000-06-3020-429/+129
|
* Trent Mick: familiar simple Win64 patchesGuido van Rossum2000-06-284-11/+14
|
* Jack Jansen: Removed Macintosh tab-guessing codeGuido van Rossum2000-06-281-7/+0
|
* Add new parser error code, E_OVERFLOW. This error is returned whenJeremy Hylton2000-06-202-17/+23
| | | | | | the number of children of a node exceeds the max possible value for the short that is used to count them. The Python runtime converts this parser error into the SyntaxError "expression too long."
* Vladimir Marangozov's long-awaited malloc restructuring.Guido van Rossum2000-05-034-15/+18
| | | | | | | | | | 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.)
* Ignore a bunch of generated files.Barry Warsaw2000-05-021-0/+3
|
* Only write message about changed Tab size with -v.Guido van Rossum2000-04-031-1/+2
|
* Fix by Eric Raymond: make the code that looks for various bits ofGuido van Rossum2000-03-311-15/+30
| | | | | tab-setting magic much smarter, more correct, and more easily extensible.
* Marc-Andre Lemburg: add new string token types u"..." and ur"..."Guido van Rossum2000-03-101-0/+10
| | | | (Unicode and raw Unicode).
* Make sure that -t and -tt also work on strings passed to compile().Guido van Rossum1998-12-211-0/+7
|
* One more fprintf bites the dist -- use PySys_WriteStderrGuido van Rossum1998-12-041-1/+1
|
* Need to add default decl of DL_IMPORT, for mymalloc.hGuido van Rossum1998-12-041-0/+6
|
* Changes to deal with the sigcheck+intrcheck vs. signalmodule controversy.Guido van Rossum1998-10-071-2/+7
|
* The previous fix was still broken; the Py_END_ALLOW_THREADS macro wasGuido van Rossum1998-08-291-1/+3
| | | | never executed because of a return statement. Sigh.
* We now assume that PyOS_Readline() is called with the interpreter lockGuido van Rossum1998-08-271-11/+3
| | | | | held. It releases the lock around the call to the function pointed to by PyOS_ReadlineFunctionPointer (default PyOS_StdioReadline()).
* Replace all calls to fprintf(stderr, ...) with PySys_WriteStderr(...).Guido van Rossum1998-08-251-5/+6
|
* Add a version of PySys_WriteStderr() that writes to stderr, so we canGuido van Rossum1998-08-251-0/+27
| | | | use it in tokenizer.c.
* There's a bunch of files that shouldn't be included in libpython*.a!Guido van Rossum1998-08-091-4/+5
|
* Make new gcc -Wall happyGuido van Rossum1998-04-102-2/+2
|
* Declare and use Py_TabcheckFlag here.Guido van Rossum1998-04-101-0/+8
|
* Add dummy Py_VerboseFlag now that it's referenced in parsetok.c.Guido van Rossum1998-04-101-0/+1
|
* Add checking for inconsistent tab usageGuido van Rossum1998-04-092-3/+49
|
* Add $(LIBS) to the pgen link line.Guido van Rossum1998-04-091-1/+2
|
* Swap two statements in the dedent check loop. This makes absolutelyGuido van Rossum1998-02-161-1/+1
| | | | | no difference, but avoids triggering an optimizer bug in the AIX compiler where the loop unrolling does the wrong thing...
* Fixed the bug in searching for triple quotes -- change the 'quote2'Guido van Rossum1998-02-161-2/+2
| | | | | variable from a pointer to an index, so a realloc() of the buffer won't disturb it. Problem found by Vladimir Marangozov.
* tok_nextc() should return unsigned characters, to avoid mistakingGuido van Rossum1998-01-191-2/+10
| | | | '\377' for EOF.
* Patch for QNX, by Chris Herborth.Guido van Rossum1997-12-021-2/+2
|
* This fix (across 4 files in 3 directories) solves a subtle problem withGuido van Rossum1997-11-141-0/+5
| | | | | | | | | | | | | | | signal handlers in a fork()ed child process when Python is compiled with thread support. The bug was reported by Scott <scott@chronis.icgroup.com>. What happens is that after a fork(), the variables used by the signal module to determine whether this is the main thread or not are bogus, and it decides that no thread is the main thread, so no signals will be delivered. The solution is the addition of PyOS_AfterFork(), which fixes the signal module's variables. A dummy version of the function is present in the intrcheck.c source file which is linked when the signal module is not used.
* Renamed Py_input_hook to PyOS_InputHook.Guido van Rossum1997-08-111-3/+3
| | | | Also cleaned out some CR's left by the VC++ editor.
* Move GNU readline interface to ../Modules/readline.c.Guido van Rossum1997-08-051-78/+3
| | | | Add Py_input_hook (used by _tkinter and perhaps Gist).
* Added finalization routines.Guido van Rossum1997-08-022-1/+44
|
* Finally plug the memory leak caused by syntax error (includingGuido van Rossum1997-07-271-1/+4
| | | | interactive EOF, which leaked *one* byte).
* New build procedure.Guido van Rossum1997-07-191-15/+20
|
* Oops, missed some renamings.Guido van Rossum1997-05-071-1/+1
|
* Another directory quickly renamed.Guido van Rossum1997-04-2918-205/+218
|
* Now that the string-sig has settled on r"obin" strings, restrict theGuido van Rossum1997-04-251-3/+7
| | | | <letter><string> notation to 'r' and 'R'.
* (Jack:) On the Mac, give syntax error on \r.Guido van Rossum1997-04-111-0/+11
|
* Remove two unised variables.Guido van Rossum1997-04-091-2/+0
|
* Support for alternative string quotes (a"xx", b"xx", c"xx", ...).Guido van Rossum1997-04-061-4/+9
|
* Allow leading underscore in keywords.Guido van Rossum1997-04-021-1/+1
|
* Restructured quite a bit, hopefully Lee Busby will find this useful.Guido van Rossum1997-02-181-50/+82
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Also grandly renamed. Here's the new interface: When WITH_READLINE is defined, two functions are defined: - PyOS_GnuReadline (what used to be my_readline() with WITH_READLINE) - PyOS_ReadlineInit (for Dave Ascher) Always, these functions are defined: - PyOS_StdioReadline (what used to be my_readline() without WITH_READLINE) - PyOS_Readline (the interface used by tokenizer.c and [raw_]input(). There's a global function pointer PyOS_ReadlineFunctionPointer, initialized to NULL. When PyOS_Readline finds this to be NULL, it sets it to either PyOS_GnuReadline or PyOS_StdioReadline depending on which one makes more sense (i.e. it uses GNU only if it is defined *and* stdin is indeed a tty device). An embedding program that has its own wishes can set the function pointer to a function of its own design. It should take a char* prompt argument (which may be NULL) and return a string *ending in a \n character* -- or "" for EOF or NULL for a user interrupt. --Guido van Rossum (home page: http://www.python.org/~guido/)
generated by cgit v0.12 at 2024-09-22 19:14:22 (GMT)