Nesting in an Object Oriented Language is NOT for the Birds

Buhr, Peter A.; Zarnke, C. Robert

doi:10.1007/3-540-45910-3_8

Cited by 4 publications

(5 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Although nested classes can be very useful (as is shown in both [Madsen87] and [Buhr&Zarnke88]), this mechanism can be used by a programmer to break the encapsulation of objects. The next example is an example of class nesting.…”

Section: Classes As Attributes Class Nesting Versus Mixin Nestingmentioning

confidence: 99%

“…The relation to nested classes [Buhr&Zarnke88][Madsen87] has been discussed above. The correspondence between so called virtual superclasses in BETA, and mixins has already been noted [Bracha92].…”

Section: Related Workmentioning

confidence: 99%

“…Introducing block structure in an object-oriented system is a very delicate operation [Buhr&Zarnke88]. This is because the "natural" form of scoping that emerges from the nesting of blocks --identifiers declared in some context are visible in blocks declared in the same context --can seriously interfere with the notion of encapsulation.…”

Section: Introducing Block Structure In Object-oriented Languagesmentioning

confidence: 99%

See 2 more Smart Citations

Nested Mixin-Methods in Agora

Steyaert

Codenie

D'Hondt

et al. 1993

ECOOP’ 93 — Object-Oriented Programming

View full text Add to dashboard Cite

show abstract

Section: Classes As Attributes Class Nesting Versus Mixin Nestingmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: Introducing Block Structure In Object-oriented Languagesmentioning

confidence: 99%

See 1 more Smart Citation

Nested Mixin-Methods in Agora

Steyaert

Codenie

D'Hondt

et al. 1993

ECOOP’ 93 — Object-Oriented Programming

View full text Add to dashboard Cite

show abstract

“…Some of the argumenta aound like a nostalgic defense of structured deaign/programming [1,18], ud some authora even ahow how to converta atructured deaign into an object-oriented deaign [1]. Other authora [5,2,20] have exam.ined a related iuue, namely, the implemenh.tion of neating in object-oriented programming luguagea. We believe a common concem at both the design and programmiDg language levela ia neating encapsulation.…”

Section: Introductionmentioning

confidence: 99%

“…That is, the semantics of nesting should aliow refe. rence to definitiona from outúde the containing bloc.k without violating encapaulation [5,2,20].…”

Section: Introductionmentioning

confidence: 99%

A Rationale for Both Nesting and Inheritance in Object-Oriented Design

Carneiro

Cowan

Lucena

1993

Anais Do VII Simpósio Brasileiro De Engenharia De Software (SBES 1993)

View full text Add to dashboard Cite

It has been observed that design of complex objects such as software requires both decomposition by form (atomic objects) and decomposition by function (nesting) in order to reduce the design to a set of manageable components. However, the object-oriented design paradigm mostly supports decomposition by form. This paper uses a simple example to motivate the need for nesting (decomposition by function) and illustrates how nesting might be incorporated into a design language. We then demonstrate how the introduction of nesting into software specification and design significantly increases reusability. AD-Vcharts, a new visual formalism, and VDM are used to provide a semantics for nesting.

show abstract

Addressing in a Persistent Environment

Buhr

Zarnke

1990

Persistent Object Systems

View full text Add to dashboard Cite

Nesting in an Object Oriented Language is NOT for the Birds

Cited by 4 publications

References 11 publications

Nested Mixin-Methods in Agora

Nested Mixin-Methods in Agora

A Rationale for Both Nesting and Inheritance in Object-Oriented Design

Addressing in a Persistent Environment

Contact Info

Product

Resources

About