The C programming language was devised in the early 1970s as a system implementation language for the nascent Unix operating system. Derived from the typeless language BCPL, it evolved a type structure; created on a tiny machine as a tool to improve a meager programming environment, it has become one of the dominant languages of today. This paper studies its evolution.

Abstract not found

Copyright c ○ 2005 by Cambridge University Press. This material is in copyright. Subject to statutory exception and to the provisions of relevant collective licensing agreements, no reproduction of any part may take place without the written permission of Cambridge University

This thesis defines a set of program restructuring operations (refactorings) that support the design, evolution and reuse of object-oriented application frameworks. The focus of the thesis is on automating the refactorings in a way that preserves the behavior of a program. The refactorings are defined to be behavior preserving, provided that their preconditions are met. Most of the refactorings are simple to implement and it is almost trivial to show that they are behavior preserving. However, for a few refactorings, one or more of their preconditions are in general undecidable. Fortunately, for some cases it can be determined whether these refactorings can be applied safely. Three of the most complex refactorings are defined in detail: generalizing the inheritance hierarchy, specializing the inheritance hierarchy and using aggregations to model the relationships among classes. These operations are decomposed into more primitive parts, and the power of these operations is discussed from the perspectives of automatability and usefulness in supporting design. Two design constraints needed in refactoring are class invariants and exclusive components. These constraints are needed to ensure that behavior is preserved across some refactorings. This thesis gives some conservative algorithms for determining whether a program satisfies these constraints, and describes how to use this design information to refactor a program.

Agent software is a rapidly developing area of research. However, the overuse of the word ‘agent ’ has tended to mask the fact that, in reality, there is a truly heterogeneous body of research being carried out under this banner. This overview paper presents a typology of agents. Next, it places agents in context, defines them and then goes on, inter alia, to overview critically the rationales, hypotheses, goals, challenges and state-of-the-art demonstrators of the various agent types in our typology. Hence, it attempts to make explicit much of what is usually implicit in the agents literature. It also proceeds to overview some other general issues which pertain to all the types of agents in the typology. This paper largely reviews software agents, and it also contains some strong opinions that are not necessarily widely accepted by the agent community. 1 1

The Hearsay-II system, developed during the DARPA-sponsored five-year speech-understanding research program, represents both a specific solution to the speech-understanding problem and a general framework for coordinating independent processes to achieve cooperative problem-solving behavior. As a computational problem, speech understanding reflects a large number of intrinsically interesting issues. Spoken sounds are achieved by a long chain of successive transformations, from intentions, through semantm and syntactic structurmg, to the eventually resulting audible acoustic waves. As a consequence, interpreting speech means effectively inverting these transformations to recover the speaker's intention from the sound. At each step in the interpretive process, ambiguity and uncertainty arise. The Hearsay-II problem-solving framework reconstructs an intention from hypothetmal interpretations formulated at various levels of abstraction. In additmn, it allocates hmlted processing resources fwst to the most promising incremental actions. The final configuration of the Hearsay-II system comprises problem-solving components to generate and evaluate speech hypotheses, and a focus-of-control mechanism to identify

Abstract not found

One potentially useful feature of future computing environments is the ability to capture the live experiences of the occupants and to provide that record to users for later access and review. Over the last 3 years, we have designed and extensively used a particular instrumented environment, the classroom, designed to facilitate the easy capture of the traditional lecture experience. We will describe the history of the Classroom 2000 project at Georgia Tech, and provide results of extended evaluations of the impact of automated capture on the teaching and learning experience. In addition to understanding the impact of automated capture in this educational domain, there are many important lessons to take away from this long-term, largescale experiment with a living ubiquitous computing environment. The environment needs to address issues of scale and extensibility, and there needs to be a way to continuously evaluate the effectiveness of the environment and understand and react to the w...

The spectre of climate change that is unfolding now is undeniably a cumulative impact of anthropogenic interference in the climate system over the last two centuries. The science is clear and the policy community is being increasingly convinced and galvanised into action to address this emergent challenge in light of the associated economic and human dimensions. The impacts of climate change ranging from sea level rise, melting ice caps and glaciers, severe weather events, drought, flooding, warming, subtle changes in ecosystems – will impinge on every aspect of society and economic life. The costs of inaction will more than outweigh the costs of action. There is only a narrow window of opportunity to redress the situation. The Intergovernmental Panel on Climate Change (IPCC) in its Fourth Assessment Report has

Abstract not found