Here is some Ruby code:
def InTheForest x
donald = Duck.new
john = Person.new
print "Donald in the forest: "
print "John in the forest: "
donald = Duck()
john = Person()
sys.stdout.write("Donald in the forest: ")
sys.stdout.write("John in the forest: ")
The code does not show the whole story. Duck typing is about trying something and handling exceptions if they occur. As long it quacks, treat it like a duck, otherwise, treat it differently.
try: dog.quack() except AttributeError: dog.woof()
This behavior is explained at the top of the wikipedia Duck_typing article following a description of a non-duck-typed language:
In a duck-typed language, the equivalent function would take an object of any type and call that object's walk and quack methods. If the object does not have the methods that are called then the function signals a run-time error. If the object does have the methods, then they are executed no matter the type of the object, evoking the quotation and hence the name of this form of typing.
For your example:
class Person: def help(self): print("Heeeelp!") class Duck: def help(self): print("Quaaaaaack!") class SomethingElse: pass def InTheForest(x): x.help() donald = Duck() john = Person() who = SomethingElse() for thing in [donald, john, who]: try: InTheForest(thing) except AttributeError: print 'Meeowww!'
Quaaaaaack! Heeeelp! Meeowww!