A number of lattice-theoretic fixed point rules are generalised to category theory and applied to... more A number of lattice-theoretic fixed point rules are generalised to category theory and applied to the construction of isomorphisms between list structures.
A considerable interest in design patterns has sprouted in the last couple of years. This interes... more A considerable interest in design patterns has sprouted in the last couple of years. This interest has been stimulated by the appearance of some excellent books on the subject. A notable example is the book by Gamma et al. . At the time the first ideas of patterns in software engineering were developed, a couple of essential ingredients were available. First, the mechanisms of behavioral and structural abstraction as offered by object-oriented methods (i.e. encapsulation and inheritance). Second, the availability of a notation to communicate the patterns (i.e. OMT [2] as proper predecessor of UML [3]), and last but not least, relevant design-experience with object-oriented systems. The latter is important because patterns are supposed to capture experience on how to solve certain often-occurring problems in system design. Many of the patterns described by Gamma are intended for improving a design by changing class dependencies (possibly without affecting resulting object dependencies) such that groups of classes are de-coupled from others. For example, the observer pattern can be used to make problem specific classes ("concrete subject") independent of the user interface ("concrete observer") such that the changes in the user interface will not affect the implementation of a problem solution. It is interesting to observe that such patterns lean very heavily on inheritance and the related extended object substitutability.
A number of lattice-theoretic fixed point rules are generalised to category theory and applied to... more A number of lattice-theoretic fixed point rules are generalised to category theory and applied to the construction of isomorphisms between list structures.
A considerable interest in design patterns has sprouted in the last couple of years. This interes... more A considerable interest in design patterns has sprouted in the last couple of years. This interest has been stimulated by the appearance of some excellent books on the subject. A notable example is the book by Gamma et al. . At the time the first ideas of patterns in software engineering were developed, a couple of essential ingredients were available. First, the mechanisms of behavioral and structural abstraction as offered by object-oriented methods (i.e. encapsulation and inheritance). Second, the availability of a notation to communicate the patterns (i.e. OMT [2] as proper predecessor of UML [3]), and last but not least, relevant design-experience with object-oriented systems. The latter is important because patterns are supposed to capture experience on how to solve certain often-occurring problems in system design. Many of the patterns described by Gamma are intended for improving a design by changing class dependencies (possibly without affecting resulting object dependencies) such that groups of classes are de-coupled from others. For example, the observer pattern can be used to make problem specific classes ("concrete subject") independent of the user interface ("concrete observer") such that the changes in the user interface will not affect the implementation of a problem solution. It is interesting to observe that such patterns lean very heavily on inheritance and the related extended object substitutability.
Uploads
Papers by R. van Geldrop