2006
DOI: 10.1016/j.scico.2005.07.003
|View full text |Cite
|
Sign up to set email alerts
|

Safe instantiation in Generic Java

Abstract: This paper introduces the "Safe Instantiation Principle", a new design criterion for evaluating extensions of Java that support generic types. The paper initially focuses on the GJ and NextGen formulations of Generic Java and the implications of safe instantiation for both approaches. Then it applies the safe instantiation principle to the problem of adding mixins to Java as generic types. Finally, it shows that the hygienic formulation of mixins is the only way to maintain safe instantiation and type soundnes… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
9
0

Year Published

2008
2008
2018
2018

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 9 publications
(9 citation statements)
references
References 15 publications
0
9
0
Order By: Relevance
“…To detect possible Whatever types anti‐pattern causes, the detector uses a list of classes that are known to be too generic . When a method uses one of these classes, the detector informs that there is an issue.…”
Section: Anti‐pattern Detection Heuristics (Detectors)mentioning
confidence: 99%
See 2 more Smart Citations
“…To detect possible Whatever types anti‐pattern causes, the detector uses a list of classes that are known to be too generic . When a method uses one of these classes, the detector informs that there is an issue.…”
Section: Anti‐pattern Detection Heuristics (Detectors)mentioning
confidence: 99%
“…However, the structures that they compare are very different because manifestation of these issues in Java is very different from their manifestation in WSDL. For instance, the tag <any> is the manifestation of the Whatever‐types anti‐patterns in WSDL documents, but in Java, the cause of this anti‐pattern can be the use of the class Object or not using generics when available, for example, using List instead of List<Clazz> . Something similar happens with the Undercover fault information within standard messages anti‐pattern.…”
Section: Anti‐pattern Detection Heuristics (Detectors)mentioning
confidence: 99%
See 1 more Smart Citation
“…Too generic type definitions -definitions that are based on xsd:any-should be avoided because they only obscure the semantic of the data. This problem is analogous to using too many generics types in Java, such as Object for defining the return class or parameters' classes of a method, to assure extensibility [29]. Besides, as these definitions allow all the other defined data, they are inherently redundant.…”
Section: Guidelines For Improving Service Descriptionsmentioning
confidence: 99%
“…Overall, by applying these modifications we were able to decrease the number of occurrences of the Whatever types anti-pattern. Aside from these benefits for WSDL document quality, this refactor is also recommended for any Java code [20].…”
Section: The Service Implementation Watchermentioning
confidence: 99%