Handling Source Code in a Database

I mean, source code in files; how quaint, how seventies! - Kent Beck

The Holon way

A computer program is an ordered collection of units; procedures, objects, methods, variables, etc., each identified by a name.

Collections are usually handled in databases. Why do programmers edit source code in text files? Why not in a database?

You can let the database create files for the compiler. And you have new options to present and handle the whole program clearly structured in a browser.

I admired the hierarchical presentation of classes in Smalltalk and wondered how the source browser could be applied to procedural source. There were files and programming units; but a middle level was missing. Finally, I noted that groups of units serve related functions.

The first Holon system had a structure of modules, groups and (Forth) words. It was functional in 1989 and evolved into Holon86.

Holon86 was a complete IDE including compiler, assembler and debugger. Source and compiled code are managed in an 'image', similar to Smalltalk. There is no need for external source files.

Later Holonforth became a multi-platform IDE for general use. HolonU (image above) creates source files as pipes to the code generator (compiler, interpreter).