M. Serrano. Wide Classes. In ECOOP'99, volume 1628 of LNCS, pages 391--415, Berlin, 1999. Springer.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....this, but (informally) documenting the framework. Summarizing, we think that our proposal has two main useful features: we achieve a good degree of exibility in dealing with object run time behaviors, without any substantial type reclassi cation (as required in other approaches, see, e.g. [7,19]) basic features are (logically and physically) separated from object roles, thus class hierarchies do not tend to explode in number and size. Finally, the extended Java here proposed is translated into standard Java. We remark that the same extension can be applied to other object oriented ....

Manuel Serrano. Wide Classes. In R. Guerraoui, editor, Proceedings ECOOP'99, volume 1628 of LNCS, pages 391-415, Lisbon, Portugal, 1999. Springer-Verlag.

....from different comparison operators methods varies from language to language. A thorough examination of this issue is given in [9] 8 Newer approaches that head for subtractive object replacement, and modify the type system for this purpose in a similar way, are Fickle [7] and Wide Classes [17]. However, these approaches still do not allow for declaration of classes that must not be used as types. 6 Conclusions and Future Work We have designed the programming language GILGUL, a compatible extension to Java. It introduces the pseudoclass Comparand and the referent assignment operator ....

M. Serrano. Wide Classes. in: ECOOP '99. Proceedings, Springer.

....From a databases perspective, 6] suggests multiple most speci c classes, while in [19] objects may accumulate several roles in a functional setting. From a programming perspective, in [30] classes have modes representing di erent states, e.g. opened vs. iconi ed window. Wide classes [29] allow an object to be temporarily widened or shrunk , i.e. become an object of a subclass or superclass, requiring run time tests for the presence of elds. Predicate classes [10, 14] extend multimethods, suggesting method dispatch depending on predicates on the receiver and argument. We take ....

....vs. precedence lists, whereas print depends on empty vs. non empty lists. This is not possible in Fickle, unless perhaps, extended with multiple inheritance. For single method dispatch, in [30] classes have modes representing di erent states, e.g. opened vs. iconi ed window. Wide classes [29] are the nearest to our approach, and allow an object to be temporarily widened or shrunk . However they di er from Fickle, by dropping the requirement for a strong type system, and requiring run time tests for the presence of elds not amazing, since wide classes were primarily developed to ....

[Article contains additional citation context not shown here]

M. Serrano. Wide Classes. In ECOOP'99, volume 1628 of LNCS, pages 391-415. Springer, 1999.

....limitation of object oriented programming. Fickle [4] is a Java like language supporting dynamic object re classi cation, aimed at illustrating features for object re classi cation which could extend an imperative, typed, class based, objectoriented language. Other approaches have been attempted [3, 6, 7]; however, Fickle is more within the main stream of the object oriented approach, and moreover it is type safe, in the sense that any type correct program (in terms of the Fickle type system) is guaranteed never to access non existing elds or methods. A further problem is how to construct, ....

M. Serrano. Wide Classes. In ECOOP'99, volume 1628 of LNCS, pages 391-415. Springer, 1999.

.... TOSCA Teoria della Concorrenza, Linguaggi di Ordine Superiore e Strutture di Tipi. 2 Partially supported by EPSRC (Grant Ref:GR L 76709) Preprint submitted to Elsevier Preprint 12 November 2001 feature of Fickle, with respect to other proposals for dynamic object reclassi cation (see, e.g. [2,4,5]) is that it is type safe, in the sense that any type correct program is guaranteed never to access non existing elds or methods. Fickle is essentially a small subset of Java (with only non abstract classes, instance elds and methods, integer and boolean types and a minimal set of statements ....

M. Serrano. Wide Classes. In ECOOP'99, volume 1628 of LNCS, pages 391-415. Springer, 1999. 14

....99, 8] Although both Fickle and Fickle 99 address the same requirement for object re classi cation, the approaches are very di erent. functional setting. From a programming perspective, in [22] classes have modes representing di erent states, e.g. opened vs. iconi ed window. Wide classes [21] allow an object to be temporarily widened or shrunk , i.e. become an object of a subclass or superclass, requiring run time tests for the presence of elds. Predicate classes [5, 9] extend multimethods, suggesting method dispatch depending on predicates on the receiver and argument. We take a ....

....extended with multiple inheritance. Finally, 5, 9] raise the question of disjointness and completeness of predicates (unambiguous and complete) Similarly, for single method dispatch, in [22] classes have modes representing di erent states, e.g. opened vs. iconi ed window. Wide classes [21] are the nearest to our approach, and allow an object to be temporarily widened or shrunk . However they di er from Fickle, by dropping the requirement for a strong type system, and requiring run time tests for the presence of elds. Anyway the aim of wide classes was to have a better memory ....

[Article contains additional citation context not shown here]

M. Serrano. Wide Classes. In ECOOP'99, volume 1628 of LNCS, pages 391-415. Springer, 1999.

....where a class may have several modes representing the transient states, e.g. opened window, iconified window etc. This however requires knowledge about all possible modes at the time of programming that class, somewhat departing from classical object oriented philosophy. Wide classes of [19] extend the language Clos allowing an object to be temporarily widened , i.e. become an object of a subclass, and then shrunk , i.e. become an object of the original class. However this approach requires run time tests for the presence of fields. For a somewhat different purpose, new classes may ....

....should return 20, while line 6 should return 25. But what about line 7 Since each object belongs to exactly one class at a time, marks is not available for judy at that point. We see four strategies to prevent execution of line 7: First, check at run time the presence of a field or method, as in [19] i.e. execute 4, but raise an exception at 7. Second, allow mutations only if there are no remaining references that consider the object to have a type incompatible to the new type i.e. the mutation on line 5 would not be executed. Third, allow mutations only between classes with the same ....

[Article contains additional citation context not shown here]

M. Serrano. Wide Classes. In ECOOP'99, LNCS 1628, pages 391--415. Springer, 1999.

No context found.

M. Serrano. Wide classes. In Proceedings ECOOP'99, pages 391--415, Lisbon, Portugal, June 1999.

No context found.

M. Serrano. Wide Classes. In ECOOP'99, volume 1628 of LNCS, pages 391--415, Berlin, 1999. Springer.

No context found.

Manuel Serrano. Wide Classes. In R. Guerraoui, editor, Proceedings ECOOP'99, volume 1628 of LNCS, pages 391--415, Lisbon, Portugal, 1999. Springer-Verlag.

No context found.

M. Serrano. Wide Classes. In ECOOP'99, volume 1628 of LNCS, pages 391--415, Berlin, 1999. Springer.

No context found.

M. Serrano. Wide Classes. In ECOOP'99, volume 1628 of LNCS, pages 391--415. Springer, 1999. A Operational semantics, definitions of lookup, subtypes, acyclic programs, and agreements

No context found.

M. Serrano. Wide Classes. in: ECOOP '99. Proceedings, Springer.

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