Re: Java exceptions and function overriding.
From: Tor Iver Wilhelmsen (tor.iver.wilhelmsen_at_broadpark.no)
Date: 09/01/04
- Next message: Aria Kokoschka: "Re: Xerces problem with jar file"
- Previous message: eeyimaya: "Help: jsp:include error???"
- Next in thread: Razvan: "Re: Java exceptions and function overriding."
- Maybe reply: Razvan: "Re: Java exceptions and function overriding."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 01 Sep 2004 17:42:25 +0200
Babu Kalakrishnan <k.a.l.a@sankya.com> writes:
> Refer to the Java Language Specification Second Edition - section 11 for the
> full rationale behind why designers of the Java language chose to bifurcate
> exceptions into two types.
The C# language is strangely schizophrenic this way: The designers
decided you don't need to declare ANY exception throws, very nice of
them. (In effect, all exceptions are RuntimeExceptions.)
However, the language is more stringent than Java in other respects,
like explicit method "override"/"new" keywords, no switch fallthrough
etc.
- Next message: Aria Kokoschka: "Re: Xerces problem with jar file"
- Previous message: eeyimaya: "Help: jsp:include error???"
- Next in thread: Razvan: "Re: Java exceptions and function overriding."
- Maybe reply: Razvan: "Re: Java exceptions and function overriding."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
