Excellent. Could you tell me more about the crucial bug?
We're up to two now, I think. Here's the first for sure: http://
rt.perl.org/rt3/Ticket/Display.html?id=44019
We're returning a pointer to a struct on the stack.
Basically, what I'm doing is installing as many seat belts in the
code as I can. I've got GCC's warnings cranked as high as I can; I'm
building with Intel's ICC; I've got a Solaris box for the sole
purpose of running Sun Studio 12's lint; and we're running splint.
We've got infrastructure in place for giving hints to all of those
various tools. Scan is certainly the most powerful in terms of
tracking paths, though.
Paul and I were exchanging messages about that tonight. I definitely
want to scan all projects more often, but there's a build dependency
tracking non-scalability issue.
Could we do something to minimize the amount of time it takes? Could
we give you a subset of files to scan?
I'm working on a few different approaches to handling that. Paul
said he
believes you're going to be as OSCON next week? I'll be there all
week,
and I'm giving a presentation about Scan on Thursday. We could find
some
time to chat - I'd like to hear about your experiences with the perl
results as well.
Yeah, I'm coming in Saturday night, and then leaving Friday. I'm
coming in early specifically to hang out and talk to people.
I've added you to my OSCON plans: http://xoa.petdance.com/
OSCON_2007_plans
And of course you have to come hear me talk about technical debt.
Probably we should get together some time before Wednesday,
especially if you want to get stuff for your talk about the Perl
help, although they might be pretty far out in my mind to remember.
The Perl 5 codebase is RADICALLY different from the Parrot one, thank
goodness.
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
