list-noob here - I hope this gets threaded ok.
One of the pieces of awkward ES specification terminology has been the use of
the word Program as the name for a global top-level StatementList.
This, I think is what (the noun) program should be reserved for.
A ES Program is commonly only a
One of the pieces of awkward ES specification terminology has been the use of
the word Program as the name for a global top-level StatementList. A ES
Program is commonly only a single fragment of what most of us commonly
think of as a program.
I agree.
I proposed that we replace Program
On Oct 10, 2012, at 4:20 PM, Rick Waldron waldron.r...@gmail.com wrote:
-1
Script might be the most common execution context, but there is more then
one of those to consider. I think Program is just the right amount of
neutral.
This doesn't address Allen's point, though, which is that a
On Wed, Oct 10, 2012 at 4:20 PM, Rick Waldron waldron.r...@gmail.com wrote:
...
Allen Wirfs-Brock wrote:
I proposed that we replace Program in this context with Script. This
is much less confusing and matches the most common manifestation of an ES
Program as an HTML script block.
+1 --
On 11 October 2012 17:49, John J Barton johnjbar...@johnjbarton.com wrote:
Script is not neutral but neither is Program plus it's just wrong.
The language needs a name for both the unit of compilation and the
assembly of those units. The latter is a program right? So the former
needs a
John J Barton wrote:
That is not my understanding, but I don't think it matters: that is an
implementation specific notion without consequence. Whether the
compiler treats all of the top level statements of ascript tag
individually or separately cannot influence the result.
No, this ignores
On Thu, Oct 11, 2012 at 11:03 AM, Brendan Eich bren...@mozilla.com wrote:
John J Barton wrote:
That is not my understanding, but I don't think it matters: that is an
implementation specific notion without consequence. Whether the
compiler treats all of the top level statements of ascript tag
John J Barton wrote:
On Thu, Oct 11, 2012 at 11:03 AM, Brendan Eichbren...@mozilla.com wrote:
John J Barton wrote:
That is not my understanding, but I don't think it matters: that is an
implementation specific notion without consequence. Whether the
compiler treats all of the top level
Allen Wirfs-Brock wrote:
I proposed that we replace Program in this context with Script.
This is much less confusing and matches the most common manifestation
of an ES Program as an HTML script block.
+1 -- it the term at least some engines use, and it makes more sense for
eval, or at least
+1 Tracuer uses 'Program' and that makes it too easy to forget that
the program consists of multiple Program-s
jjb
On Wed, Oct 10, 2012 at 11:56 AM, Brendan Eich bren...@mozilla.com wrote:
Allen Wirfs-Brock wrote:
I proposed that we replace Program in this context with Script. This
is
On Wednesday, October 10, 2012 at 6:14 PM, John J Barton wrote:
+1 Tracuer uses 'Program' and that makes it too easy to forget that
the program consists of multiple Program-s
jjb
On Wed, Oct 10, 2012 at 11:56 AM, Brendan Eich bren...@mozilla.com wrote:
Allen Wirfs-Brock wrote:
On Oct 10, 2012 4:20 PM, Rick Waldron waldron.r...@gmail.com wrote:
On Wednesday, October 10, 2012 at 6:14 PM, John J Barton wrote:
+1 Tracuer uses 'Program' and that makes it too easy to forget that
the program consists of multiple Program-s
jjb
On Wed, Oct 10, 2012 at 11:56 AM,
I'm tarting to work on the global scope/program/module level of the
specification.
One of the pieces of awkward ES specification terminology has been the use of
the word Program as the name for a global top-level StatementList. A ES
Program is commonly only a single fragment of what most of
13 matches
Mail list logo
