Matches in DBpedia 2014 for { <http://dbpedia.org/resource/Heap_pollution> ?p ?o. }
Showing items 1 to 12 of
12
with 100 items per page.
- Heap_pollution abstract "In Java programming language, type arguments and variables are not reified at run-time. As a result, different parameterized types are implemented by the same class or interface at run time. Indeed, all invocations of a given generic type declaration share a single run-time implementation. This results in the possibility of heap pollution.Under certain conditions, it is possible that a variable of a parameterized type refers to an object that is not of that parameterized type. The variable will always refer to an object that is an instance of a class that implements the parameterized type.".
- Heap_pollution wikiPageID "15399561".
- Heap_pollution wikiPageRevisionID "601790049".
- Heap_pollution hasPhotoCollection Heap_pollution.
- Heap_pollution subject Category:Java_platform.
- Heap_pollution comment "In Java programming language, type arguments and variables are not reified at run-time. As a result, different parameterized types are implemented by the same class or interface at run time. Indeed, all invocations of a given generic type declaration share a single run-time implementation. This results in the possibility of heap pollution.Under certain conditions, it is possible that a variable of a parameterized type refers to an object that is not of that parameterized type.".
- Heap_pollution label "Heap pollution".
- Heap_pollution sameAs m.03m7386.
- Heap_pollution sameAs Q5691516.
- Heap_pollution sameAs Q5691516.
- Heap_pollution wasDerivedFrom Heap_pollution?oldid=601790049.
- Heap_pollution isPrimaryTopicOf Heap_pollution.