On Wednesday 02 November 2016 18:20:41 H.Merijn Brand wrote: > On Wed, 2 Nov 2016 18:03:52 +0100, pali@cpan.org wrote: > > On Wednesday 02 November 2016 09:32:56 demerphq wrote: > > > On 1 Nov 2016 7:37 p.m., <pali@cpan.org> wrote: > > > > But, question is: how to prevent to happen this situation again? > > > > Compile errors are already handled by travis when making pull > > > > requests but looks like this is not enough... > > > > > > There are build options for gcc that will help you catch most of the > > > common patterns that break c89. > > > > It is possible to configure travis-ci for github encode repository to > > use it? Or do you have any other idea of automated tests (ideally for > > those platforms which are c89 only)? > > I can give you access to HP-UX 11.23/PA2 which has a C89 compiler (with > optional C99 modus) and GNU gcc. > > That is a slow box however and not suitable for automatic testing. Ok, that would help to test some "problematic" changes if compiles correctly and unit test passes.Thread Previous | Thread Next