Actually this is fixed in ToT WebKit, have closed the stale bug.
https://bugs.webkit.org/show_bug.cgi?id=56041
cheers,
G.
On Jun 5, 2011, at 5:04 PM, Juriy Zaytsev wrote:
>
>
> On Sun, Jun 5, 2011 at 5:30 PM, Brendan Eich wrote:
> On Jun 3, 2011, at 10:49 AM, Juriy Zaytsev wrote:
>
> > Chr
2011/6/6 Brendan Eich :
> Escapes are a pain, due to the double-backslash burden.
Yep. To fit into this kind of library, you could use a quasi syntax like
regexp`...`.ignoreSpaces().nonCapturingByDefault().build()
Not as pithy as flags, but extensible via
regexp.prototype.nonCapturingBy
Escapes are a pain, due to the double-backslash burden.
We really want quasis for this kind of extensibility. Quasis solve the
multiline problem too (I hope... :-).
/be
On Jun 6, 2011, at 9:52 AM, Mike Samuel wrote:
> 2011/6/3 Kyle Simpson :
>> I propose a /n flag for regular expressions, whic
2011/6/3 Kyle Simpson :
> I propose a /n flag for regular expressions, which would swap the default
> capturing/non-capturing behavior between ( ) and (?: ) operators (that is, (
> ) would not capture, and (?: ) would capture).
>
> The /n property would reflect on the RegExp object as `Noncapturing
On Sun, Jun 5, 2011 at 5:30 PM, Brendan Eich wrote:
> On Jun 3, 2011, at 10:49 AM, Juriy Zaytsev wrote:
>
> > Chrome (13) and Safari (5) tolerate "n". No error.
>
> Bugs filed?
>
WebKit bug — https://bugs.webkit.org/show_bug.cgi?id=41614
Seems to be stalled. cc'ing Oliver.
--
kangax
_
The point is to encourage people to write *more* well-thought-out proposals
than can fit in an email, not less. Hence Allen's suggestion of blogs,
websites, or github. If language design issues can be resolved in bursts of 140
characters then I think I will need to find a new line of work. ;)
D
On Jun 3, 2011, at 10:49 AM, Juriy Zaytsev wrote:
> Chrome (13) and Safari (5) tolerate "n". No error.
Bugs filed?
/be
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
On Jun 3, 2011, at 8:47 AM, Allen Wirfs-Brock wrote:
> I just wanted to add, that it's always wise to flesh out an idea by writing
> it up as a cohesive proposal. Don't let lack of non-member access to the
> TC39 wiki stop you from doing this. Write it up anyway. Then post it to
> your pe
On Fri, Jun 3, 2011 at 1:51 AM, Brendan Eich wrote:
> On Jun 2, 2011, at 10:49 PM, Brendan Eich wrote:
>
> > On Jun 2, 2011, at 10:46 PM, Kyle Simpson wrote:
> >
> >> I propose a /n flag for regular expressions, which would swap the
> default capturing/non-capturing behavior between ( ) and (?: )
On Thu, Jun 2, 2011 at 10:15 PM, Kyle Simpson wrote:
> With all due respect, it's a somewhat common occurrence on this list when
> someone brings up an idea that bears even a remote resemblance to an
> existing official strawman, the instinctual and rapid triage is to shoehorn
> the discussion in
I just wanted to add, that it's always wise to flesh out an idea by
writing it up as a cohesive proposal. Don't let lack of non-member access
to the TC39 wiki stop you from doing this. Write it up anyway. Then post
it to your personal blog, website, github, or anywhere else that you have
ac
I just wanted to add, that it's always wise to flesh out an idea by writing it
up as a cohesive proposal. Don't let lack of non-member access to the TC39
wiki stop you from doing this. Write it up anyway. Then post it to your
personal blog, website, github, or anywhere else that you have acc
The /n property would reflect on the RegExp object as `Noncapturing ==
true`.
Lowercase noncapturing, right?
Yeah.
--Kyle
___
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
On Jun 2, 2011, at 10:49 PM, Brendan Eich wrote:
> On Jun 2, 2011, at 10:46 PM, Kyle Simpson wrote:
>
>> I propose a /n flag for regular expressions, which would swap the default
>> capturing/non-capturing behavior between ( ) and (?: ) operators (that is, (
>> ) would not capture, and (?: ) wo
On Jun 2, 2011, at 10:46 PM, Kyle Simpson wrote:
> I propose a /n flag for regular expressions, which would swap the default
> capturing/non-capturing behavior between ( ) and (?: ) operators (that is, (
> ) would not capture, and (?: ) would capture).
I like it. No worries about the .NET somew
I propose a /n flag for regular expressions, which would swap the default
capturing/non-capturing behavior between ( ) and (?: ) operators (that is,
( ) would not capture, and (?: ) would capture).
The /n property would reflect on the RegExp object as `Noncapturing ==
true`.
Is there any p
On Jun 2, 2011, at 10:15 PM, Kyle Simpson wrote:
>>> So if a non-TC39 member wants to create suggestions and proposals and ideas
>>> for the community to discuss, am I to understand that not only this list,
>>> but also the wiki that this list so frequently references, are not really
>>> intend
So if a non-TC39 member wants to create suggestions and proposals and
ideas for the community to discuss, am I to understand that not only this
list, but also the wiki that this list so frequently references, are not
really intended for that?
I didn't say anything about this list. Discussion o
On 06/02/11 17:56, Kyle Simpson wrote:
Is it available for general public members to register for an account to create
strawman proposals for ES?
No, it's an Ecma TC39 resource. Ecma needs IPR handoff per its patent covenant
so this can't be a free-for-all, for better or worse.
So if a non-
On Jun 2, 2011, at 5:56 PM, Kyle Simpson wrote:
>>> Is it available for general public members to register for an account to
>>> create strawman proposals for ES?
>>
>> No, it's an Ecma TC39 resource. Ecma needs IPR handoff per its patent
>> covenant so this can't be a free-for-all, for better
Is it available for general public members to register for an account to
create strawman proposals for ES?
No, it's an Ecma TC39 resource. Ecma needs IPR handoff per its patent
covenant so this can't be a free-for-all, for better or worse.
So if a non-TC39 member wants to create suggestions a
On Jun 2, 2011, at 4:16 PM, Kyle Simpson wrote:
> Is it available for general public members to register for an account to
> create strawman proposals for ES?
No, it's an Ecma TC39 resource. Ecma needs IPR handoff per its patent covenant
so this can't be a free-for-all, for better or worse.
>
Is it available for general public members to register for an account to
create strawman proposals for ES?
In particular, I'd like to create two proposals for some future discussion:
1. a "n" (or "c") flag for regexp's, that reverses the default capturing
behavior of ( ) to be non-capturing by
23 matches
Mail list logo
