Pinocchio: Bringing Reflection to Life with First-Class Interpreters

To support development tools like debuggers, runtime systems need to provide a meta-programming interface to alter their semantics and access internal data. Reflective capabilities are typically fixed by the Virtual Machine (VM). Unanticipated reflective features must either be simulated by complex program transformations, or they require the development of a specially tailored VM. We propose a novel approach to behavioral reflection that eliminates the barrier between applications and the VM by manipulating an explicit tower of first-class interpreters. Pinocchio is a proof-of-concept implementation of our approach which enables radical changes to the interpretation of programs by explicitly instantiating subclasses of the base interpreter. We illustrate the design of Pinocchio through non-trivial examples that extend runtime semantics to support debugging, parallel debugging, and back-in-time object-flow debugging. Although performance is not yet addressed, we also discuss numerous opportunities for optimization, which we believe will lead to a practical approach to behavioral reflection.

A qualitative study on the role of cultural background in patients perspectives on rehabilitation

Background Low back pain (LBP) is one of the major concerns in health care. In Switzerland, musculoskeletal problems represent the third largest illness group with 9.4 million consultations per year. The return to work rate is increased by an active treatment program and saves societal costs. However, results after rehabilitation are generally poorer in patients with a Southeast European cultural background than in other patients. This qualitative research about the rehabilitation of patients with LBP and a Southeast European cultural background, therefore, explores possible barriers to successful rehabilitation. Methods We used a triangulation of methods combining three qualitative methods of data collection: 13 semi-structured in-depth interviews with patients who have a Southeast European cultural background and live in Switzerland, five semi-structured in-depth interviews and two focus groups with health professionals, and a literature review. Between June and December 2008, we recruited participants at a Rehabilitation Centre in the German-speaking part of Switzerland. Results To cope with pain, patients prefer passive strategies, which are not in line with recommended coping strategies. Moreover, the families of patients tend to support passive behaviour and reduce the autonomy of patients. Health professionals and researchers propagate active strategies including activity in the presence of pain, yet patients do not consider psychological factors contributing to LBP. The views of physicians and health professionals are in line with research evidence demonstrating the importance of psychosocial factors for LBP. Treatment goals focusing on increasing daily activities and return to work are not well understood by patients partly due to communication problems, which is something that patients and health professionals are aware of. Additional barriers to returning to work are caused by poor job satisfaction and other work-related factors. Conclusions LBP rehabilitation can be improved by addressing the following points. Early management of LBP should be activity-centred instead of pain-centred. It is mandatory to implement return to work management early, including return to adapted work, to improve rehabilitation for patients. Rehabilitation has to start when patients have been off work for three months. Using interpreters more frequently would improve communication between health professionals and patients, and reduce misunderstandings about treatment procedures. Special emphasis must be put on the process of goal-formulation by spending more time with patients in order to identify barriers to goal attainment. Information on the return to work process should also include the financial aspects of unemployment and disability.

Back to the future in one week - implementing a Smalltalk VM in PyPy

We report on our experiences with the Spy project, including implementation details and benchmark results. Spy is a re-implementation of the Squeak (i.e., Smalltalk-80) VM using the PyPy toolchain. The PyPy project allows code written in RPython, a subset of Python, to be translated to a multitude of different backends and architectures. During the translation, many aspects of the implementation can be independently tuned, such as the garbage collection algorithm or threading implementation. In this way, a whole host of interpreters can be derived from one abstract interpreter definition. Spy aims to bring these benefits to Squeak, allowing for greater portability and, eventually, improved performance. The current Spy codebase is able to run a small set of benchmarks that demonstrate performance superior to many similar Smalltalk VMs, but which still run slower than in Squeak itself. Spy was built from scratch over the course of a week during a joint Squeak-PyPy Sprint in Bern last autumn.

Die laesio enormis und der dolus re ipsa heute: die Verschuldensfrage

The mediaeval interpreters of Roman law have worked out the dolus re ipsa-concept to explain the mysterious laesio enormis (C. 4.44.2 [a. 285]). The inequality in exchange has been supposed then to be a result of malicious undertaking, for which paradoxically, no one was personally liable (Ulp. 45 ad Sab. D. 45.1.36). In course of time, the incorporation of laesio enormis into the scheme of dolus turned into a presumption of a malicious act on the part of the enriched party, even though, the laesio enormis is free from subjective criteria. It is astonishing how little the dolus re ipsa is discussed, although the modern paradigm for correcting inequality in exchange is based on same assumptions. This ‘Wiederkehr der Rechtsfigur’ certainly deserves more attention.