Pure OO vs. Curried Syntax

So /prog/, I have looked around and I haven't been able to find any more-or-less pure OO languages with curried syntax. What gives?

It's not uncommon to see: object message message message

Where object message returns an object which accepts takes the next message, but what if the message is a method call that takes parameters? Instead of returning a curried object, you still get: object method(a,b) method(x,y), but never: object method a b method x y -- why is that?

>>9
What makes Object.method1(param1).method2(param2) so hard to read?  Even if you don't know exactly what it is doing, as long as you know how a single object uses a single method, you can easily imply that both methods act on the object in some order.
That's not necessarily a correct explanation but it is a logical conclusion.