Re: Should &&/|| really be at the end of lines?

2017-02-18 Thread Kyle Lahnakoski
On 2017-02-16 18:21, Jean-Yves Avenard wrote: > > > On 17/02/17 00:17, Jeff Gilbert wrote: >> If there are so many parens that we require an editor to disambiguate >> them, it's too dense. Add whitespace or decompose the expression until >> readable. >> > I'd love to know how adding any whitespac

Re: Intent to remove: support for installing multiple xpis simultaneously

2017-02-18 Thread Kris Maglione
On Sat, Feb 18, 2017 at 05:40:32AM -0800, bird.freudent...@googlemail.com wrote: Unfortunately I'm using this approach to bundle my themes with an extension that extends capability to them. I'm wondering why to remove this feature at this point of development, since for Firefox 57 upwards XUL b

Re: Should &&/|| really be at the end of lines?

2017-02-18 Thread Eric Rescorla
On Sat, Feb 18, 2017 at 1:10 AM, Jean-Yves Avenard wrote: > > > On 17/02/17 23:18, gsquel...@mozilla.com wrote: > >> Hi again Nick, >> >> Someone made me realize that I didn't fully read your message, sorry for >> that. >> >> I now see that as well as &&/||, you have grepped for other operators,

Re: Should &&/|| really be at the end of lines?

2017-02-18 Thread Eric Rescorla
On Fri, Feb 17, 2017 at 4:24 PM, ISHIKAWA,chiaki wrote: > > Point 5: We should set up a "Flag Day" to convert the source tree into the > official format THAT IS SUPPORTED by the mechanical converter/formater, and > change the source code in one sweep. > This seems like it places an enormous amou

Re: Should &&/|| really be at the end of lines?

2017-02-18 Thread Michael Froman
> On Feb 17, 2017, at 6:24 PM, ISHIKAWA,chiaki wrote: > > Point 2: > I prefer all the operators including "&&" and "||" > at the beginning since such a format makes the tree-like structure of > multi-line easier to understand and edit, too. > Adding a condition or removing a condition is much e

Re: Intent to remove: support for installing multiple xpis simultaneously

2017-02-18 Thread bird . freudenthal
Unfortunately I'm using this approach to bundle my themes with an extension that extends capability to them. I'm wondering why to remove this feature at this point of development, since for Firefox 57 upwards XUL based addons will not work anymore. ___

Re: Should &&/|| really be at the end of lines?

2017-02-18 Thread Jean-Yves Avenard
On 17/02/17 23:18, gsquel...@mozilla.com wrote: Hi again Nick, Someone made me realize that I didn't fully read your message, sorry for that. I now see that as well as &&/||, you have grepped for other operators, and shown that the overwhelming usage is to put all of them at the end of lines