Re: Case insensitive String startsWith, contains, endsWith, replaceAll method

2013-02-16 Thread Rick Waldron
On Saturday, February 16, 2013, David Bruant wrote: > Le 17/02/2013 00:58, Biju a écrit : > >> In most time when user want to search something in a text, he/she >> wants to do a case insensitive search. >> For example to filter items displayed in list on a page. >> Also on other applications, say

Re: Case insensitive String startsWith, contains, endsWith, replaceAll method

2013-02-16 Thread David Bruant
Le 17/02/2013 00:58, Biju a écrit : In most time when user want to search something in a text, he/she wants to do a case insensitive search. For example to filter items displayed in list on a page. Also on other applications, say any word processor, or in page search in Firefox, IE, Chrome etc.

Case insensitive String startsWith, contains, endsWith, replaceAll method

2013-02-16 Thread Biju
In most time when user want to search something in a text, he/she wants to do a case insensitive search. For example to filter items displayed in list on a page. Also on other applications, say any word processor, or in page search in Firefox, IE, Chrome etc. So can we make the default behavior of

Re: A case for removing the seal/freeze/isSealed/isFrozen traps

2013-02-16 Thread David Bruant
Le 16/02/2013 23:31, Allen Wirfs-Brock a écrit : Will this not just shift the current complexity someplace else? Well, it means that for 100% backwards compatibility, Object.isFrozen would have to be something like: 1. Let state = obj.[[GetIntegrity]](); 2 If state is "frozen" return true;

Re: A case for removing the seal/freeze/isSealed/isFrozen traps

2013-02-16 Thread Allen Wirfs-Brock
On Feb 14, 2013, at 1:14 AM, Tom Van Cutsem wrote: > 2013/2/14 Allen Wirfs-Brock > > On Feb 13, 2013, at 12:53 PM, David Bruant wrote: > >> Interesting. > >> So what would happen when calling Object.isFrozen on a proxy? Would >> Object.isFrozen/isSealed/isExtensible reach out directly to the

Re: A case for removing the seal/freeze/isSealed/isFrozen traps

2013-02-16 Thread Allen Wirfs-Brock
On Feb 14, 2013, at 11:46 AM, Andreas Rossberg wrote: > On 14 February 2013 01:05, Allen Wirfs-Brock wrote: >> Where "do without", means replaced with set/getIntegrity traps and objects >> have explicit internal state whose value is one of >> normal/non-extensible/sealed/frozen (and possibly)

Re: [].push wrt properties along the [[Prototype]] chain

2013-02-16 Thread Allen Wirfs-Brock
On Feb 16, 2013, at 11:57 AM, Mark S. Miller wrote: > Allen, by "put:", did you mean "set:"? > arrrggg. to much vacation. yes, of course, it should be "set" in which case the exception does occur as it should in FF. Allen > > On Sat, Feb 16, 2013 at 10:51 AM, Allen Wir

Re: [].push wrt properties along the [[Prototype]] chain

2013-02-16 Thread Mark S. Miller
Allen, by "put:", did you mean "set:"? On Sat, Feb 16, 2013 at 10:51 AM, Allen Wirfs-Brock wrote: > > On Feb 15, 2013, at 6:30 PM, Jeff Walden wrote: > > Consider: > > Object.defineProperty(Object.prototype, "0", { value: 17, writable: > false, configurable: false }); > [].push(42); > > Per ES

Re: [].push wrt properties along the [[Prototype]] chain

2013-02-16 Thread Allen Wirfs-Brock
On Feb 15, 2013, at 6:30 PM, Jeff Walden wrote: > Consider: > > Object.defineProperty(Object.prototype, "0", { value: 17, writable: false, > configurable: false }); > [].push(42); > > Per ES5, I think this is supposed to throw a TypeError. The push should be > setting property "0" with Thr