M. Flatt and M. Felleisen. Units: Cool units for HOT languages. In Proc. of the ACM SIGPLAN '98 Conf. on Programming Language Design and Implementation (PLDI), pages 236--248, Montreal, Canada, June 1998. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Static and Dynamic Structure in Design Patterns - Eide, Reid, Regehr, Lepreau (2002) (Correct)
....a systematic method for applying our approach to existing patterns (Section 3. 1) We show that our approach is applicable to three major programming language paradigms that support the unit component model: imperative languages, exemplified by C [21] functional languages, exemplified by Scheme [11]; and object oriented languages, exemplified by Java [17] Sections 2 and 3) We demonstrate our approach with two examples from the OSKit [12] a set of operating system components written in C (Sections 3.2 and 3.3) We evaluate the approach by applying it to each pattern described by Gamma ....
....patterns and in multiple language paradigms; we consider the static dynamic decision in the context of design patterns; and we thoroughly evaluate when to apply and when not to apply our approach. 2. THE UNIT MODEL Our approach to realizing patterns is most readily expressed in terms of units [10,11], a component definition and linking model in the spirit of the Modula 3 and Mesa [19] module systems. The unit model emphasizes the notion of components as reusable architectural elements with well defined interfaces and dependencies. It fits well with the definitions of component in the ....
[Article contains additional citation context not shown here]
M. Flatt and M. Felleisen. Units: Cool units for HOT languages. In Proc. of the ACM SIGPLAN '98 Conf. on Programming Language Design and Implementation (PLDI), pages 236--248, Montreal, Canada, June 1998.
Aspect Weaving as Component Knitting: Separating Concerns .. - Eide, Reid, Flatt.. (2001) (1 citation) Self-citation (Flatt) (Correct)
....imports [ io: printf ] exports [ main: main ] depends main needs io; files hello.c ; b) The file hello.unit, the unit definition for Hello, world Figure 1: Defining an atomic unit with Knit. 2Knit The Knit component specification and linking language is based on units [5, 6], a model of components in the spirit of the Modula 3 [8] and Mesa [10] module systems. A unit is a component or model definition, either atomic (with a C implementation) or compound (composed of other units) 2.1 Building Blocks: Atomic Units An atomic unit can be thought of as a module with ....
M. Flatt and M. Felleisen. Units: Cool units for HOT languages. In Proc. ACM SIGPLAN '98 Conf. on Programming Language Design and Implementation (PLDI), pages 236--248, June 1998.
Knit: Component Composition for Systems Software - Reid, Flatt, Stoller, al. (2000) (20 citations) Self-citation (Flatt) (Correct)
....interfaces. Indeed, attempting to use such techniques while developing the OSKit has been a persistent source of problems, both for ourselves as developers and for OSKit users. We have developed a new module language and toolset for managing systems components called Knit. Knit is based on units [8, 9], a model of components in the spirit of the Mesa [23] and Modula 3 [14] module languages. In addition to bringing state of the art module technology to C programs, Knit provides features of particular use in the design and implementation of complex, low level systems: Knit provides automatic ....
....component languages offer little help to the programmer in ensuring that components are linked together properly. While objects can serve a useful and important role in implementing data structures, they do as much harm as good at the component level. 2. 3 Unit Linking The linking model for units [8,9] eschews the bag of objects in favor of explicit, programmer directed linking. It also avoids the excessive dynamism and intractable analysis of object based linking by keeping the linking specification separate from (and simpler than) the core programming language. The model builds on pioneering ....
[Article contains additional citation context not shown here]
M. Flatt and M. Felleisen. Units: Cool Units for HOT Languages. In Proc. ACM SIGPLAN '98 Conf. on Programming Language Design and Implementation (PLDI), pages 236--248, June 1998.
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