W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2011

Re: Reviving E4X (H4E)?

From: Alex Russell <slightlyoff@google.com>
Date: Tue, 22 Nov 2011 15:37:06 +0000
Message-ID: <CANr5HFXPueL-1ov40WjE7FUyLXMC+hKj=LVvfjZVuJhZFGK5wg@mail.gmail.com>
To: Dominic Cooney <dominicc@chromium.org>
Cc: ☻Mike Samuel <msamuel@google.com>, Brendan Eich <brendan@mozilla.org>, Allen Wirfs-Brock <allen@wirfs-brock.com>, "Mark S. Miller" <erights@google.com>, Anne van Kesteren <annevk@opera.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Rafael Weinstein <rafaelw@google.com>, Adam Klein <adamk@google.com>, Erik Aarvidson <arv@google.com>
On Sun, Oct 23, 2011 at 5:22 AM, Dominic Cooney <dominicc@chromium.org> wrote:
> Quasis don’t provide a means for accurate error reporting, ie line and
> column numbers. (Since quasis seem designed for embedding DSLs, this seems
> like a shortcoming?)

What form would you expect this to take?

> The browser should provide a convenient way to create DOM subtrees; it would
> be nice if errors in the tree structure were lifted into JavaScript errors.
> If there was some way around the namespace pollution problem, simply using
> function calls could work well:
> div({
>     style: 'background: yellow;',
>     onclick: function () { alert('world'); }
>   },
>   text('Hello...'));

Modules can actually get us around this. Hooray for ES.next!

> Dominic
>
> On Thu, Oct 20, 2011 at 6:16 AM, ☻Mike Samuel <msamuel@google.com> wrote:
>>
>> On Wed, Oct 19, 2011 at 16:11, Brendan Eich <brendan@mozilla.org> wrote:
>> > On Oct 19, 2011, at 1:55 PM, ☻Mike Samuel wrote:
>> >
>> >>> I love quasis and don't mind their hunchback-like name, but others say
>> >>> it is
>> >>> a scary unknown neologism. Can we have a better term?
>> >>> For the unprefixed `... ${...} ...` form we could say "string
>> >>> interpolation". That's a mouthful but it is a known phrase.
>> >>> Sorry to bikeshed the name! If that's the biggest problem (and it may
>> >>> be),
>> >>> well done to you and Mike.
>> >>> /be
>> >>
>> >> I'm happy with either "string interpolation" or "template".  I can't
>> >> find "template" in FutureReservedWord, but I thought it was in there.
>> >> If so it would be odd to have a language feature named "template" but
>> >> not have any relation to the future reserved word.
>> >
>> > No, template was never reserved -- not in Java, so not reserved by me in
>> > 1995, or in ES1 based on that. And we unreserved a bunch of Java's keywords
>> > in ES5. No C++ templates in sight.
>> >
>> > Does template carry too much other baggage (e.g. JQuery template
>> > plugins)? I don't know.
>>
>> The jquery function is such a chameleon that jquery`...` could
>> probably be made to work for a subset of jquery templates excluding
>> {{each}}.
>>
>>
>
>
Received on Tuesday, 22 November 2011 15:38:14 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:05 UTC