Talk:Java (programming language): Difference between revisions

Content deleted Content added
Dynamic class loading is not reflection
Jkominek (talk | contribs)
No edit summary
Line 51:
 
:::No, dynamic class loading is not reflection. Two different things. Dynamic class loading is very much a part of the Java language. See http://java.sun.com/docs/books/jls/second_edition/html/execution.doc.html#44459 It is far more pervasive and integral to Java than to C; in fact, all classes in Java are loaded dynamically.
 
::::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!)
 
:::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?