Re: Should `use strict` be a valid strict pragma?

2015-02-05 Thread Andy Earnshaw
I think you're missing the point Leon is trying to make. He's saying that, in ES 6 we have a new way to write strings. In some ways, these more powerful strings may condition some people to use ` as their main string delimiter. An unsuspecting person may liken this to PHP's double quotes vs

Re: Should `use strict` be a valid strict pragma?

2015-02-05 Thread Allen Wirfs-Brock
On Feb 5, 2015, at 7:24 AM, Alex Kocharin wrote: Why is there two of them, not one? It was my invention, so take this as definitive... In 2008 (or maybe 7) when we were came up with the strings for mode directives idea, there was no obvious preference among JS programmers in their use of

Re: Should `use strict` be a valid strict pragma?

2015-02-05 Thread Steve Fink
On 02/05/2015 05:12 AM, Andy Earnshaw wrote: I think you're missing the point Leon is trying to make. He's saying that, in ES 6 we have a new way to write strings. In some ways, these more powerful strings may condition some people to use ` as their main string delimiter. An unsuspecting

Re: Should `use strict` be a valid strict pragma?

2015-02-05 Thread Axel Rauschmayer
Also: given that modules are implicitly strict, you will hardly ever use the strict directive in ES6. On 05 Feb 2015, at 20:20, Steve Fink sph...@gmail.com wrote: On 02/05/2015 05:12 AM, Andy Earnshaw wrote: I think you're missing the point Leon is trying to make. He's saying that, in ES

Re: Should `use strict` be a valid strict pragma?

2015-02-05 Thread Alex Kocharin
 Why is there two of them, not one?  05.02.2015, 18:06, "Frankie Bagnardi" f.bagna...@gmail.com:I think any issues with that are imagined.  Languages have rules, and of the people who both know what 'use strict' does and are using es6 syntax, they're very unlikely to make the mistake. I don't see

Re: Should `use strict` be a valid strict pragma?

2015-02-05 Thread Frankie Bagnardi
I think any issues with that are imagined. Languages have rules, and of the people who both know what 'use strict' does and are using es6 syntax, they're very unlikely to make the mistake. I don't see people using template literals for arbitrary strings... it could happen but it probably won't.

Re: Should `use strict` be a valid strict pragma?

2015-02-05 Thread Mathias Bynens
On 5 Feb 2015, at 11:04, Leon Arnott leonarn...@gmail.com wrote: Well, that isn't quite the full story - if it were just a case of pragmas having to use something, anything, that could pass ES3 engines, then there wouldn't necessarily be two otherwise-redundant forms of the syntax - `use

Re: Should `use strict` be a valid strict pragma?

2015-02-05 Thread Leon Arnott
Well, that isn't quite the full story - if it were just a case of pragmas having to use something, anything, that could pass ES3 engines, then there wouldn't necessarily be two otherwise-redundant forms of the syntax - `use strict` and `'use strict'`. The reason those exist is to save the author

Re: Should `use strict` be a valid strict pragma?

2015-02-05 Thread Andy Earnshaw
On 5 Feb 2015 15:06, Frankie Bagnardi f.bagna...@gmail.com wrote: I think any issues with that are imagined. Languages have rules, and of the people who both know what 'use strict' does and are using es6 syntax, they're very unlikely to make the mistake. Sure, it's theoretical at this point

Should `use strict` be a valid strict pragma?

2015-02-04 Thread Leon Arnott
Given that `use strict` and `'use strict'` are both valid strict pragmas, should `` `use strict` `` in the same position also be regarded as a valid strict pragma? Against: * Backtick strings aren't really strings, but a kind of string-related function call, and thus are more complex than the

Re: Should `use strict` be a valid strict pragma?

2015-02-04 Thread Mark S. Miller
No it should not. use string and 'use strict' are specially recognized syntax. The *only* reason that they reuse the syntax of expression statements, rather than being, for example, use strict; without the quotes, is so this pragma would be ignored on older pre-ES5 browsers without causing