Re: method overriding
From: Neal Gafter (gafter_at_spamcop.net)
Date: 03/17/04
- Previous message: John W.: "JNDI Ldap Password Expiration Controls"
- In reply to: Chris Uppal: "Re: method overriding"
- Next in thread: Chris Uppal: "Re: method overriding"
- Reply: Chris Uppal: "Re: method overriding"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 17 Mar 2004 02:10:19 GMT
Chris Uppal wrote:
> In my opinion the covariant returns are a heavyweight feature (complex
> semantics, complex implementation, non-obvious side-effects) that should be
> reserved (if they're used at all) for the cases where they are really *needed*.
This is the first time I've ever heard covariant returns described in these
terms. In what way are the semantics complex? What are the non-obvious side
effects? What is complex about the implementation?
I can tell you that J2SE 1.5.0 uses covariant returns in a number of places for
just this purpose.
- Previous message: John W.: "JNDI Ldap Password Expiration Controls"
- In reply to: Chris Uppal: "Re: method overriding"
- Next in thread: Chris Uppal: "Re: method overriding"
- Reply: Chris Uppal: "Re: method overriding"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]