C warnings: which merit cage-cleaning?

James E Keenan jkeen at verizon.net
Thu Aug 16 11:56:01 UTC 2012


On 8/16/12 2:23 AM, Stefan Seifert wrote:
> On Wednesday 15 August 2012 22:25:27 James E Keenan wrote:
>> Tonight I had occasion to grep for the C warnings generated while
>> running 'make' for each of the whiteknight/io_cleanup1 and threads branches.
>>
>> threads:  http://nopaste.snit.ch/157225
>
> None of these are in code the threads branch touched, so they all should be in
> master as well. We probably should focus on master first before looking at
> branches to avoid fixing the same problems multiple times.
>

Yes, I found the C warnings as fallout from at attempt to diagnose some 
Perl warnings.  And we should focus on master first.  However, the 
io_cleanup1 branch had more than twice the number of warnings as the 
threads branch, so perhaps we should see if we can do some cleanup there 
before merging.

Thank you very much.
Jim Keenan


More information about the parrot-dev mailing list