G
gabriele renzi
Hi gurus and nubys,
lurking comp.lang.misc, I noticed this message:
http://tinyurl.com/2q8c7
and suddenly had the vision to have that in ruby too.
What I'm talking about is application of callable objects.
As of now we have to explicitly write:
callable.call arg1, arg2
and it feels ugly.
I was going to ask if we could have this:
callable arg1,arg2 # implicitly looks for #call
callable # the callable object
callable() # forces application with zero arguments
....
what's wrong with this?
PS
also, was'nt Marcin 'Qrczak' Kowalczyk on this list long time ago?
lurking comp.lang.misc, I noticed this message:
http://tinyurl.com/2q8c7
and suddenly had the vision to have that in ruby too.
What I'm talking about is application of callable objects.
As of now we have to explicitly write:
callable.call arg1, arg2
and it feels ugly.
I was going to ask if we could have this:
callable arg1,arg2 # implicitly looks for #call
callable # the callable object
callable() # forces application with zero arguments
....
what's wrong with this?
PS
also, was'nt Marcin 'Qrczak' Kowalczyk on this list long time ago?