Gosling J, McGilton H. The Java language  Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Applying the Decorator Pattern for Profiling.. - Duffy, Gibson, Malloy (Correct)
....state will not be recognized if invariants are only validated upon program termination. 7 Implementation Diculty In this section, we overview two diculties that we encountered during the implementation of the pro ler. While our implementation language is C [31] the problems also occur in Java [19]. The rst diculty concerns run time type information and the second diculty concerns name hiding. For the rst diculty, consider Figure 1, containing classes UserClassImpl, Profiler, and ProfiledUserClass, described in Section 3.1. Our technique is designed so that a programmer may use either ....
....work includes extending the invariant validation to other types of applications where objects in the program are more volatile. Moreover, we are constructing a case study to apply the Decorator pattern to pro ling memory in C applications. See name hiding in reference [31] or reference [19]. 9 ....
J. Gosling, B. Joy, and G. Steele. The Java Language
Ephemeral Java Source Code - Eisenbach, Sadler (1999) (Correct)
....systems are implemented. It is possible to construct implementations, which avoid or ameliorate the problem[8] but only at a price, which increases the complexity of the implementation and in some cases may reduce the object oriented capabilities of the language[2] The Java Language Specification[9] solves the problem by stipulating how implementations must behave. Conforming implementations must record type information symbolically and are mandated to implement dynamic loading. This development represents a new excursion into comparatively unknown territory and the Sun Java Software team ....
....together. Dynamic binding (and binary compatibility) by contrast is concerned with whether a set of binaries will run together. In the next section we show how these two concepts can provide interference with each other. 3. Binary Compatibility the Guarantee The Java Language Specification[9] defines the term binary compatibility in a declarative manner, expressing the properties that binary compatible changes must guarantee: A change to a type is binary compatible with (equivalently, does not break compatibility with) preexisting binaries if pre existing binaries that previously ....
[Article contains additional citation context not shown here]
J. Gosling, B. Joy and G. Steele, The Java Language
Ambiguities in Java - Jien-Tsai Chan And (2002) (Correct)
No context found.
Gosling J, McGilton H. The Java language
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC