Books I'd like to see

[Andrew Dalke]

Alex:
> I'm familiar with Ruby's claims, but, as methods/functions aren't really
> first-class objects there, I don't necessarily buy into them.

The claim, as I understand it, is that the method notation

  qwerty.abc(1,2,3);

sends the 'abc' message to 'qwerty', and they don't go along with
Python's approach that 'qwerty.abc' gets the method 'abc'.  Instead,
they say there's another way to ask for the method object,

  theMethod = qwerty.method("abc")
  theMethod.call(1,2,3)

What makes that not a first class object?

                    Andrew
                    dalke at dalkescientific.com