> I like the idea of currying, it seems powerful and Perlish in many
> ways. However, I don't like the currying operator chosen, because
> of it's ugliness (IMHO), and its potential for ambiguity (human,
> not necessarily parser).
It's not an operator, it&#
Piers Cawley wrote:
> Graham Barr <[EMAIL PROTECTED]> writes:
> > On Fri, Aug 11, 2000 at 01:47:12PM +0100, Piers Cawley wrote:
> > > > /^_/
> > > >
> > > > What is that matching ?
> > >
> > > We've done this. It's matching a string that begins with '_'. Which is
> > > why, if you want to disamb
On Fri, Aug 11, 2000 at 02:52:32AM -0700, Nathan Wiger wrote:
> Mike-
>
> Jeremy's got a great explanation of this, which I'll paraphrase, but the
> discussion went through lots of iterations. Think of the ^ as a carat or
I only make this annoying and pedantic point because everyone I have
seen
On Fri, Aug 11, 2000 at 02:03:47PM +0100, Graham Barr wrote:
> On Fri, Aug 11, 2000 at 01:47:12PM +0100, Piers Cawley wrote:
> > > /^_/
> > >
> > > What is that matching ?
> >
> > We've done this. It's matching a string that begins with '_'. Which is
> > why, if you want to disambiguate you do
> "Graham" == Graham Barr <[EMAIL PROTECTED]> writes:
Graham> No that won't work either. That matches the string {_}
But that's arguably a DWIMmy thing, since {} is in the category of * +
and ?, which always need to be *after* something, and there's no
*something* here. I don't know how muc
Graham Barr <[EMAIL PROTECTED]> writes:
> On Fri, Aug 11, 2000 at 01:47:12PM +0100, Piers Cawley wrote:
> > > /^_/
> > >
> > > What is that matching ?
> >
> > We've done this. It's matching a string that begins with '_'. Which is
> > why, if you want to disambiguate you do /^{_}/ just like yo
On Fri, Aug 11, 2000 at 01:47:12PM +0100, Piers Cawley wrote:
> > /^_/
> >
> > What is that matching ?
>
> We've done this. It's matching a string that begins with '_'. Which is
> why, if you want to disambiguate you do /^{_}/ just like you do with
> variables.
No that won't work either. Tha
Graham Barr <[EMAIL PROTECTED]> writes:
> On Fri, Aug 11, 2000 at 02:52:32AM -0700, Nathan Wiger wrote:
> > Mike-
> >
> > Jeremy's got a great explanation of this, which I'll paraphrase, but the
> > discussion went through lots of iterations. Think of the ^ as a carat or
> > thumbtack, holding t
On Fri, Aug 11, 2000 at 02:52:32AM -0700, Nathan Wiger wrote:
> Mike-
>
> Jeremy's got a great explanation of this, which I'll paraphrase, but the
> discussion went through lots of iterations. Think of the ^ as a carat or
> thumbtack, holding the place for later variables. Then, consider the
> pa
On Fri, Aug 11, 2000 at 02:52:32AM -0700, Nathan Wiger wrote:
> Jeremy's got a great explanation of this, which I'll paraphrase, but the
> discussion went through lots of iterations. Think of the ^ as a carat or
> thumbtack, holding the place for later variables.
Yea, I ran across the description
r wrote:
>
> I like the idea of currying, it seems powerful and Perlish in many ways.
> However, I don't like the currying operator chosen, because of it's ugliness
> (IMHO), and its potential for ambiguity (human, not necessarily parser).
>
> So, here is my propos
I like the idea of currying, it seems powerful and Perlish in many ways.
However, I don't like the currying operator chosen, because of it's ugliness
(IMHO), and its potential for ambiguity (human, not necessarily parser).
So, here is my proposal to change the operator.
fr
12 matches
Mail list logo
