[3428] in java-interest
Re: declaration v.s. definition ambiguity
daemon@ATHENA.MIT.EDU (Gary Aitken)
Sat Nov 11 23:13:53 1995
Date: Sat, 11 Nov 1995 19:27:41 -0700
From: garya@village.org (Gary Aitken)
To: daconta@PrimeNet.Com (Michael C. Daconta), java-interest@java.sun.com
In-Reply-To: <v01510100acc96175a1d1@[198.68.41.96]>
>Java seems to have done away with declarations all together and
>just uses definitions.
I don't think this is quite correct, or else I don't understand what
you mean by definition.
The members of a class are declared, with no storage allocation
implied unless they are declared static.
The methods are defined, since the announcement of their signature is
required to be accompanied by the definition of the semantics which
implements them. Exception: abstract methods, which are a pure
declaration, and cannot include any semantics (unfortunately).
If you also consider interfaces, interfaces are pure declarations,
and have no storage reservation associated with them anywhere, unless
you consider the implicit storage reservation which occurs
when they are implemented in a class.
Gary Aitken garya@village.org
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com
