DenkzeitWiki

Main /

Fluent Interfaces

DomainSpecificLanguages
Interfaces
OOP

• http://www.nealford.com/downloads/conferences/canonical/Neal_Ford-10_Ways_to_Improve_Your_Code-slides.pdf
  • http://www.nealford.com/mypastconferences.htm

fluent: objects are passed through a chain of method-invokatios:

 Car.describeAs().box().wheels(4)

e.g. mutators return this.

• http://www.martinfowler.com/bliki/FluentInterface.html

The API is primarily designed to be readable and to flow. The price of this fluency is more effort, both in thinking and in the API construction itself. The simple API of constructor, setter, and addition methods is much easier to write. Coming up with a nice fluent API requires a good bit of thought.

Building a fluent API like this leads to some unusual API habits. One of the most obvious ones are setters that return a value.

• http://en.wikipedia.org/wiki/Fluent_interface