Matthias Blume and Andrew W. Appel. Hierarchical modularity. ACM Transactions on Programming Languages and Systems, 21(4):813--847, 1999.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....to separate compilation as happens in our framework, simply because its validity requires the type environment extracted from the compilation environment to be well formed. Finally, several interesting papers can be found in literature on separate compilation for ML (see among many others [17, 16, 7]) All these papers clearly show that separate compilation in ML is not a simple issue, and for this reason, needs to be properly formalized. However, ML separate compilation is based on traditional static linking, therefore many problems arising in Java disappear in ML; for instance, the static ....

....contribute all together to the design of a better compiler linker for ML. For instance, using the terminology used in our paper to model the overall compilation process, 17] is mainly concerned with the de nition of the type extraction function, while [16] with the typechecking of sources and [7] with the de nition of the dependency function. 6 Conclusion We have introduced a formal framework modeling Java separate compilation. The overall compilation process is modeled by the formal notion of compilation schema, in which the aspects which concern truly separate typechecking of ....

M. Blume. Dependency analysis for standard ML. ACM Transactions on Programming Languages and Systems, 21(4):790-812, 1999.

....definition completely omits even the practical issues of how programs are to be organized into source files and how to support separate compilation. The existing SML implementations address these issues each in their own way, for instance Standard ML of New Jersey [3] has its Compilation Manager [5]. None of these approaches provide dynamic linking in a satisfactory way. Alice extends Standard ML by platform independent components a la Oz. Fig. 3 shows Alice versions of the Oz components depicted in Fig. 2. When the compiler encounters an import announcement, it loads the referenced ....

Blume, M. and A. Appel, Hierarchical modularity, ACM Transactions on Programming Languages and Systems 21 (1999), pp. 813--847.

....guarantees that the types of symbols in the interfaces between modules match, but it does nothing else to ensure that the objects with which a program links will behave in the manner that the programmer expects. Some languages, such as Standard ML [3] with its associated Compilation Manager [4], develop the idea of module level information hiding by providing the facility for structuring modules hierarchically. Lower levels in a module hierarchy can communicate across more expressive interfaces; higher levels can enforce more restrictive ones. We present an ML style hierarchical module ....

....the group can communicate amongst themselves through their own interfaces, which can be much less restrictive than the group s top level interface. This approach can be applied repeatedly to create a hierarchy of modules. Hierarchical modularity was comprehensively investigated by Blume and Appel [4]; we use a similar approach for Java. Our module system supports hierarchical modularity by allowing modules to explicitly list the submodules on which they depend. Modules can not only export classes that have been defined in their own source files, but also classes that have been defined in ....

[Article contains additional citation context not shown here]

Blume M, Appel AW. Hierarchical modularity. ACM Transactions on Programming Languages and Systems 1999; 21(4):812--846.

....from the component model of Flatt and Felleisen [9] who provide an extensive overview of related programming languages research. Module work that subsequently achieved similar goals includes the recursive functors of Crary et al. 5] and the typed assembly linker of Glew and Morrisett [12] CM [3] solves for ML many of the same problems that Knit solves for C, but ML provides CM with a preexisting module language and a core language with welldefined semantics. Unlike Knit, CM disallows recursive modules, thus sidestepping initialization issues. Further, CM relies on ML s type system to ....

M. Blume and A. W. Appel. Hierarchial Modularity. ACM Transactions on Programming Languages and Systems, pages 812--846, July 1999.

No context found.

Matthias Blume and Andrew W. Appel. Hierarchical modularity. ACM Transactions on Programming Languages and Systems, 21(4):813--847, 1999.

No context found.

Matthias Blume. Dependency analysis for Standard ML. ACM Transactions on Programming Languages and Systems, 21(4):790--812, 1999.

No context found.

Matthias Blume and Andrew W. Appel. Hierarchical modularity. ACM Transactions on Programming Languages and Systems, 21(4):813--847, 1999.

No context found.

Matthias Blume. Dependency analysis for Standard ML. ACM Transactions on Programming Languages and Systems, 21(4):790-- 812, 1999.

No context found.

M. Blume. Dependency analysis for standard ML. ACM Transactions on Programming Languages and Systems, 21(4):790-812, 1999.

No context found.

M. Blume. Dependency analysis for standard ML. ACM Transactions on Programming Languages and Systems, 21(4):790--812, 1999.

No context found.

M. Blume. Dependency analysis for standard ML. ACM Transactions on Programming Languages and Systems, 21(4):790--812, 1999.

No context found.

M. Blume and A.W. Appel. Hierarchical modularity. ACM Transactions on Programming Languages and Systems, 21(4):813-847, 1999.

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