Howdy,

Thanks for this awesome work, Andy. I have added a summary of the new
compiler flags to the ChangeLog.

Duke

On Fri, Mar 16, 2012 at 11:31 PM, Andy Lester <[email protected]> wrote:
> I've been adding more and more compiler flags for safety.  I know some of 'em 
> are breaking the builds, but I think that when we get through with it, Parrot 
> will be much safer.
>
> Example:  I added a flag that makes it an error to call a function for which 
> there has been no declaration.  Imagine that, right?  Apparently we've never 
> had this error on before.  So it turns out that on BSD we were calling 
> pthread_sigmask() without ever having #included a declaration.  Here's the 
> failure: http://tt.taptinder.org/cmdinfo/72837  The fix: Add an include on 
> pthread.h, and all is happy.
>
> So here's hoping that these more stringent compile settings prevent more bugs 
> in the future, catching them as compile failures rather than having weird 
> stuff turn up when they build incorrectly.
>
> Thanks,
> xoxo,
> Andy
>
> --
> Andy Lester => [email protected] => www.petdance.com => AIM:petdance
>
> _______________________________________________
> http://lists.parrot.org/mailman/listinfo/parrot-dev



-- 
Jonathan "Duke" Leto <[email protected]>
Leto Labs LLC
209.691.DUKE // http://labs.leto.net
NOTE: Personal email is only checked twice a day at 10am/2pm PST,
please call/text for time-sensitive matters.
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev

Reply via email to