Re: String.prototype.repeat

2011-03-23 Thread David Bruant
Le 22/03/2011 22:29, Peter van der Zee a écrit : On Tue, Mar 22, 2011 at 2:39 AM, Dmitry A. Soshnikov dmitry.soshni...@gmail.com mailto:dmitry.soshni...@gmail.com wrote: On 22.03.2011 23:42, David Bruant wrote: Hi, About the string_repeat strawman

Re: Standardizing out-of-memory and stack-depth-exceeded errors?

2011-03-23 Thread Juriy Zaytsev
On Tue, Mar 22, 2011 at 12:07 PM, Joshua Bell j...@lindenlab.com wrote: I was noodling with a (toy) compiler-to-JS for a (dead) language that supports error handlers for two boundary conditions - stack depth exceeded out of memory - and noticed that the relevant behavior in JS is not standard

Re: [Harmony proxies] Revisiting the forwarding proxy pattern

2011-03-23 Thread Tom Van Cutsem
Hi David, As I understand it, the difference between the two patterns you presented is not so much in using a full forwarding handler versus an own forwarding handler, but in the fact that you pass different initial prototypes. Consider: var p = Proxy.create(fullForwardingHandler(target),

Re: [Harmony proxies] Inheritance safe proxies (was: [Harmony proxies] Proxies, prototype chain and inheritance)

2011-03-23 Thread Tom Van Cutsem
Hi David, In one of the first discussion about proxies on this list, the question popped up on whether proxy handlers should implement inheritance (prototype chain walking) themselves, or whether the engine should take care of this, only allowing the handler to control the own layer. The

Re: [Harmony proxies] Proxies, prototype chain and inheritance

2011-03-23 Thread David Bruant
Le 22/03/2011 00:08, David Bruant a écrit : Hi, Proxies can be helpful to emulate multiple inheritance (http://journal.stuffwithstuff.com/2011/02/21/multiple-inheritance-in-javascript/). Long story short, with the get and set traps, you can emulate this multiple inheritance without having

Re: [Harmony proxies] Inheritance safe proxies

2011-03-23 Thread David Bruant
Le 23/03/2011 11:26, Tom Van Cutsem a écrit : Hi David, In one of the first discussion about proxies on this list, the question popped up on whether proxy handlers should implement inheritance (prototype chain walking) themselves, or whether the engine should take care of this, only allowing

Re: String.prototype.repeat

2011-03-23 Thread Dmitry A. Soshnikov
On 23.03.2011 0:18, David Bruant wrote: Le 22/03/2011 02:39, Dmitry A. Soshnikov a écrit : On 22.03.2011 23:42, David Bruant wrote: Hi, About the string_repeat strawman (http://wiki.ecmascript.org/doku.php?id=strawman:string_repeat), one alternative solution could be a two argument

March 22/23 notes

2011-03-23 Thread Waldemar Horwat
Here are my raw notes from the last couple days. Ask the GA for a way for non-members to sign software contribution agreements? Waldemar: Thinks this would be a hard sell in the GA. They'll be annoyed at increasing provisions for non-members to participate. Istvan: This should not be too

Re: Standardizing out-of-memory and stack-depth-exceeded errors?

2011-03-23 Thread Garrett Smith
On 3/22/11, Joshua Bell j...@lindenlab.com wrote: I was noodling with a (toy) compiler-to-JS for a (dead) language that supports error handlers for two boundary conditions - stack depth exceeded out of memory - and noticed that the relevant behavior in JS is not standard across browsers. Has

Re: Standardizing out-of-memory and stack-depth-exceeded errors?

2011-03-23 Thread Oliver Hunt
On Mar 23, 2011, at 6:21 PM, Garrett Smith wrote: The infinite recursion could be detected and reported early. Where does that happen? Does any engine report early for infinite recursion? Non-trivial infinite recursion can't be detected early, and it's the non-trivial cases that people miss

Re: Standardizing out-of-memory and stack-depth-exceeded errors?

2011-03-23 Thread Mike Shaver
On Wed, Mar 23, 2011 at 6:21 PM, Garrett Smith dhtmlkitc...@gmail.com wrote: javascript: alert(new InternalError(Got on tha inside, bitch!)); Hrm. seems odd to expose the constructor publicly. Necessary to permit instanceof testing, no? The infinite recursion could be detected and reported

Re: Standardizing out-of-memory and stack-depth-exceeded errors?

2011-03-23 Thread felix
On Wed, Mar 23, 2011 at 6:25 PM, Mike Shaver mike.sha...@gmail.com wrote: On Wed, Mar 23, 2011 at 6:21 PM, Garrett Smith dhtmlkitc...@gmail.com wrote: The infinite recursion could be detected and reported early. Where does that happen? Does any engine report early for infinite recursion? No

Re: Standardizing out-of-memory and stack-depth-exceeded errors?

2011-03-23 Thread Garrett Smith
On 3/23/11, Mike Shaver mike.sha...@gmail.com wrote: On Wed, Mar 23, 2011 at 6:21 PM, Garrett Smith dhtmlkitc...@gmail.com wrote: javascript: alert(new InternalError(Got on tha inside, bitch!)); Hrm. seems odd to expose the constructor publicly. Necessary to permit instanceof testing, no?

Re: Standardizing out-of-memory and stack-depth-exceeded errors?

2011-03-23 Thread Garrett Smith
Bad quoting made it confusing, but I was (am) right. Edited as intended below: On 3/23/11, Garrett Smith dhtmlkitc...@gmail.com wrote: On 3/23/11, Mike Shaver mike.sha...@gmail.com wrote: On Wed, Mar 23, 2011 at 6:21 PM, Garrett Smith dhtmlkitc...@gmail.com wrote: javascript: alert(new

Re: Standardizing out-of-memory and stack-depth-exceeded errors?

2011-03-23 Thread Garrett Smith
On 3/23/11, Mike Shaver mike.sha...@gmail.com wrote: On Wed, Mar 23, 2011 at 8:21 PM, Garrett Smith dhtmlkitc...@gmail.com wrote: Bad quoting made it confusing, but I was (am) right. Edited as intended below: On 3/23/11, Garrett Smith dhtmlkitc...@gmail.com wrote: On 3/23/11, Mike Shaver