. Granted, I've never seen
this pattern used in production code except incidentally, but it's a
guarantee that ES3.0 does have nonetheless and I could see myself
using it if I really wanted to protect an object's prototype from
being modified.
--
David liorean Andersson
://www.ecmascript.org/es4/spec/incompatibilities.pdf
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
On 25/06/2008, liorean [EMAIL PROTECTED] wrote:
Also, while String objects are created as temporaries when looking up
a property on a string, how many of those properties or methods
actually return a String object? The only situation I can think of off
the top of my head where you're going
is the only browser that doesn't use
insertion order enumeration.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
for each
such case. (If using the form operator [no newlines here] ident,
that would be a safe way to do it since all code looking like that
cause a syntax error in ES3.) I don't know if that's a good or bad
idea though.
--
David liorean Andersson
___
Es4
, for example
by prohibiting adding new operators and keywords.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
for that particular name or a catch-all,
now, that's where this issue arises.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
2008/5/14 Mike Samuel [EMAIL PROTECTED]:
Ok. So it's a content-type which is not a mime-type even though it looks
like one?
Is there a separate recommendation that defines a mime-type for ecmascript?
uri:http://www.ietf.org/rfc/rfc4329.txt
--
David liorean Andersson
world of ES3, I expect.
Or one could consider an ES3 property as a getter/setter pair, if one wished.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
the scoping to function
level since all browser hosted implementations currently guarantee use
even after the block has exited.
[1] uri:https://mail.mozilla.org/pipermail/es4-discuss/2007-March/000483.html
[2] uri:https://mail.mozilla.org/pipermail/es4-discuss/2007-March/000495.html
--
David liorean
namespace lookups too,
however.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
()...,
get *: function(propname)...,
set *: function(propname, value)...,
...
};
The brackets for syntax would from what I can tell work here, since
they are syntax errors in ES3. Or using some double keyword syntax I
guess.
--
David liorean Andersson
the public feature specs drafts are here:
uri:http://wiki.ecmascript.org/doku.php?id=features_specs:feature_specs
Lars has posted some more for review here on es4-discuss though.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss
mechanisms in ES4 (but not in ES3.1 obviously)
Good to hear, because I still want to see something that can be used
in object literals and property declarations.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https
that only makes sence on elements
and not on any other nodes - element-rooted instead of
subtree-only-but-document-rooted queries. (I don't see any real
benefit from such an interface though, but I've seen the idea
mentioned on the mailing lists.)
--
David liorean Andersson
Oops, don't know how I ended up sending that to this mailing list - it
was intended for the WebAPI WG list...
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
a specific slice syntax in ES4, but the slice
functionality itself is ES3 compatible.)
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
).
And near the end of the document you have
/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/p/div
Slightly broken conversion tool?
--
David liorean Andersson
___
Es4
it appears to be GMail's fault.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
into the page using DOM;
javascript written directly into the page using innerHTML?
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
used it on, however, so
I can't look it up.)
I recall there was some engine that used the name lineNo for that
(together with a property for getting the column number I think,
though I can't recall the name). There was also some engine using the
name source for the file name.
--
David liorean
On 06/03/2008, liorean [EMAIL PROTECTED] wrote:
(Hmm. Were there any proposal for adding a any-includes-newline flag
or a any-including-newlines escape instead of the [\s\S] cludge? If
not, is \A)
Never finished that sentence it seems. It should have run:
If not, is \A or some similar
,
and for the use case of not having to escape singly quoted delimiters
in the string, what we have is good enough. I think we should keep it
as-is.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org
every backslash located inside the string.
Seems so to me.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
On Feb 18, 2008 1:17 PM, liorean [EMAIL PROTECTED] wrote:
Basically the idea was along the lines of investigating the effects of
removing GetValue usage from those productions whose semantics just
pass values through (such as all the shortcut evaluation operators,
parenthesised
On Feb 18, 2008 1:17 PM, liorean [EMAIL PROTECTED] wrote:
Basically the idea was along the lines of investigating the effects of
removing GetValue usage from those productions whose semantics just
pass values through (such as all the shortcut evaluation operators,
parenthesised
, nor do I know of any definition of greedy/lazy
algorithms as opposed to greedy/lazy quantifiers in regex or grammars.
I've got no formal CS education though, so I've not read that much of
the literature...
--
David liorean Andersson
___
Es4-discuss mailing
-within-labelled-statement case, IIRC.
In other words, to do a full set of tests one need to try both the
statement-list wrapped versions and the plain function declaration
versions, because they may have differing results.
--
David liorean Andersson
to an end at the right curly brace.
/be
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
ImplicitTailCallElimination=false;, leaving the default
behaviour for implicit TCE up to the implementation? Or would that be
three ways too many to handle it?
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https
up to the engine
implementors.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
compilation unit.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
desired, judging from real-world problems.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
, and not on the inside scope at all. This means a dissociated
function object from a function declaration will no longer be able to
use the original name as a reference to itself.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https
that it merits its own operator syntax.
Seems like an innocent enough extension to me, and for some of the
uses, it should definitely allow engine to perform it faster than if
the developers had to code the equivalent functionality using only
ES3.
--
David liorean Andersson
,
there's likely a significant risk that changing to this method could break
some
existing ECMAScript.
That's really serious breakage - books, tutorials, references and real
world code all take for granted that halves alway round up.
--
David liorean Andersson
side.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
language isn't important, what's important is the fact it's
pretty much entirely additional features that were lacking in the
predecessor or added orthogonal mechanisms that makes things possible
in the engine that were not possible before.
--
David liorean Andersson
, as well as other syntax
additions, it's going to be one tiny part of an entire new domain to
learn.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
On Tue, 2007-10-23 at 14:58 +0200, liorean wrote:
It's there to prevent the grammar from being ambiguous. function,
let and { have different meaning in statement context from
expression context. If the ExpressionStatement construct allowed them,
then they would be ambigous in statement
; instead of
representing an empty regular expression literal, the characters //
start a single-line comment. To specify an empty regular expression,
use /(?:)/.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https
in one case, and that would be if you actually
used the fall through mechanism. If you don't fall through, it's just
bloat without any gain.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4
serialize
such an array.
It cannot be serialised using JSON/ES3 literal syntax. Not if you want
to retain both the array-ness and the properties with non-array-ish
names.
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https
On 23/09/2007, Garrett Smith [EMAIL PROTECTED] wrote:
2. (new function(){}).constructor should be Function.
On Sep 23, 2007, at 8:59 AM, liorean wrote:
I agree. And in ES3 it is, unless the function either:
On 23/09/2007, Brendan Eich [EMAIL PROTECTED] wrote:
No:
js (new function
be on the object instance *created*
by the function.
On 9/23/07, liorean [EMAIL PROTECTED] wrote:
That argument I agree with. It should be on the instance and not the
prototype.
On 23/09/2007, Garrett Smith [EMAIL PROTECTED] wrote:
Which is different from the way built ins work, but seems OK
On 9/13/07, liorean [EMAIL PROTECTED] wrote:
That the spec doesn't match expectations and that there are behaviours
that do make sense to replace it with, coupled with the fact there
seems to be no obvious compatibility problem with changing it
(otherwise JScript and JavaScriptCore surely
construct)?
2. Can (?P=varname) refer to a lexical variable varname from a
containing scope, or just to groups within the regex itself?
3. If it can refer to a variable in a containing scope, what
constraints are put on the variable type, what conversions are made,
etc?
--
David liorean Andersson
, the undefined really means a match with the empty string thing
again. I should have known...
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
Ah, just the answers I wanted to hear:)
--
David liorean Andersson
___
Es4-discuss mailing list
Es4-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es4-discuss
Peter Hall wrote:
type B = {b:Self};
On 14/08/07, Cormac Flanagan [EMAIL PROTECTED] wrote:
Yes, I think this should be fine.
I'm all for allowing recursive structural types e.g. for use as binary
trees or linked lists.
type BinTree = {sin:Self, dx:Self, value:*};
--
David liorean
52 matches
Mail list logo