[Development] QtBase WIP branch request

[Morten Sorvig]

Hi,

We’re working on an update to the macOS/Cocoa platform plugin,
and I would like to request a WIP branch where the changes can
be finalized:

   wip/remac

Thanks!
Morten


___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] bugreports.qt.io: unplanned interruption

[Robert Löhning]

Hi,

in the past hour loads of reports were created on bugreports.qt.io which
did not even attempt providing meaningful data. Since blocking single
users did not help, we decided to take the server offline to investigate
the situation. It will be back as soon as we found a way to protect the
server from this. We apologize for the inconvenience.

Best Regards,
Robert Löhning
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] [closed] Using semicolons in JS (QML)

[Kai Koehne]

Hi,

Alright, to close this thread: It seems the majority agrees that using 
semicolons after JS statement inside a Javascript {} block is a good idea. The 
suggestion is to follow this in new code. Personally, I will point out missing 
; as defects in reviews.

Regards

Kai

> -Original Message-
> From: Development [mailto:development-bounces+kai.koehne=qt.io@qt-
> project.org] On Behalf Of Viktor Engelmann
> Sent: Tuesday, October 04, 2016 3:51 PM
> To: development@qt-project.org
> Subject: Re: [Development] Using semicolons in JS (QML)
> 
> Am 30.09.2016 um 17:43 schrieb Shawn Rutledge:
> 
> 
>   Back in Nokia times it was said that we shouldn't use semicolons,
> because it would speed up the parsing [...]
> 
> 
> As someone who has written countless parsers, I *highly* doubt that this is
> actually true. Indenting with tabs was also believed to be *much* slower
> than indenting with spaces (which makes absolutely no sense), and that
> measurement result turned out to be caused by a bug in firebird. I bet this is
> also just an urban legend. Someone probably thought "hey - one less
> character to read - must be faster to load", but as André pointed out, the
> error recovery will most likely cost more than what you save. Unless if the
> behavior is baked into the LR(1) state-graph maybe.
> 
> Also I don't think it is good style to write code that doesn't conform to the
> actual language, just because *most* parsers correctly *guess* what you
> meant *most* of the time (except in those pathological cases...). I think that
> you should *always* tell parsers *precisely* what you mean and don't rely
> on it's guessing ability. For reference: The Mariner 1 crash (which cost $80
> million) was supposedly caused by an error that could have been caught by
> static analysis at compile time, but was just "guessed away" wrongly.
> 
> 
> Anyhow, I believe that we have spent more time on this debate than will
> ever be saved by omitting semicolons.
> 
> 
> Viktor
> 
> 
> --
> 
> 
> 
> Viktor Engelmann
> Software Engineer
> 
> The Qt Company GmbH
> Rudower Chaussee 13
> D-12489 Berlin
> viktor.engelm...@qt.io 
> +49 151 26784521
> http://qt.io
> 
> Geschäftsführer: Mika Pälsi, Juha Varelius, Mika Harjuaho
> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg,
> HRB 144331 B
>  
>  
> 
> 
> 
> 
>  
> Qt World Summit 2016 | Pier 27, San Francisco, CA Experience Exponential
> Potential on October 18-20
> www.qtworldsummit.com 
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Managing branches of Qt's git modules

[Robert Löhning]

Am 30.09.2016 um 13:05 schrieb Sean Harmer:
> 
> 
> On 30/09/2016 11:57, Marc Mutz wrote:
>> On Friday 30 September 2016 12:39:20 Sean Harmer wrote:
>>> Hi,
>>>
>>> just a query as to how people do bulk checkouts of different branches
>>> when working with the Qt git modules. It would be nice to be able to use
>>> git submodule foreach ... but this is a problem because not all modules
>>> use the same branching scheme.
>>>
>>> So, what do people do to checkout all interesting modules to 5.7, 5.8,
>>> dev etc on Unix like systems and on Windows?
>>>
>>> On *nix systems I've been getting away with a simple bash for loop. But
>>> on windows I find this painful but maybe that's just my unfamiliarity
>>> with windows batch scripts.
>>
>> to speed up fetching:
>>
>>   git submdule foreach "git fetch --all &"
>>
>> for everything else there's the repo tool, though I have not gotten
>> around
>> to checking it out, since most of my work is in qtbase.
>>
>>   git checkout 
>>   git submodule update --rebase
> 
> Thanks! Somehow I'd missed knowing about the --rebase option.

Hi,

wouldn't that rebase the branches the submodules have currently checked
out onto the top of ?

Best Regards,
Robert

> 
>> doesn't do what you want?
> 
> Looks like it should.
> 
> Thanks,
> 
> Sean
> 

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development