On Mon, May 17, 2010 at 4:07 PM, David Herman dher...@mozilla.com wrote:
[snip] For example, consider:
module M = load http://example.com/foo.js;;
module N = load http://example.com/foo.js;;
These two modules are loaded from the exact same MRL, but the module system
treats them as
On Wed, May 19, 2010 at 2:59 AM, Kevin Curtis kevinc1...@gmail.com wrote:
For the following scenario:
script
module ModA = http://acme.com/moda.js;;
module ModB = http://acme.com/modb.js;;
... source
/script
Both ModA and ModB use a utility module - that is the moda.js and
modb.js files
That's surprising. Within a moduleloader I would have thought that
same url meant the same static module. Across moduleloaders maybe not.
The problem is defining same url. One option is that same means identical
string but then when http://example.com/foo.html says:
script
module A =
On May 18, 2010, at 6:12 PM, Allen Wirfs-Brock wrote:
From: Kenneth Russell [mailto:k...@google.com]
Out of curiosity what are the implications of the word buffer?
The usage isn't absolute, but the term buffer is often used to for areas of
memory that hold transient data. Often data that
On Wed, May 19, 2010 at 3:04 PM, David Herman dher...@mozilla.com wrote:
If they want to share a utility module, you pull it out into a place that's
in scope for both ModA and ModB:
script
module ModUtils = load http://acme.com/modutils.js;;
module ModA = load
No variables or labels named implements, interface, let, package,
private, protected, public, static, or yield. (7.6.1.2)
Should be added to the Errata.
--
Cheers,
--MarkM
___
es-discuss mailing list
es-discuss@mozilla.org
I wonder if you can answer some of the metacircularity concerns by
defining the necessary parts using operational semantics, as in
http://jssec.net/semantics/sjs.pdf .
As an aside, has anyone actually attempted to formally document the
necessary kernel subset (apart from the above paper)?
--
Arjun Guha, Claudio Saftoiu and Shriram Krishnamurthi have a recent paper on
the topic:
http://www.cs.brown.edu/~sk/Publications/Papers/Published/gsk-essence-javascript/
Having had some experience with this question myself, let me just say that
while formalization is appealing, it's a
So both the moda.js and modb.js source files can contain (for example):
ModUtils.myfunc();
And can import the exports of ModUtils:
import ModUtils.myfunc;
myfunc();
Yes.
Is it correct that a module declaration within a script tag only has
scope within that script tag?
No, each script
I don't agree with this. Two of us formalized, implemented, and tested
that paper in a month. That is hardly time-consuming, and it's not
very subtle since we have test suites to test our formalization.
I brought up your paper because it's good work. I wasn't criticizing it. But
there's a
I brought up your paper because it's good work. I wasn't criticizing it. But
there's a difference between formalizing the operational core of a language
and writing a language standard.
To be clear, we formalized much more than an operational core of the
language. We've formalized a portion
You're still not understanding me. My cat could write an executable
implementation of the ES standard library. (Seriously, he's an amazing cat.)
The point is whether you can hit the right level of abstraction, the right
level of presentation, and the right level of specification-- neither over-
You're still not understanding me. My cat could write an executable
implementation of the ES standard library. (Seriously, he's an amazing cat.)
Hm. I was feeling silly at the time but that just came across mean. Sorry about
that. All I meant was that there's more to the spec than just
2010/5/19 David Herman dher...@mozilla.com:
You're still not understanding me. My cat could write an executable
implementation of the ES standard library. (Seriously, he's an amazing cat.)
Hm. I was feeling silly at the time but that just came across mean. Sorry
about that. All I meant was
d) If you're serious about suggesting lambda-JS as a basis (or starting
point, anyway) for future editions of ECMA-262, may I make a suggestion? Do a
proof-of-concept by taking the ES5 document and rewriting some of it in your
suggested style.
If I understand your suggestion right, this is
15 matches
Mail list logo
