W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2013

Re: E4H compatible with string templates

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 14 Mar 2013 17:12:59 -0700
Message-ID: <CAAWBYDB5tKse3ndhRMD35P8JoqJ8M9jqxbj2X=nQLK6hrnLXuw@mail.gmail.com>
To: Brendan Eich <brendan@secure.meer.net>
Cc: Mike Samuel <mikesamuel@gmail.com>, Ian Hickson <ian@hixie.ch>, "public-script-coord@w3.org" <public-script-coord@w3.org>, Adam Barth <w3c@adambarth.com>
On Thu, Mar 14, 2013 at 4:57 PM, Brendan Eich <brendan@secure.meer.net> wrote:
> Depending on what goes in the ${...} holes, though, the failure might
> necessarily be runtime. Error is enough, and a sometimes-compile-time,
> other-times-runtime error can be worse. In my experience, anyway.

In Hixie's E4H proposal, the contents of the holes *never* causes an
error.  You can only put a hole as an attribute value or element text
contents (or just contents, if we also allow the hole's value to be
DOM).  These can't ever fail - you'll just stringify (or append, if
it's DOM).

Received on Friday, 15 March 2013 00:13:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:08 UTC