Mark,
Random cage cleaner here. At Andy Lester's suggestion, I've begun working on this splint stuff. So everything below is all his fault. :)
Great to have another cage cleaner around :-) There aren't many of us at this stage!
<snip splint stuff> In my (very limited) dealings with splint I too have found problems with the standard headers, and have used the same options (if only to make splint get further before it barfs; btw: I'm using Gentoo linux as well). I think you're heading in the right direction though.
I'd like to spend some time trying to make "make splint" more portable... splint defines a special preprocessor variable when it runs, so maybe config.h can skip all the platform-specific stuff when that variable is defined, or something like that. And I'd like to spend some time fixing the source files I listed above, or, failing that, marking them somehow so splint will skip the erroneous stuff.
Awesome! Go for it!!! Start making patches (see http://www.parrotcode.org/docs/submissions.html for help on how to create patches) and send them to [EMAIL PROTECTED] and we'll review them and apply your changes. There is also the file docs/project/cage_cleaners_guide.pod in the Parrot distro, so if you're interested there's stuff to do there. Also, if you do a search on http://rt.perl.org/rt3//Public/ for "cage" then there's heaps to do there too :-)
I'd also like to spend some time researching and (hopefully) fixing some of the warnings in the above warning list, too. Is anyone already working on this?
When I have the tuits, yeah, but generally I work on other stuff, so any help in this department is *greatly* appreciated.
Does anyone have any interest in this?
I can't speak for everyone, but Parrot is going to be the most platform independent thing out there so making it as compliant as possible with every platform/compiler/etc is of interest to the project as a whole. So yes, I'd say there's interest :-)
Does anyone have an objection to it?
None whatsoever. Paul
