| 
|
QuoteRef: hamiJ2_2003
topics >
all references >
ThesaHelp:
references g-h
Topic:
programming language design
Topic:
extensible languages
Topic:
attribute-value pairs as information
Topic:
user-defined data type
Topic:
interpreter
Topic:
memory management by garbage collection
Group:
data value
Topic:
variable as reference to a value
Topic:
uniform reference to data
Topic:
interface type
Topic:
non-hierarchical classification and multiple classification
Topic:
opaque and partially-opaque data types
Topic:
global declarations and variables
Topic:
local vs. global
Topic:
object-oriented methods
Topic:
generic operations and polymorphism
Topic:
object-oriented fields
Topic:
inheritance of properties
Topic:
event controlled processing
Topic:
deployable module or assembly
Topic:
interface between program modules
Topic:
dynamic vs. static data type
Topic:
type reflection and introspection
Topic:
uniform language systems
Topic:
data alignment
Topic:
implementing distributed systems and applications
Topic:
scripting language
Topic:
software portability
Topic:
primitive data types of a language
Topic:
exception handling by try..catch
Group:
exception handling
Topic:
early vs. late binding
Reference
Hamilton, J., "Language interpretation in the Common Language Runtime", SIGPLAN Notices, 38, 2, February 2003, pp. 19-28. Google
20 ;;Quote: .NET supports a wide variety of programming languages through the common language runtime (CLR)
21 ;;Quote: System.Attribute is an arbitrary type associated with an object; extends metadata, e.g., 'const'
22 ;;Quote: CLR supports unsafe code, tail calls, user-defined value types, enumerations, unsigned ints, variable length arguments, pointer arithmetic, global variables, private scope, function pointers, call-by-reference, multidim arrays, pinned objects
22 ;;Quote: CLR supports pinned objects that do not move during garbage collection; for arguments to native functions
23 ;;Quote: a value type is a bit sequence allocated on the stack with an implicit type; defines a representation and valid operations
23+;;Quote: a reference type is an explicitly typed object allocated from the heap; unique identity and type handle
23 ;;Quote: any value type instance can be boxed and turned into a reference type instance; inherits from ValueType or Enum; no subtyping
23 ;;Quote: CLR uses single inheritance with multiple interfaces; all interface methods must be implemented
23+;;Quote: can not derive a subtype from a sealed CLR type
23 ;;Quote: static CLR fields and methods are global to the type
23 ;;Quote: a virtual CLR method may be final (no derivation), new (parent method accessible), abstract (no implementation); interface methods are virtual
23 ;;Quote: a CLR property is a named value and its methods; typically a getter method and an optional setter method
23 ;;Quote: a CLR event includes methods for issuing, registering, and deregistering event notifications; like properties but with different, conventionally named methods
23 ;;Quote: CLR members defined with an accessibility rule: private, family, assembly, family and/or assembly, public
23+;;Quote: family accessibility only allows access from derived types
23+;;Quote: assembly accessibility allows access from an assembly; i.e., one or more application units with name scoping, class versioning, etc.
24 ;;Quote: CLR reflection allows runtime type creation, queries, and method invocation
24 ;;Quote: CLR does not specify method overloading; compiler explicitly specifies whether a method is virtual, non-virtual, or new
24 ;;Quote: a CLR type may have sequential or explicit layout; use explicit layout to define offsets and overall size for new value types
24 ;;Quote: a shared type system is necessary to integrate multiple languages
24+;;Quote: .NET's common language specification (CLS) is a subset of its type system; unique, Unicode names, no static and instance methods or fields, properties, events, predefined types, closed
25 ;;Quote: CLR uses Ramsey and Jones' two-pass runtime-stack unwinding exception handlers; first, find the handler, then cleanup stack, etc.; first, cross-language exception handler
25+;;Quote: CLR exception handlers may be typed (catch on type match), filtered (catch on true evaluation), termination (always called on exception cleanup); late binding
ThesaHelp: references g-h (299 items)
Topic: programming language design (53 items)
Topic: extensible languages (71 items)
Topic: attribute-value pairs as information (57 items)
Topic: user-defined data type (13 items)
Topic: interpreter (59 items)
Topic: memory management by garbage collection (116 items)
Group: data value (19 topics, 433 quotes)
Topic: variable as reference to a value (21 items)
Topic: uniform reference to data (34 items)
Topic: interface type (50 items)
Topic: non-hierarchical classification and multiple classification (16 items)
Topic: opaque and partially-opaque data types (14 items)
Topic: global declarations and variables (33 items)
Topic: local vs. global (29 items)
Topic: object-oriented methods (42 items)
Topic: generic operations and polymorphism (67 items)
Topic: object-oriented fields (28 items)
Topic: inheritance of properties (24 items)
Topic: event controlled processing (46 items)
Topic: deployable module or assembly (12 items)
Topic: interface between program modules (55 items)
Topic: dynamic vs. static data type (24 items)
Topic: type reflection and introspection (28 items)
Topic: uniform language systems (25 items)
Topic: data alignment (2 items)
Topic: implementing distributed systems and applications (41 items)
Topic: scripting language (27 items)
Topic: software portability (43 items)
Topic: primitive data types of a language (31 items)
Topic: exception handling by try..catch (53 items)
Group: exception handling (12 topics, 314 quotes)
Topic: early vs. late binding (15 items)