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. _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
- Re: [Development] Future of QBS Ulf Hermann
- Re: [Development] Future of QBS Konstantin Tokarev
- Re: [Development] Future of QBS Adam Treat
- Re: [Development] Future of QBS Konstantin Tokarev
- Re: [Development] Future of QBS Kevin Kofler
- Re: [Development] Future of QBS André Somers
- Re: [Development] Future of QBS Joerg Bornemann
- Re: [Development] Future of QBS Tobias Hunger
- Re: [Development] Future of QBS Ulf Hermann
- Re: [Development] Future of QBS Christian Kandeler
- Re: [Development] Future of QBS Oswald Buddenhagen
- Re: [Development] Future of QBS André Somers
- Re: [Development] Future of QBS Adam Treat
- Re: [Development] Future of QBS Konstantin Tokarev
- Re: [Development] Future of QBS Jake Petroules
- Re: [Development] Future of QBS jeandet
- Re: [Development] Future of QBS Konstantin Tokarev
- Re: [Development] Future of QBS Jake Petroules
- Re: [Development] Future of QBS Christian Gagneraud
- Re: [Development] Future of QBS Jake Petroules
- Re: [Development] Future of QBS Christian Gagneraud