Rename

Abstract: Symbols and Meanings in School Mathematics explores the various uses and aspects of symbols in school mathematics and also examines the notion of mathematical meaning. It is concerned with the power of language which enables us to do mathematics, giving us the ability to name and rename, to transform names and to use names and descriptions to conjure, communicate and control our images. It is in the interplay between language, image and object that mathematics is created and can be communicated to others. The book also addresses a set of questions of particular relevance to the last decade of the twentieth century, which arise due to the proliferation of machines offering mathematical functioning.

Abstract: Numerous studies have highlighted the importance of street naming as a strategy for constructing ‘places of memory’. This paper draws upon Bourdieu's theory of symbolic capital to examine two key moments in the history of street renaming in New York City: the renaming of the avenues on Manhattan's Upper West Side in the latter nineteenth century and the street renamings in Harlem a century later. The aim of such a comparative case study approach is to demonstrate how the symbolic capital associated with street naming may be linked to an elite project of symbolic erasure and forced eviction, on the one hand, and the cultural recognition of a historically marginalized group, on the other. Both cases consider attempts to rename formerly numbered streets and avenues, and the benefit of considering them together is that they illustrate the multiple interests—as well as the exclusionary politics of race, class, and gender—involved in such shifts from ‘number’ to ‘name’. In doing so, this paper extends the curre...

Abstract: Source code lexicon plays a paramount role in software quality: poor lexicon can lead to poor comprehensibility and even increase software fault-proneness. For this reason, renaming a program entity, i.e., altering the entity identifier, is an important activity during software evolution. Developers rename when they feel that the name of an entity is not (anymore) consistent with its functionality, or when such a name may be misleading. A survey that we performed with 71 developers suggests that 39 percent perform renaming from a few times per week to almost every day and that 92 percent of the participants consider that renaming is not straightforward. However, despite the cost that is associated with renaming, renamings are seldom if ever documented—for example, less than 1 percent of the renamings in the five programs that we studied. This explains why participants largely agree on the usefulness of automatically documenting renamings. In this paper we propose REanaming Program ENTities (REPENT), an approach to automatically document—detect and classify—identifier renamings in source code. REPENT detects renamings based on a combination of source code differencing and data flow analyses. Using a set of natural language tools, REPENT classifies renamings into the different dimensions of a taxonomy that we defined. Using the documented renamings, developers will be able to, for example, look up methods that are part of the public API (as they impact client applications), or look for inconsistencies between the name and the implementation of an entity that underwent a high risk renaming (e.g., towards the opposite meaning). We evaluate the accuracy and completeness of REPENT on the evolution history of five open-source Java programs. The study indicates a precision of 88 percent and a recall of 92 percent. In addition, we report an exploratory study investigating and discussing how identifiers are renamed in the five programs, according to our taxonomy.