Mozilla used to support something like this, it is being removed in Firefox 12, but perhaps the implementation can give you ideas.
https://developer.mozilla.org/en/Sharp_variables_in_JavaScript Wes On 5 March 2012 07:49, Andreas Rossberg <[email protected]> wrote: > On 5 March 2012 13:35, 程劭非 <[email protected]> wrote: > > { > > a: path(/a2), // yes, path(/a2) is a object > > a2: {c: 1, d: path(../b/d)}, // no, path(/b) is a path itself you > will > > get undefined here. > > b: path(/b2), //yes, path(/b2) is a object > > b2: {c: path(../a/c), d: 2}, // no path(../a) is a path itself you > will > > get undefined here. > > } > > > > In general, I mean a path will never refer to a object specified by a > path. > > Why? And anyway, what about: > > { > a: {c: 1, d: path(../b/d)}, > b: {c: path(../a/c), d: 2}, > } > > You still need deep dependency analysis. > > /Andreas > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss > -- Wesley W. Garland Director, Product Development PageMail, Inc. +1 613 542 2787 x 102
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
