[Development] Future of QBS

Oswald Buddenhagen oswald.buddenhagen at qt.io
Tue Oct 17 17:31:45 CEST 2017

On Tue, Oct 17, 2017 at 05:23:17PM +0200, Ulf Hermann wrote:
> >> Exactly. The halting problem can be worked around pragmatically.
> > 
> > ... at the price of getting different build results based on CPU speed ...
> > 
> > Your fast desktop CPU crunches through the JS and you get a working
> > built, while my sucky laptop CPU does not and the build fails for me.
> A simple timeout may be a bit too pragmatic, but you could count the
> JS instructions executed.
you guys are discussing the locks of a house without walls. when any
type of reasonable limiter needs to kick in, the your build system is
*broken*. that's a fatal error, not just a "different result", and you
need to rethink what you're doing.

More information about the Development mailing list