LockerGnomeTech news and nostalgia for today's technology professionals
Subscribe

Search

Retro

Apple restored the vowels in Lisa’s code before turning it into the Macintosh memory manager

Bud Tribble’s translation job began with making somebody else’s identifiers readable, according to Andy Hertzfeld.

Chris presses a small rounded piece into a gap in a marquetry panel of interlocking shapes, a tray of spare rounded pieces beside him.
Illustration: LockerGnome

Before Bud Tribble could translate Lisa’s memory manager for the Macintosh, he had to translate the variable names back into readable words. Their vowels had disappeared. Apple was borrowing a memory-management design, and the identifiers apparently charged extra for A, E, I, O and U.

Andy Hertzfeld’s account of the work places the episode around the Mac team’s effort to reuse Lisa software under tighter memory constraints. Both machines used the Motorola 68000, but much of Lisa’s code was Pascal. The Mac team translated system components into assembly to reduce their footprint.

The memory manager had a job beyond merely handing out blocks. Without the memory-mapping hardware found in larger systems, the Mac needed software to move allocated blocks and reduce fragmentation. Indirect references called handles let the program find a block after it moved. Reusing a working design was sensible, assuming the next person could read it.

Tom Malloy had written the Lisa word processor and its memory manager, bringing techniques learned while working with Charles Simonyi at Xerox PARC. One naming convention placed type information at the beginning of identifiers. Limited identifier lengths then left little room for a descriptive name. Removing vowels was one way to squeeze the remainder in.

Tribble encountered the result when taking on the assembly translation. Hertzfeld recalls identifiers becoming “an unpronounceable jumble of consonants.” Missing comments made the job harder still. The first obstacle wasn’t how to express the algorithm in a different language; it was understanding what the existing expressions meant.

Tribble first stripped the type prefixes, restored vowels and added explanatory block comments. Only then did he translate the memory manager. Hertzfeld says he returned a few weeks later with an efficient assembly implementation and readable names, which became a cornerstone of the developing Mac system.

That order of work deserves attention. Making the old version readable reduced the chance of misunderstanding it during translation. A smaller final executable would have been a poor bargain if it quietly changed how memory moved. The intermediate clarity had a purpose even though customers would never see that version.

The account also limits the easy joke about naming conventions. This particular style came from a real combination of compiler limits, type information and workplace influence. It wasn’t random keyboard abuse, entertaining as that explanation might be. Constraints can produce habits that remain after their original benefit becomes harder for another team to see.

For a modern migration, the parallel is practical: making the source understandable can be part of the migration itself. That doesn’t mean renaming an entire project before every change. Tribble had a specific translation blocked by specific unreadable identifiers, and fixed those before proceeding.

The consonants finally had company.

More Retro

Every Retro story →