Reading diagrams / Topic 30 of 42

Cables and journeys

The rule

A program with more than twelve entries draws its routes as cables. Routes that go through the same wrapper and carry exactly the same marks share one thick line, labelled with a pattern that covers their paths and a count. A route with a thin line of its own has no twin.

The label is a short name, not a rule. In problemsapi, “/learner/{check, check_photo}” names both its routes, but “/*/*” stands for six routes whose paths share no part. To see which routes a cable holds, open it: select it, and its routes are drawn one to a row with every mark and name.

Opening is not only for cables. Any part of a map, such as a wrapper or a shared step, opens as if it were the whole program: a journey. The part fills the wall. Everything that calls it directly comes in on the left, with its route under it when it is a route's handler. A caller with no route is another definition in the program. The name above the picture goes back to the whole map.

Two routes in one cable share every mark, so one review of that shape covers both. How often each route is called is not drawn.

A map this dense opens focused on one row: the row that reaches the most, named on the frame, with its wrapper, its handles, the resources it reaches and the program and engines it starts or runs; everything else is drawn but faded, and the frame says “the rest is faded”. The chooser above the map picks another row, or everything. Faded is not absent: a faded mark is still part of the program.

problemsapi.

Loading the system map.

The six-route /*/* cable of problemsapi, opened.

Loading the journey.

read_validated, a part shared by three callers in Icetakes, opened as a journey.

Loading the journey.

Loading the worked examples and practice.