Piccola is a language for composing applications from software components. It has a small syntax and a minimal set of features needed for specifying different styles of software composition. The core features of Piccola are communicating agents, which perform computations, and forms, which are the communicated values. Forms are a special notion of extensible, immutable records. Forms and agents allow us to unify components, static and dynamic contexts and arguments for invoking services. Through a series of examples, we present a tour of Piccola, illustrating how forms and agents suffice to express a variety of compositional abstractions and styles
Present-day applications are increasingly required to be flexible, or "open" in a variety of ways. B...
Separation of concerns is a principle we apply to reduce complexity. This principle is especially im...
Wrapping external components by scripts can be a performance bottleneck if inter-language bridging i...
Although object-oriented languages are well-suited to implementing software components, they fail to...
Software is not just difficult to develop, but it is even more difficult to maintain in the face of ...
Many competing definitions of software components have been proposed over the years, but still today...
Object-oriented technology and design is not the final answer to the recurrent problem of making sys...
The last decade has shown that object-oriented technology alone is not enough to cope with the rapid...
The last decade has shown that object-oriented technology alone is not enough to cope with the rapid...
The last decade has shown that object-oriented technology alone is not enough to cope with the rapid...
Experience has shown us that object-oriented technology alone is not enough to guarantee that the sy...
Experience has shown us that object-oriented technology alone is not enough to guarantee that the sy...
www.iam.unibe.ch/∼scg Although the term software component has become commonplace, there is no unive...
AbstractAlthough the term software component has become commonplace, there is no universally accepte...
The development of flexible and reusable programming abstractions has suffered from the inherent pro...
Present-day applications are increasingly required to be flexible, or "open" in a variety of ways. B...
Separation of concerns is a principle we apply to reduce complexity. This principle is especially im...
Wrapping external components by scripts can be a performance bottleneck if inter-language bridging i...
Although object-oriented languages are well-suited to implementing software components, they fail to...
Software is not just difficult to develop, but it is even more difficult to maintain in the face of ...
Many competing definitions of software components have been proposed over the years, but still today...
Object-oriented technology and design is not the final answer to the recurrent problem of making sys...
The last decade has shown that object-oriented technology alone is not enough to cope with the rapid...
The last decade has shown that object-oriented technology alone is not enough to cope with the rapid...
The last decade has shown that object-oriented technology alone is not enough to cope with the rapid...
Experience has shown us that object-oriented technology alone is not enough to guarantee that the sy...
Experience has shown us that object-oriented technology alone is not enough to guarantee that the sy...
www.iam.unibe.ch/∼scg Although the term software component has become commonplace, there is no unive...
AbstractAlthough the term software component has become commonplace, there is no universally accepte...
The development of flexible and reusable programming abstractions has suffered from the inherent pro...
Present-day applications are increasingly required to be flexible, or "open" in a variety of ways. B...
Separation of concerns is a principle we apply to reduce complexity. This principle is especially im...
Wrapping external components by scripts can be a performance bottleneck if inter-language bridging i...