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?

pure OO language
wat

>>13
I've heard two different meanings for that phrase. Either
a) everything is an object
or
b) objects are immutable (pure in functional sense)
I'd assume that OP is referring to (a), but I don't think it would have any bearing on his question anyway