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 *
day, October 4, 2016 10:13:21 AM
To: Olivier Goffart
Cc: development@qt-project.org
Subject: Re: [Development] Using semicolons in JS (QML)
> On Oct 1, 2016, at 8:33 AM, Olivier Goffart wrote:
>
> On Freitag, 30. September 2016 15:43:57 CEST Shawn Rutledge wrote:
>> Back in Nokia
> On Oct 1, 2016, at 8:33 AM, Olivier Goffart wrote:
>
> On Freitag, 30. September 2016 15:43:57 CEST Shawn Rutledge wrote:
>> Back in Nokia times it was said that we shouldn't use semicolons, because it
>> would speed up the parsing and reduce the size of resources slightly. [...]
>
> Back in
> On 30 Sep 2016, at 23:57, Robin Burchell wrote:
>
> For Qt, while I would like to see one or the other picked and followed
> for consistency's sake, I'm not sure it would be a useful investment of
> your time to try to enforce a particular semicolon-style without tooling
> enforcement, as it s
> -Original Message-
> From: Development [mailto:development-bounces+mitch.curtis=qt.io@qt-
> project.org] On Behalf Of Robin Burchell
> Sent: Friday, 30 September 2016 11:57 PM
> To: development@qt-project.org
> Subject: Re: [Development] Using semicolons in JS (QML)
&
i
Koehne
Sent: Friday, 30 September 2016 11:00 PM
To: Shawn Rutledge ; development@qt-project.org
Subject: Re: [Development] Using semicolons in JS (QML)
>> To make a proposal: Let's use semicolons in imperative JS parts of QML in
>> our examples and documentation
>
> Ba
On Freitag, 30. September 2016 15:43:57 CEST Shawn Rutledge wrote:
> Back in Nokia times it was said that we shouldn't use semicolons, because it
> would speed up the parsing and reduce the size of resources slightly. [...]
Back in Nokia times, someone was reviewing a patch and made a comment that
On Fri, Sep 30, 2016 at 4:43 PM, Shawn Rutledge wrote:
> On 30 Sep 2016, at 14:19, Kai Koehne wrote:
>> To make a proposal: Let’s use semicolons in imperative JS parts of QML in
>> our examples and documentation
>
> Back in Nokia times it was said that we shouldn't use semicolons, because it
>
On Fri, Sep 30, 2016, at 11:00 PM, Kai Koehne wrote:
> Interesting. Indeed, I wouldn't have thought it makes any measurable
> difference. IIRC we had a qml mimizer once, I guess this is still around?
tools/qmlmin in qtdeclarative
> It's certainly not that important to me that I will spend a day o
On Fri, Sep 30, 2016 at 03:43:57PM +, Shawn Rutledge wrote:
> On 30 Sep 2016, at 14:19, Kai Koehne wrote:
> > To make a proposal: Let’s use semicolons in imperative JS parts of QML in
> > our examples and documentation
>
> Back in Nokia times it was said that we shouldn't use semicolons, beca
ai
From: Development on
behalf of Shawn Rutledge
Sent: Friday, September 30, 2016 5:43:57 PM
To: development@qt-project.org
Subject: Re: [Development] Using semicolons in JS (QML)
On 30 Sep 2016, at 14:19, Kai Koehne wrote:
> To make a proposal: Let’s use semicolon
On 30 Sep 2016, at 14:19, Kai Koehne wrote:
> To make a proposal: Let’s use semicolons in imperative JS parts of QML in our
> examples and documentation
Back in Nokia times it was said that we shouldn't use semicolons, because it
would speed up the parsing and reduce the size of resources sligh
On Freitag, 30. September 2016 12:19:09 CEST Kai Koehne wrote:
> Hi,
>
> It’s Friday, so time for some bikeshedding ;)
>
>
> As you might know, the semicolon as a statement separator in JavaScript is
> optional.
Technicly, that's more complicated than that. The semicolons are mandatory.
But i
I am also already abiding to the practice of using semicolons between curly
braces and no semicolons for simple bindings.
Marco Piccolino
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
FWIW, in unity8 (reasonably big QML application) we agreed to not use
semicolons for declarative code unless you really want to write some
things into a single line and need them, but always use semicolons for
imperative code.
This has served us very well over the past years, seems consistent and
I personally use semicolons always when {} is incorporated. And {} I'm using
when its more than a single statement.
Beste Grüße / Best regards,
Alexander Nassian, bitshift dynamics GmbH___
Development mailing list
Development@qt-project.org
http://lists
4. If the semicolon makes you feel angry, feel free to arbitrarily add (or
remove) semicolons to make you feel better.
;;
2016-09-30 14:19 GMT+02:00 Kai Koehne :
> To make a proposal: Let’s use semicolons in imperative JS parts of QML in
> our examples and documentation.
>
> Apart from being on the safe side regarding some pathological cases, it
> also makes the difference between declarative QML bindings and
>
> im
I think that would be fine to require semicolons everywhere except last
statement (and if there is single statement in the binding, no semi-colons are
needed at all)
I'm fine with having no semicolon on single statement bindings or signal
handlers that also don't require a pair of curly bra
30.09.2016, 15:19, "Kai Koehne" :
> Hi,
>
> It’s Friday, so time for some bikeshedding ;)
>
> As you might know, the semicolon as a statement separator in JavaScript is
> optional. That is, most of the time you can just separate commands
>
> by newlines. There are a few pathological cases [1] th
Hi,
It’s Friday, so time for some bikeshedding ;)
As you might know, the semicolon as a statement separator in JavaScript is
optional. That is, most of the time you can just separate commands
by newlines. There are a few pathological cases [1] though where a semicolon is
needed. It seems the J
21 matches
Mail list logo
