http://ttul.org/~ingy/release/Inline-0.44-TRIAL4.tar.gz
Well this is a pretty big one, and some pretty big thanks go out to Mitchell
Charity for some pretty big patches.
Here's the Changes:
version: 0.44
date: Fri Oct 11 18:09:03 PDT 2002
changes:
- Added the USING keyword. This allows you to specify a list of modules
which can override certain parts of the Inline process.
- Added Inline::C::ParseRecDescent and Inline::C::ParseRegExp to
provide two (hopefully) functionally identical C parsers. You use
one of these by saying 'use Inline C => DATA => USING => "ParseRegExp"'.
Big thanks to Mitchell Charity for ParseRegExp. It's over two orders
of magnitude faster than ParseRecDescent.
- Added the more diagnostics to BUILD_NOISY.
- Added BUILD_TIMERS for benchmarking the Inline build process.
---
version: 0.44
date: Wed Oct 9 19:03:34 PDT 2002
changes:
- Applied a (BIG) patch to the Inline distribution to use File::Spec
to manipulate all file paths. Thanks Mitchell Charity!
Hopefully that explains things pretty well. The File::Spec stuff should
help get us closer to working with VMS and others. Testing here would be
appreciated. Inline::C::ParseRegExp is the first step towards speeding things
up. It also might work better than the old ::ParseRecDescent code in
detecting Nicholaus' signature combinations. So give that a try with your old
code. I'm strongly considering making ParseRegExp the default very soon, and
eliminating the strong dependency on Parse::RecDescent.
If all this makes your head spin, try playing around with this one liner:
perl -MInline=force,noisy,timers -e 'use Inline C=>q{void h(char*n){printf("hello,
%s\n",n);}},USING=>ParseRegExp;h"inline"'
I'd be interesting in hearing about your various benchmarks, and ideas for
speeding things up.
That's about it. Oh yeah; I didn't break Inline::CPP AFAICT.
Cheers, Brian
