dispatching to same function name based on argument type

[metaperl]

In this video -
http://video.google.com/videoplay?d...=14&start=0&num=10&so=0&type=search&plindex=0

Peter Seibel says that Lisp generic functions give Lisp an edge in
"double dispatch" or even higher degrees of dispatch. I.e., when you
must decide which function to run based on the types of n or more
things.

The example he gave was displaying one of { Book, CD, DVD } to
any of { Text , Graphics }

but can't you simply write a bunch of static functions for each case?
Ie:

static void display(Book b, TextDisplay t);
static void display(Book b, GraphicDisplay t);

and so on?

 

[Patricia Shanahan]

In this video -
http://video.google.com/videoplay?d...=14&start=0&num=10&so=0&type=search&plindex=0

Peter Seibel says that Lisp generic functions give Lisp an edge in
"double dispatch" or even higher degrees of dispatch. I.e., when you
must decide which function to run based on the types of n or more
things.

The example he gave was displaying one of { Book, CD, DVD } to
any of { Text , Graphics }

but can't you simply write a bunch of static functions for each case?
Ie:

static void display(Book b, TextDisplay t);
static void display(Book b, GraphicDisplay t);

and so on?

You can, but the class containing the static methods would have N*M
methods, where N is the number of media and M is the number of displays.
It would have to be updated for addition of either a new medium or a new
display type.

Ideally, one would implement e.g. paper tape input by adding a class
PaperTape, implementing the same interface as Book, CD, and DVD, and
that would be the end of the matter.

Patricia

 

[Eric Sosman]

Patricia Shanahan wrote On 08/24/07 11:06,:

You can, but the class containing the static methods would have N*M
methods, where N is the number of media and M is the number of displays.
It would have to be updated for addition of either a new medium or a new
display type.

Ideally, one would implement e.g. paper tape input by adding a class
PaperTape, implementing the same interface as Book, CD, and DVD, and
that would be the end of the matter.

Also, note that Java's determination of which method
to call depends on the compile-time types of the arguments,
not their run-time types. If all these things are subclasses
of Media and Display, as appropriate, then

Media m = new Book();
Display d = new TextDisplay();
display(m, d);

.... will *not* call the first of your static functions.