2005
DOI: 10.1016/j.entcs.2005.02.036
|View full text |Cite
|
Sign up to set email alerts
|

Flexible Bytecode for Linking in .NET

Abstract: Dynamic linking in modern execution environments like .NET is considerably more sophisticated than in the days of C shared libraries on UNIX. One aspect of this sophistication is that .NET assemblies embed type information about dynamically linked resources. This type information implicitly represents compile-time assumptions about the resources available at run-time. However, the resources available at run-time may differ from those available at compiletime. For example, the execution environment on a mobile … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
7
0

Year Published

2005
2005
2007
2007

Publication Types

Select...
4
2

Relationship

2
4

Authors

Journals

citations
Cited by 8 publications
(7 citation statements)
references
References 18 publications
(16 reference statements)
0
7
0
Order By: Relevance
“…Some recent work [3,4] has introduced the notion of flexible dynamic linking in .NET, where type variables are contained in binaries exactly as it happens in polymorphic bytecode [1].…”
Section: Related and Further Workmentioning
confidence: 99%
See 2 more Smart Citations
“…Some recent work [3,4] has introduced the notion of flexible dynamic linking in .NET, where type variables are contained in binaries exactly as it happens in polymorphic bytecode [1].…”
Section: Related and Further Workmentioning
confidence: 99%
“…However, as already noted [3,4], combining polymorphic bytecode with dynamic linking allows programmers to reuse code with more flexibility, because the same polymorphic binaries can be dynamically adapted to run on diverse environments.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…In the meantime, linking-time behaviour, both for .NET and for the Java Virtual Machine has received some formal attention [2,12,7]. The current work is built on a number of earlier projects, focused initially on component evolution [14], which anticipated the .NET 2.0 introduction of type forwarders [19]; and then on component adaptation [9,1]. Execution environments that support the runtime interpretation of metadata, in conjunction with pertinent configuration files, are bound to receive increasing attention [25,27,4].…”
Section: Related and Future Workmentioning
confidence: 99%
“…Sharable assemblies must have strong names, which include a public key, file hashes, and a major.minor.build.revision version. Compile-time assembly references can be modified before use by XML policy files of the application, code publisher, and machine administrator; the semantics is complex [BMED05].…”
Section: Related Workmentioning
confidence: 99%