[3606] in java-interest
Re: declaration v.s. definition ambiguity
daemon@ATHENA.MIT.EDU (Michael Daconta)
Fri Nov 17 10:26:26 1995
Date: Fri, 17 Nov 1995 06:40:04 -0700 (MST)
To: garya@village.org (Gary Aitken)
From: daconta@PrimeNet.Com (Michael Daconta)
Cc: java-interest@java.sun.com
At 10:33 AM 11/16/95 -0700, Gary Aitken wrote:
>
>
>...
>[deleted proposed wording for definition and declaration]
>...
>>I think you are close; however, I don't think there is actually any storage
>>allocated for "the stuff which implements the class." Not at runtime anyway.
>>At compile time there is of course symbol table entries. However,
>>I think the ANSI C distinction of storage allocation was referring to
>>runtime allocation.
>
>But there *is* lots of storage allocation at runtime.
>Not necessarily dynamic heap / stack allocation, but storage allocation
>none the less, which has to be considered in C as well.
>Static variables are allocated by the loader;
>the space taken up by the function bodies is allocated by the loader.
>
Agreed, however, I do not think the storage for code and statics is
what the ANSI C definition was refering to. Anyway, we are now
splitting hairs. In general I think the distinction is now clear for
me.
Thanks for your help.
- Mike Daconta
-
This message was sent to the java-interest mailing list
Info: send 'help' to java-interest-request@java.sun.com
