Content deleted Content added
No edit summary |
More bickering over dynamic class loading |
||
Line 53:
::::Thats the way the [[Java virtual machine]] works, not the [[Java programming language]]. Sure they're muddled beyond belief, but I feel as though I can safely draw a line and say that the dynamic loading you're talking about isn't part of the language. (I certainly hope that native implementations of the [[Java programming language]] won't do the same thing!)
:::::Ok, what about when I say "2+3" and the VM adds two numbers together? I guess that's also how the VM works, not the language? Honestly, we can argue about this all day, but if you really don't think dynamic class loading is a fundamental part of the Java language, then perhaps we must simply agree to disagree. As you say below, it's not like it really matters anyway. --[[User:P3d0|P3d0]] 13:08, 19 Aug 2003 (UTC)
:::Besides, the fact that a language feature is implemented in a library is just good design, and doesn't mean that feature isn't part of the language. For instance, would you say that variadic functions are not part of C just because you need to #include <stdarg.h> to use them? --[[User:P3d0|P3d0]] 15:52, 18 Aug 2003 (UTC)
::::I'd say they're part of C because they affect the syntax. IMO, something isn't part of the language until there are syntactic elements related to it. Up until that point, I can get rid of it and replace it. This is getting a long ways away from being something that has anything to do with language facilities for networking. How does the dynamic class loading of the [[Java programming language]] (if there are any which pertain to the language, rather than its implementation) distinguish its networking facilities from another language enough that it is worth mentioning them?
:::::Because IIRC the entire motivation to add dynamic class loading was to allow programs to be loaded and run incrementally over a network. --[[User:P3d0|P3d0]] 13:08, 19 Aug 2003 (UTC)
| |||