Proceedings 2nd IEEE International Symposium on Object-Oriented Real-Time Distributed Computing (ISORC'99) (Cat. No.99-61702)
DOI: 10.1109/isorc.1999.776349
|View full text |Cite
|
Sign up to set email alerts
|

The PURE family of object-oriented operating systems for deeply embedded systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
28
0
1

Publication Types

Select...
6
1
1

Relationship

1
7

Authors

Journals

citations
Cited by 36 publications
(29 citation statements)
references
References 14 publications
0
28
0
1
Order By: Relevance
“…Many of these systems use heavyweight composition mechanisms, such as COM or CORBA, and several support runtime component instantiation or interpositioning. PURE [6], eCos [66], and icWORKSHOP [35] more closely match TinyOS's goal of lightweight, static composition. These systems consist of a set of components that are wired together (either manually or using a composition tool) to form an application.…”
Section: Related Workmentioning
confidence: 99%
“…Many of these systems use heavyweight composition mechanisms, such as COM or CORBA, and several support runtime component instantiation or interpositioning. PURE [6], eCos [66], and icWORKSHOP [35] more closely match TinyOS's goal of lightweight, static composition. These systems consist of a set of components that are wired together (either manually or using a composition tool) to form an application.…”
Section: Related Workmentioning
confidence: 99%
“…4 But indirectly there may be cases where the changes made have strange effects in this regard. Assume function f x gets specialized, which then propagates downward because the new implementation of f x may perform even better if function f z , called by f x , is specialized too (but, maybe, in a different fashion than f x ).…”
Section: Vertical Changesmentioning
confidence: 99%
“…As a matter of fact, it is impossible to proof that the design and implementation of some software is optimal with respect to runtime resource requirements. The authors have, however, profound experience in developing resource-minimal object-oriented product lines [11,10,34]. There is, furthermore, quite some evidence that any OO version would lead to higher memory requirements than the AO version: As pointed out in the previous sections, runtime mechanisms have to be used with OO to reach the required flexibility which, as described in sections 3.5 and 4, induce overhead.…”
Section: Design Issuesmentioning
confidence: 99%