On Sep 13, 2015 7:46 PM, "François Laupretre" <franc...@php.net> wrote: > > Le 13/09/2015 04:14, Sean DuBois a écrit : >> >> That sounds good to me! >> >> That would double build times though, is that going to be a concern? >> This won't hurt development time though, since you would dev in zstrict, >> and then switch to non-zstrict when running/testing? > > > Why would it double build times ? This is an optional tool, developers will run a zstrict build when they want to check their code against API 'best practices'. Some will do it more often than others, but that's their choice. Some ext devs will probably never use it, that's their decision.
> The only constraint will be for core developers. If travis runs in zstrict mode, every non-zstrict code will cause it to fail. So, core changes will need to be 'strict'. That's why this decision needs a vote. The more I think about it the more I think it should be part of the code quality analysis process, like static analyzers and the likes. Maybe a llvm plug-in or we'll configured options for existing analyzers (like with VC) Optional build options may not achieve what this proposal does. Except if we enforce it.
