Jasvir Nagra wrote:
According to your proposal, one.js is doing in essence a text inclusion of the
contents of two.js and as a result is susceptible to the problems unhygienic
macro expansion suffers.
I have been thinking about similar concerns, but, as the proposal mentions
separate
zero.js:
module One = load 'one.js';
module Drawing = load 'gun.js';
module JQ = load 'jquery.js';
one.js:
import JQ;
module Two = load 'two.js';
two.js:
import JQ;
import Drawing;
Drawing.draw();
The module of concern to us is one.js. According to your proposal, one.js is
Jasvir Nagra
http://www.cs.auckland.ac.nz/~jas
On Mon, May 24, 2010 at 6:21 AM, Mike Wilson mike...@hotmail.com wrote:
Jasvir Nagra wrote:
According to your proposal, one.js is doing in essence a text inclusion
of the contents of two.js and as a result is susceptible to the
problems
2010/5/24 David Herman dher...@mozilla.com
zero.js:
module One = load 'one.js';
module Drawing = load 'gun.js';
module JQ = load 'jquery.js';
one.js:
import JQ;
module Two = load 'two.js';
two.js:
import JQ;
import Drawing;
Drawing.draw();
The module of concern to us
Here are my notes for today's meeting.
Waldemar
Khronos: standard-setting consortium
Khronos standards are royalty-free (any essential patents must also be
royalty-free).
We'll have a joint meeting with them on Tuesday 3PM.
Khronos categories of members: adopters and implementors.
On Thu, May 20, 2010 at 4:50 PM, Waldemar Horwat walde...@google.com wrote:
Having unspecified endianness in the specification of TypedArrays seems like
a show-stopper to me. There are two alternatives here:
- If you do any I/O, you want the endianness to be specified. Sending data
from one
6 matches
Mail list logo
