Related articles |
---|
[20 earlier articles] |
Re: Polymorphism vs. Overloading danhicks@aol.com (1994-10-31) |
Re: Polymorphism vs. Overloading odersky@ira.uka.de (Martin Odersky) (1994-10-31) |
Re: Polymorphism vs. Overloading bevan@cs.man.ac.uk (1994-10-27) |
Re: Polymorphism vs. Overloading pjj@cs.man.ac.uk (1994-10-28) |
Re: Polymorphism vs. Overloading jhf@c3serve.c3.lanl.gov (1994-10-28) |
Re: Polymorphism vs. Overloading mmcg@bruce.cs.monash.edu.au (1994-10-29) |
Re: Polymorphism vs. Overloading hbaker@netcom.com (1994-10-29) |
Re: Polymorphism vs. Overloading jhallen@world.std.com (1994-11-01) |
Re: Polymorphism vs. Overloading kanze@lts.sel.alcatel.de (kanze) (1994-11-01) |
Re: Polymorphism vs. Overloading davidm@Rational.COM (1994-10-31) |
Re: Polymorphism vs. Overloading bill@amber.ssd.csd.harris.com (1994-11-01) |
Re: Polymorphism vs. Overloading drichter@pygmy.owlnet.rice.edu (1994-11-01) |
Re: Polymorphism vs. Overloading bevan@cs.man.ac.uk (1994-11-02) |
[4 later articles] |
Newsgroups: | comp.compilers |
From: | hbaker@netcom.com (Henry G. Baker) |
Keywords: | polymorphism |
Organization: | nil |
References: | 94-10-144 94-10-180 |
Date: | Sat, 29 Oct 1994 20:37:45 GMT |
ryer@dsd.camb.inmet.com (Mike Ryer) writes:
>Overloading happens at compilation time -- the compiler decides which function
>to invoke based on statically-determined types of the operands.
>
>Polymorphism may not happen until runtime -- the compiler generates code that
>fans out based on the runtime value of a tag.
You may be correct that most implementations of overloading and
polymorphism do what you suggest, but aren't you mixing up semantics
and implementation by tying these concepts so closely to an envisioned
implementation?
Henry Baker
Read ftp.netcom.com:/pub/hbaker/README for info on ftp-able papers.
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.