Marco van de Voort hat am 18. Oktober 2012 um 13:41
geschrieben:
> In our previous episode, Mattias Gaertner said:
> > > I disagree. To prevent any strange side-effects (undefined behaviour),
> > > the version check should happen as early as possible - before any
> > > compiling commences.
> >
>
Hi list,
I've been working on a listener for FPCUnit that writes test results to
a database.
I intend to use it to run e.g. database tests on my Jenkins CI server
whenever a new build is done. Therefore, the db is quite normalized in
order to limit used space.
I've included a flattening view that
In our previous episode, Mattias Gaertner said:
> > I disagree. To prevent any strange side-effects (undefined behaviour),
> > the version check should happen as early as possible - before any
> > compiling commences.
>
> I'm compiling fpc trunk with trunk/fixes/release since years. It works more
Graeme Geldenhuys hat am 17. Oktober 2012 um 17:05
geschrieben:
> On 2012-10-17 15:57, Vincent Snijders wrote:
> >
> > Alternatively, it could just be a warning. Then if it fails later, the
> > complete output will show the reason.
>
>
> I disagree. To prevent any strange side-effects (undefined
