Gramada: immediacy in programming language development

Rein, Patrick; Hirschfeld, Robert; Taeumel, Marcel

doi:10.1145/2986012.2986022

Cited by 6 publications

(5 citation statements)

References 23 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…From a programmers' perspective, Edit Transactions introduce a two-stage workflow into live programing in which programmers collect a number of changes to the Edit [13][14][15][16][17][18][19][20][21][22][23][24][25] Transaction before deliberately activating the new behavior in running programs. Our case study gives insights into a programming experience that constantly balances immediacy against the need for grouped changes and the associated safety net.…”

Section: Resultsmentioning

confidence: 99%

“…His Software Architecture Group is concerned with fundamental elements and structures of software. [13][14][15][16][17][18][19][20][21][22][23][24][25][26][27][28][29][30][31][32]…”

Section: A Micro Benchmarks For Methods Call and State Access Overheadmentioning

confidence: 99%

“…The second class of errors occurred when we used messages in a method which were not implemented yet. When this type of error occurred [13][14][15][16][17][18][19] while the simulation was running, again a lot of debuggers opened. Often, we could resolve the issue without closing the simulation by quickly removing the call to the unimplemented method.…”

Section: Workflow Without Edit Transactionsmentioning

confidence: 99%

“…From the perspective of the programming environment, the feedback cycle can be modeled as a two-stage process [19]: 1. Adaptation, the phase where a changed translation unit, e.g. a method in Smalltalk, is translated to its executable representation.…”

Section: Introductionmentioning

confidence: 99%

“…From the perspective of the programming environment, the feedback cycle can be modeled as a two-stage process [19]:…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Edit Transactions: Dynamically Scoped Change Sets for Controlled Updates in Live Programming

2017

Self Cite

View full text Add to dashboard Cite

Live programming environments enable programmers to edit a running program and obtain immediate feedback on each individual change. The liveness quality is valued by programmers to help work in small steps and continuously add or correct small functionality while maintaining the impression of a direct connection between each edit operation and its manifestation at run-time. Such immediacy may conflict with the desire to perform a combined set of intermediate steps, like a refactoring, without instantly taking effect after each individual edit operation. This becomes important when an incomplete sequence of small-scale changes can easily break the running program.State-of-the-art solutions focus on retroactive recovery mechanisms, such as debugging or version control. In contrast, we propose a proactive approach: Multiple individual changes to the program are collected in an Edit Transaction, which can be made effective if deemed complete. Upon activation, the combined steps become visible together.Edit Transactions are capable of dynamic scoping, allowing a set of changes to be tested in isolation before being extended to the running application. This enables a live programming workflow with full control over change granularity, immediate feedback on tests, delayed effect on the running application, and undos at the right level of granularity.We present an implementation of Edit Transactions along with Edit-Transaction-aware tools in Squeak/Smalltalk. We asses this implementation by conducting a case study with and without the new tool support, comparing programming activities, errors, and detours for implementing new functionality in a running simulation. We conclude that workflows using Edit Transactions have the potential to increase confidence in a change, reduce potential for run-time errors, and eventually make live programming more predictable and engaging. ACM CCS 2012Software and its engineering → Development frameworks and environments; Object oriented development;

show abstract

Section: Resultsmentioning

confidence: 99%

“…His Software Architecture Group is concerned with fundamental elements and structures of software. [13][14][15][16][17][18][19][20][21][22][23][24][25][26][27][28][29][30][31][32]…”

Section: A Micro Benchmarks For Methods Call and State Access Overheadmentioning

confidence: 99%