xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Re: [XOM-interest] why is Element.toString() final?

From: Elliotte Harold <elharo AT metalab.unc.edu>
To: Steve Loughran <steve.loughran AT gmail.com>
Cc: xom-interest <xom-interest AT lists.ibiblio.org>
Subject: Re: [XOM-interest] why is Element.toString() final?
Date: Fri, 09 Dec 2005 08:19:31 -0500

Steve Loughran wrote:

Given that it is primarily for debugging, why is Element.toString() final?

It's final because everything should be final unless and until there's a clear and compelling use case for subclassing/overriding it. So far no one has demonstrated such a use case or shown a need for overriding it. if someone does, then I'd consider making it non-final.

--
Elliotte Rusty Harold elharo AT metalab.unc.edu
XML in a Nutshell 3rd Edition Just Published!
http://www.cafeconleche.org/books/xian3/
http://www.amazon.com/exec/obidos/ISBN=0596007647/cafeaulaitA/ref=nosim

[XOM-interest] why is Element.toString() final?, Steve Loughran, 12/09/2005
- Re: [XOM-interest] why is Element.toString() final?, Elliotte Harold, 12/09/2005
  - Re: [XOM-interest] why is Element.toString() final?, Steve Loughran, 12/09/2005
    - Re: [XOM-interest] why is Element.toString() final?, Noam Tamim, 12/21/2005
      - Re: [XOM-interest] why is Element.toString() final?, Steve Loughran, 12/21/2005
        
        Re: [XOM-interest] why is Element.toString() final?, Noam Tamim, 12/24/2005