Group:
code generation
Group:
memory management
ThesaGroup:
entries related to compiling
Topic:
compiler
Topic:
compiling pseudocode designs
Topic:
interpreter
Topic:
managing a Thesa database
Topic:
object code linkers and loaders
Topic:
software maintenance by patching
| |
Summary
Notes relevant to the design and implementation of Thesa's compiler and loader.
Subtopic: syntax 
| Quote: Thesa syntax defines certain symbols as operators; scan for match and replace with result; one crack at full match [»cbb_1980, OK]
|
Subtopic: performance
| Quote: first Thesa benchmark was better than existing languages but much worse than assembly code [»cbb_1980, OK]
|
Subtopic: macros
| Quote: a macro processor adds flexibility to a base language; allows alteration, delayed binding, and extensions [»browPJ_1974]
|
Subtopic: maintenance
| Topic: software maintenance by patching
| | Quote: Cedar system development by overloading a new module with the same interface; periodically rebuild to remove old versions [»swinDC7_1985]
| | Quote: Cedar goal of under five seconds for minor program changes; makes programming think-bound [»teitW3_1985]
| | Quote: update a distributed program by new functions with old and new interfaces [»giffDK7_1985, OK]
| | Quote: handle modified types by defining error handlers for each version; these handlers fixup an old version's behavior [»zdonSB10_1986]
| | Quote: if a module changes its exported interface, can hide it in a configuration that exports the old interface
| | Quote: Modeler includes single keystroke updating a system with a newly edited program [»lampBW6_1983]
| | Quote: Smalltalk can translate and relink a single change in a few seconds; makes simple modifications easy [»teslL8_1981]
|
Subtopic: dependency
| Quote: a useful utility is one that determines compilation dependencies and recompiles dependent modules [»laueHC_1979]
| | Quote: a compilation dependency occurs when one module is used to compile another; if a module is recompiled, then so are all dependent modules [»laueHC_1979]
| | Quote: what happens to old objects and their programs when a type definition changes; assumptions will no longer hold [»zdonSB10_1986]
| | Quote: changes in an integrated database are automatically made everywhere
| | Quote: Cedar uses system layering to reduce compilation dependencies and increase use of system components [»swinDC7_1985]
| | Quote: in source control, users should define dependencies between elements for warnings prior to changes and notification after changes [»leblDB5_1984]
| | Quote: to 'make' a node N, 'make' all nodes on which it depends; if any were modified after N, update N [»feldSI4_1979]
| | Quote: a DSEE system model describes the components, their build dependencies, and the build rules needed to recreate the system [»leblDB5_1984]
|
Subtopic: timestamp
| Topic: timestamps
| | Quote: represent modified object by original surrogate, new timestamp, modified data [»copeG3_1980]
| | Quote: if an analysis uses an item that becomes modified, the former value has a timestamp to limit its validity [»shavMJ2_1980]
|
Subtopic: module description
Quote: description files for external objects allow separate compilation and strong type checking
[»hansDR11_1979]
|
Related Topics
Group: code generation (30 topics, 585 quotes)
Group: memory management (11 topics, 346 quotes)
ThesaGroup: entries related to compiling (0 topics, 5 quotes)
Topic: compiler (18 items)
Topic: compiling pseudocode designs (8 items)
Topic: interpreter (59 items)
Topic: managing a Thesa database (34 items)
Topic: object code linkers and loaders (29 items)
Topic: software maintenance by patching
(26 items)
|
