Fri, 22 Sep 2006 21:51:38 -0700> From: [EMAIL PROTECTED]> To: [EMAIL PROTECTED]> Subject: Re: [Python-Dev] Typo.pl scan of Python 2.5 source code> CC: python-dev@python.org> > On 9/22/06, Johnny Lee <[EMAIL PROTECTED]> wrote:> >> > Hello,> > My name is Johnn
"Neal Norwitz" <[EMAIL PROTECTED]> writes:
> I ignored these as I'm not certain all the platforms we run on accept
> free(NULL).
It's mandated by C99, and I don't *think* it changed from the previous
version (I only have a bootleg copy of C99 :).
Cheers,
mwh
--
TRSDOS: Friendly old lizard. O
"Neal Norwitz" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I ignored these as I'm not certain all the platforms we run on accept
> free(NULL).
>
That sounds like exactly what the autotools are designed for. You simply use
free(), and have autoconf check for support of free(NUL
On 9/22/06, Johnny Lee <[EMAIL PROTECTED]> wrote:
>
> Hello,
> My name is Johnny Lee. I have developed a *ahem* perl script which scans
> C/C++ source files for typos.
Hi Johnny.
Thanks for running your script, even if it is written in Perl and ran
on Windows. :-)
> The Python 2.5 typos can be c
Hello,My name is Johnny Lee. I have developed a *ahem* perl script which scans C/C++ source files for typos. I ran the typo.pl script on the released Python 2.5 source code. The scan took about two minutes and produced ~340 typos.After spending about 13 minutes weeding out the obvious false p
