BTW. Interesting to read what others have done in this area:
http://osteele.com/sources/javascript/functional/
http://ejohn.org/blog/partial-functions-in-javascript/
Cheers,
/Per
On Thu, Dec 18, 2008 at 9:32 PM, Per Cederberg wrote:
> Thanks for the clarification, Bob!
>
> Regarding the funct
Thanks for the clarification, Bob!
Regarding the functions in questions I think other names might be in
place, to avoid misleading interpretations. What we're really doing
here is attempting to patch the poor JavaScript syntax and/or standard
library for function calls (i.e. call, apply, argument
Hi all,
On Thu, Dec 18, 2008 at 16:07, Bob Ippolito wrote:
> I'm not a real big fan of currying in languages where it's not
> built-in. It's easy to make a mistake by calling a function with too
> few arguments and you get a harder to track down bug. It also doesn't
> work well with languages th
The difference between currying and partial application is that you
can call a curried function f with 1 argument that needs N arguments
and the return value is a function f_1 that needs N-1 arguments and
when called again with 1 argument will return a function f_2 that
takes N-2 arguments, etc. u
This is a WebKit (both Safari & Chrome) issue, since it handles
attributes more strictly than other browsers. I.e. 'selected' is not
an attribute on the HTML node, just a property. We try to work around
this in most cases by setting both the attribute and the property just
to be sure:
Hi Christoph,
On Thu, Dec 18, 2008 at 13:00, Christoph Zwerschke wrote:
> By the way, one (new) useful feature of Python's startswith is that you
> can also pass a tuple of substrings (prefixes) instead of only one. So
> maybe you can accept arrays as well.
Ah, nice - I didn't know about this f
Amit Mendapara schrieb:
> Again, I'm too, agree with Arner. Try to follow Python conventions as
> much as possible.
>
> startsWith => startswith
> endsWith => endswith
By the way, one (new) useful feature of Python's startswith is that you
can also pass a tuple of substrings (prefixes) inst
On Tue, Dec 16, 2008 at 3:47 PM, Eoghan wrote:
> 2. Modify the lookup by id convention to lookup by selector + map:
>connect('#my-ul li', 'onclick', func);
Yes, changing these lookups would break the current API. But it
wouldn't be impossible to create a migration path with decent
backwards
