| let x = "outer"; | |
| let obj = { x: "object" }; | |
| let res; | |
| with ( obj ) { | |
| res = { x }; | |
| // per 12.1.2.1, short-hand propdef must statically bind to a declarative env record binding | |
| } | |
| assert( res.x === "outer" ); // is this true? |
| 1. Let O be the result of calling ToObject passing the this value as the argument. | |
| 2. ReturnIfAbrupt(O). | |
| 3. Let lenVal be the result of Get(O, "length"). | |
| 4. Let len be ToLength(lenVal). | |
| 5. ReturnIfAbrupt(len). | |
| 6. Let middle be floor(len/2). | |
| 7. Let lower be 0. | |
| 8. Repeat, while lower ≠ middle | |
| a. Let upper be len−lower−1. | |
| b. Let upperP be ToString(upper). |
This document attempts to exhaustively explore the syntax of the ES6 Modules proposal.
Module syntax is valid only in module code. Script code is not
module code, so existing script tags cannot contain module code. The
intention is that HTML will add a module tag and a default module
loader that is used to fetch and instantiate module code. See
dherman/web-modules for more
info on progress specifying the behavior of these components.
| <!doctype html> | |
| <meta charset="utf-8"> | |
| <script> | |
| var Platform = {flags: {shadow: 'native'}}; | |
| </script> | |
| <script src="http://cdnjs.cloudflare.com/ajax/libs/polymer/0.1.4/platform.js"></script> | |
| <script> | |
| document.registerElement('x-a', { | |
| prototype: { | |
| __proto__: HTMLElement.prototype, |
Generally useful links:
| function assertOrderOfOps(act, exp) { | |
| exp.forEach(function(e, i) { | |
| if(act[i][0] !== exp[i][0] || act[i][1] !== exp[i][1]) { | |
| throw new Error('Expected operation ' + i + ' to be ' + exp[i] + ' but was ' + act[i]); | |
| } | |
| }); | |
| if(act.length > exp.length) { | |
| throw new Error('More operations than expected: ' + | |
| act.slice(exp.length).map(function(e) { return e[0] }) |
| var obj = { x: 1, y: 2 } | |
| for(var prop in obj) { | |
| console.log(prop); | |
| Object.defineProperty(obj, 'y', { enumerable: false }); | |
| } | |
| // IE logs x | |
| // Chrome/FF log x and y |
| 1. Purpose | |
| To develop HoNKit, a tool to manage mods and make them easy to use. | |
| 2. Administrative | |
| a. Vadi will administrate. This will include determining features included, when to release, determining goals and deliverables. | |
| b. Launchpad will host the code. A website will be administered by Dub. Documentation will be in a /doc dir. | |
| 3. Features |
| Another test paste I guess |