W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2000

Re: Another Java Language Binding Question

From: Stephen R. Savitzky <steve@rsv.ricoh.com>
Date: 27 Jan 2000 15:01:13 -0800
To: Arnaud Le Hors <lehors@us.ibm.com>
Cc: www-dom@w3.org
Message-ID: <qcvh4f2k7a.fsf@congo.crc.ricoh.com>
Arnaud Le Hors <lehors@us.ibm.com> writes:

> I don't know what you mean by "artificially", but the reason it is
> abstract is that it's the closest we could get to an interface. Ideally
> the DOM java binding would only define interfaces. This is unfortunately
> impossible due to the way Java defines exceptions.

What he means is that there's no real reason beyond a desire for some kind
of philosophical purity to make it abstract: as far as I know no exception
anywhere in the Java classes is abstract; you can construct and throw an
IOException or even an Exception if you want to.  The fact is that the
implementation of the IDL concept of an Exception is mapped onto a
language binding in a language-dependent way; it isn't even logically
necessary for it to be an object at all.

Philosophical purity is not a good excuse for making things unnecessarily
complicated.

-- 
Stephen R. Savitzky  <steve@rsv.ricoh.com>  <http://rsv.ricoh.com/~steve/>
Platform for Information Applications:      <http://RiSource.org/PIA/>
Chief Software Scientist, Ricoh Silicon Valley, Inc. Calif. Research Center
 voice: 650.496.5710  front desk: 650.496.5700  fax: 650.854.8740 
  home: <steve@theStarport.org> URL: http://theStarport.org/people/steve/
Received on Thursday, 27 January 2000 18:02:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:47 GMT