ansaurus

Question

Answer 1

+4 A:

EDIT:

a fluent interface (as first coined by Eric Evans and Martin Fowler) is a way of implementing an object oriented API in a way that aims to provide for more readable code.

A fluent interface is normally implemented by using method chaining to relay the instruction context of a subsequent call (but a fluent interface entails more than just method chaining).

bniwredyc 2010-04-13 05:17:19

I'm a bit skeptical about the relationship between "chaining" and "readability". I personally love chaining, because it's cool, and produces few lines of code... but is it really more readable when you have a big chain of events, than a sequence of operations where it's clearly defined what operation is being performed on what?

Mark 2010-04-13 06:05:05

@Mark: I agree. Method chaining isn't always more readable. I think readable method chaining is a part of the fluent interface style.

bniwredyc 2010-04-13 06:37:27

The point of method chaining (as used above) is that you can effectively use the language and the chained methods to implement a mini language, with the method calls taking the place of a lexer/parser. The other type of method chaining (`Foo.GetBar().GetBaz().GetQux().DoSomething()`) is often called a trainwreck, and is about as disastrous :)

kyoryu 2010-04-14 06:25:02

Answer 2

+1 A:

Chain of responsibility is more of a multiple class/object level pattern, where messages are passed down a hierarchy of objects, and each object can decide whether or not it can deal with the message or pass it on.

I think the pattern you show here is basically just a "Fluent Interface," like you said.

Andy White 2010-04-13 05:18:16

Just wanted to know, Fluent interface itself is a design pattern or it is a technique?

2010-04-13 05:23:46

I feel this is just a way to extend the concept of Method Chaining to the Interface level. That's it.

Amit 2010-04-13 05:44:36

Answer 3

+1 A:

I don't know that it's really a "pattern." It's more of an idiom.

At any rate, I'd call it either a fluent interface, or an internal Domain Specific Language.

kyoryu 2010-04-13 06:01:01

ansaurus

tags:

views:

answers:

C# - Name the Design Pattern

related questions