summaryrefslogtreecommitdiffstats
path: root/Modules/pypcre.c
Commit message (Collapse)AuthorAgeFilesLines
* Remove pcre moduleAndrew M. Kuchling2004-06-021-4756/+0
|
* Fix a bunch of typos in documentation, docstrings and comments.Walter Dörwald2003-10-201-1/+1
| | | | (From SF patch #810751)
* Undefine DPRINTF before defining it, there was a conflict with some otherJack Jansen2002-06-261-0/+1
| | | | definition.
* First stab at rationalizing the PyMem_ API. Mixing PyObject_xyz withTim Peters2002-04-121-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | PyMem_{Del, DEL} doesn't work yet (compilation problems). pyport.h: _PyMem_EXTRA is gone. pmem.h: Repaired comments. PyMem_{Malloc, MALLOC} and PyMem_{Realloc, REALLOC} now make the same x-platform guarantees when asking for 0 bytes, and when passing a NULL pointer to the latter. object.c: PyMem_{Malloc, Realloc} just call their macro versions now, since the latter take care of the x-platform 0 and NULL stuff by themselves now. pypcre.c, grow_stack(): So sue me. On two lines, this called PyMem_RESIZE to grow a "const" area. It's not legit to realloc a const area, so the compiler warned given the new expansion of PyMem_RESIZE. It would have gotten the same warning before if it had used PyMem_Resize() instead; the older macro version, but not the function version, silently cast away the constness. IMO that was a wrong thing to do, and the docs say the macro versions of PyMem_xyz are deprecated anyway. If somebody else is resizing const areas with the macro spelling, they'll get a warning when they recompile now too.
* Include Python.h first. Fixes #530159.Martin v. Löwis2002-03-151-1/+1
|
* Fix for bug #110651 (Jitterbug PR#343): only use the low 8 bits of an octalAndrew M. Kuchling2000-08-021-1/+1
| | | | escape, as documented in the comment for the check_escape() function
* merge Include/my*.h into Include/pyport.hPeter Schneider-Kamp2000-07-311-1/+0
| | | | marked my*.h as obsolete
* Spelling fixes supplied by Rob W. W. Hooft. All these are fixes in eitherThomas Wouters2000-07-161-4/+4
| | | | | | | | | | 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 ;)
* Add more "volatile" decls to stop gcc -Wall warnings.Tim Peters2000-07-051-2/+2
| | | | | | | | Somebody w/ gcc please check that the wngs are gone! There are cheaper (at runtime) ways to prevent the wngs, but they're obscure and delicate. I'm going for the easy Big Hammer here under the theory that PCRE will be replaced by SRE anyway.
* Fix bug reported by atkins@gweep.net; re.compile(r"[\100-\410]")Andrew M. Kuchling2000-06-011-1/+1
| | | | | dumps core. Solution: fix check_escape() to match its comment and use only the low 8 bits of the octal number.
* Patch from Vladimir Marangozov <marangoz@python.inrialpes.fr>Andrew M. Kuchling2000-02-181-6/+6
| | | | | | | The same problem (mixed mallocs) exists for the pcre stack. The buffers md->... are allocated via PyMem_RESIZE in grow_stack(), while in free_stack() they are released with free() instead of PyMem_DEL().
* pcre_exec(): Andrew Kuchling's patch for pcre memory leak.Barry Warsaw1999-01-271-0/+1
|
* Add dummy variable to avoid optimizer bug on OS/2 -- patch by Jeff Rush.Guido van Rossum1998-12-211-0/+2
| | | | (AMK: you should probably copy this into your patch set for pcre.)
* Fix benign problems found by a picky SGI compiler (unreachable breakGuido van Rossum1998-07-071-2/+0
| | | | after a return or goto).
* AMK's revised version of the previous patch.Guido van Rossum1998-05-071-8/+24
|
* Address warnings issued by the MSVC++ compilerGuido van Rossum1998-04-101-2/+2
|
* AMK's latestGuido van Rossum1998-04-031-47/+119
|
* patch for re.sub bug, by AMK.Guido van Rossum1998-03-101-2/+3
|
* A bug in PCRE could cause core dumps in patterns such asGuido van Rossum1998-02-201-2/+7
| | | | '((a)*)*'. Andrew Kuchling posted a fix to the string-sig.
* AMK's latest -- synchronized with PCRE 1.04.Guido van Rossum1997-12-221-123/+168
|
* AMK's latest; plus three null bytes that I added for purifyGuido van Rossum1997-12-171-146/+121
|
* Patch (by Andrew Kuchling of course) to prevent named back referencesGuido van Rossum1997-12-151-1/+1
| | | | in the pattern to wear out the reference count on small integers.
* The 'l' flag (locale specific matching) has been renamed to 'L'.Guido van Rossum1997-12-101-2/+2
|
* New pcre version from AMKGuido van Rossum1997-12-081-714/+1275
|
* Patches by Fred Lundh to make it compile better with K&R compilers.Guido van Rossum1997-12-021-20/+20
| | | | | (Should really let AMK do this, but don't know when he'll give me a new version.)
* Checking in AMK's latest installement.Guido van Rossum1997-10-081-16/+18
| | | | (Two small changes to shup up gcc added.)
* New "re" regular expression support.Guido van Rossum1997-10-061-0/+4075
This code is written by Philip Hazel and Andrew Kuchling. It requires a new "re.py" module, too.